What's New in Sevrel — March 2026
Historical snapshot
This article records what the March release announced. Product architecture changed afterward, so each item below now states its current status. It is not a list of every capability available today.
March announcements and current status
Critical Date Tracking
March introduced a standalone critical-date tracker. That router is no longer mounted. The current configurable lease-expiry agent checks recorded lease end dates inside 30 days and does not derive notice, option, covenant, or escalation deadlines.
Query Templates
March introduced a dedicated saved-template concept. That router and custom-template panel are not currently mounted. Today’s chat catalog provides editable one-turn prompt shortcuts, not separate deterministic pipelines.
Portfolio Analytics
Selected authenticated dashboard-analysis APIs remain mounted, but the legacy Dashboard UI is retired. Results depend on available structured records, critical-date fields may be empty, and scores are decision-support heuristics rather than predictions.
Scheduled Reports
The mounted API can save supported report definitions and execute them on demand. A current background dispatcher does not automatically run due definitions or deliver recurring report email, so the original recurring-delivery description should be read as historical intent.
Why we annotate instead of deleting
The easy fix for a dated announcement that no longer matches the product is to delete it. We think that is the wrong fix. This post was published, read, and indexed; quietly removing it would erase the record without correcting it, and anyone who remembered the original claims would have nothing to check them against. So the March text stays, and each item carries a plainly labeled statement of where things stand now. When the status changes again, the annotation changes with it — visibly, with the revision date at the top of the page.
The same policy applies across this blog: dated posts are records, and corrections are made in place and marked as corrections. A company asking you to trust its software with your lease files should be willing to show its own paper trail — including the parts of it that describe features that were later rebuilt or retired.
How to read a dated product post
A few habits make announcements like this one more useful and less misleading, here or anywhere else. Treat the publication date as part of the claim: “the product does X” always means “did X, as described, at that time.” Prefer the current reference pages — for Sevrel, the Features page and the release notes — over any dated announcement when the two disagree. And read renames carefully: product surfaces get rebuilt, and a March name may refer to an architecture that no longer exists even when a similar-sounding capability does. The annotations above are exactly that kind of translation, written down so you do not have to guess.
Improvements recorded in March
- CRE vocabulary support for document search
- Spreadsheet parsing for supported rent-roll and OpEx inputs
- Conversation context for multi-turn questions
- Source-citation display with document previews when evidence is available
For the current qualified capability list, review the Features page and release notes.