How it works
For each document, the existing classification request may suggest up to three important dates. Suchi checks the date, its role, and the matching text before storing it. This does not add a second model request. The model chooses a role from the document’s context. These are the eight allowed roles and their intended meanings, not hard-coded classification rules:
Suchi checks the date format, allowed role, exact quote, and matching date
spelling in the original extracted text. In a numeric date that starts with a
four-digit year, such as
2026-03-04, 2026–03–04 or 2026 03 04, and in a
date written year-first with Chinese, Japanese or Korean markers, such as
2026年3月4日 or 2026년 3월 4일, the numbers must be year, month and day in
that order. Numeric locale forms whose month/day order is genuinely ambiguous,
such as 02/01/2006, remain valid for either interpretation. Other quoted
dates must contain exactly the day, month and year the precision names:
numbers, or a month name or common abbreviation in English, German, French,
Spanish, Italian, Portuguese, Dutch, Swedish, Danish, Norwegian, Finnish,
Polish, Czech, Turkish, Russian, Ukrainian or Thai. Japanese era years
(令和8年), Buddhist-era years, two-digit years and full-width, Arabic,
Persian, Devanagari, Bengali or Thai digits are read as numbers. An extra
number (such as a time), a second month name, or a component that disagrees
rejects the date rather than guessing.
These checks do not independently verify the model’s interpretation of a role.
Read the quote and open the document before relying on a date; even a
model-confidence score of 100% is not a guarantee.
Date precision and model confidence
Precision describes how much of the date the document supplies. There are exactly three values:
Calendar and Approvals display only the known precision. For storage and
sorting, August 2026 uses
2026-08-01 and the year 2026 uses 2026-01-01.
Those first-day placeholders do not mean the document names that exact day.
Model confidence is the model’s self-reported score for its suggestion, not a
measured probability of correctness. A model can report high confidence even
when the document names only a year. Percentages are rounded; even 100% is
not a guarantee. Check the document text before relying on a date.
Configure application mode
Open Settings → Archive configuration → Classification. Apply when confident is selected by default:- Apply when confident: Add dates to Calendar and apply suggested metadata when they meet your thresholds.
- Review first: Send inferred changes to Approvals before they apply.
0.70. Each date uses its own score,
independently of the document’s overall classification score. Local matching
needs no model: its automatic threshold defaults to 0.90, with a 0.50
minimum review-suggestion score. Below-threshold usable dates still need review.
Configure the optional model and choose Test connection. The test uses
synthetic text; it checks connectivity and response format, not accuracy, and
does not enable the model. Enable model and save options activates the tested
configuration. Application mode does not authorize external text sharing.
Saving settings, lowering a threshold or restarting Suchi never promotes existing
pending dates. The current mode applies to new ingests and explicit rescans.
Automatic and reviewed dates
Calendar distinguishes how each date got there:- An automatic date met the current threshold policy and was accepted without a human reviewer or review time. The exact document text is still checked.
- A previously accepted date has no recorded review. This includes dates accepted automatically by older versions. Its value, original text, and attribution are preserved; Suchi does not invent a reviewer.
- A reviewed date records the person’s decision and review time. Rejected dates do not appear on Calendar.
threshold-auto-v1, not merely a missing reviewer.
Rescanning replaces pending model suggestions, not accepted or rejected dates.
New suggestion IDs are never reused. Older pending suggestions without a
provable document version cannot be accepted; request fresh extraction instead.
An older immutable document version retains its own review history: a new
version does not retarget an earlier date or copy its authority.
Review dates in Approvals
Approvals lists dates that still need a decision in its Dates tab, grouped by document. When there are more than two document groups, desktop uses a two-column grid; mobile remains a single column. For each date, read the suggested date, role, exact document text and How this was suggested details, then choose Add to Calendar or Reject. When more than one date can be added, Add all N dates to Calendar in the toolbar accepts every one of them at once. Dates you leave alone stay pending. Stale or unsupported suggestions cannot be added; supported stale suggestions can still be rejected. Sensitive text requires Reveal. Refresh after document or access changes; queued extraction is not an accepted date. See Approvals for permissions and API behavior.Find dates on Calendar
The public demo has read-only, curated dates labeled Demo example. They are not live model results and do not show Model confidence. Its default Calendar lists all example dates across months and years. Model calls, date extraction, and date review remain unavailable to demo visitors. Calendar pairs a grid with a date-grouped agenda. It defaults to the current fixed month; 30 Days and 2 Weeks select rolling ranges beginning today. Arrows move one complete month or rolling range, and the current-month control resets the default. Range, saved View, and date-role state stays in the URL. The All documents scope still enforces document access rules. Only exact-day dates populate grid cells. Month-only and year-only dates remain in the agenda when their sorting date falls in the range. Research links omit range bounds and include all dates.Focus a day’s dates
Selecting a day highlights its cell and scrolls the adjacent feed to its full group without changing the URL, filters, or query. A direct exact-day URL instead opens a paged full-width agenda, for example#/calendar?date=2026-08-06&role=due; Back to Calendar returns to the current
month with View and role intact.
Dates linked from Ask your documents
Open N calendar dates opens every accepted date for the answer’s documents. The Dates from N selected documents · All dates banner counts documents, not dates. Date role still filters the agenda; range controls and Document view stay hidden because the route already names the documents. Results over 500 use Previous and Next. Open full calendar clears the document scope and returns to the current fixed month.Add a reviewed date to another calendar
In an agenda entry, expand Add to calendar, read the export notice, and choose Download .ics. Open or import the file in a calendar application. This is available for reviewed, accepted dates with an exact day, for any date role. Automatic dates do not offer export. Neither do month/year-only dates, whose sorting placeholders are not known calendar days. Document Detail lists a document’s accepted dates under Dates with how far away each one is, and offers Add to calendar for the same exportable dates. A schedule with more than four dates keeps its first three on the card and moves the rest under Later dates in the More section, whose label counts them. The downloaded file contains one all-day event with the document title, date role, and a link to the document. Due dates carry a reminder one day before; expiry and renewal dates carry one a week before. It contains no attachment or quoted document text. The link still requires the recipient’s normal Suchi access; an export does not create a public share link. Suchi generates the file locally in the browser, without connecting a calendar account. Importing it into a synced calendar may send its contents to that calendar’s provider. The file is a snapshot, not a subscription: later changes in Suchi do not update an imported event. Repeated exports from the same archive URL retain the event’s identifier, but duplicate-import behavior depends on the calendar application. No reminder, recurrence, or time zone is inferred, and the event does not mark the day as busy.Search by date
You can also use dates in the query language:Apply the current settings to older documents
Model settings affect new documents and explicitly requested extraction. They never change the decision on a pending, accepted or rejected date. To process older documents:- Open Documents.
- Select the documents.
- Choose Rescan or Extract dates.
Why a date might be missing
Check these in order:- Approvals: the date may be waiting for a decision.
- Calendar filters: check the date role and exact documents. On the full calendar, also check the month and Document view.
- Document text: open the document and confirm extraction captured the date.
- Model settings: confirm the model is active and check application mode and threshold.
- Processing: select the document and run Rescan or Extract dates.
- Access: confirm you can read the document and have Manage document dates permission.
Current limits
- Dates are all-day document facts, not timed meetings.
- Time zones and reminders are not inferred.
- Relative phrases that cannot be normalized from explicit document text are ignored.
- Bare account numbers, totals, and version numbers are not treated as dates.
- At most three dates are proposed per classification run.
- Existing Calendar dates are never silently removed by a setting change.