- confident dates can go directly to Calendar;
- uncertain dates wait in Approvals; and
- you can require review for every date.
How it works
For each document, the existing classification request may propose up to three important dates. Suchi validates the date, its role, and the supporting 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 date format, allowed roles, and supporting text. Those checks do
not independently verify the model’s interpretation of a role. Read the source
quote; turn automatic dates off if each new date should need a human decision
in Approvals before reaching Calendar.
Date precision and 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.
Confidence is separate: it is the model’s self-reported score for its extraction,
not a measured probability of correctness. A model can be highly confident that
the document names only a year. Percentages are rounded; even 100% is not a
guarantee. Check the source text before relying on a date.
Choose automatic or reviewed dates
Open Settings → Archive configuration → Classification. Keep Use similar documents for automatic filing and suggestions on if you want local archive matching. It does not require a model. Configure the optional model and choose Test connection. The Choose what Suchi can handle automatically section keeps the controls in two boxes:- Works without a model contains archive matching and its own save action.
- Uses the configured model contains Apply model suggestions at and Add high-confidence dates to Calendar automatically.
Automatic dates are enabled by default. Confidence reduces review work; it is
not proof that a date is correct. Every Calendar entry still links to its
document and supporting text.
Automatic and reviewed dates
Calendar distinguishes how each date got there:- An automatic date was extracted while automatic dates were enabled and met the configured threshold. It keeps its confidence, extractor, extraction version, source revision, and evidence, but has no reviewer.
- A reviewed date records the person’s decision and review time. Rejected dates do not appear on Calendar.
day, month, or year label.
Rescanning refreshes unreviewed machine output from the current document and
extractor version. It does not overwrite a person’s accepted or rejected
decision. This prevents stale automatic results from accumulating while keeping
human decisions durable.
Review dates in Approvals
Approvals shows only dates that still need a decision. Dates are grouped by source document. When there are more than two document groups, desktop uses a two-column grid; mobile remains a single column. Some pending dates are preselected to reduce repetitive clicking. Before acting:- Read the parsed date, role, confidence, and document text.
- Uncheck anything incorrect.
- Choose Add N to Calendar for the selected dates, or Reject N to remove the selected dates from review.
Find dates on Calendar
The public demo has read-only, curated source dates labeled Demo example. They are not live model results and do not show classifier 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 shows dates added automatically and dates approved in Approvals. It supports:- a month grid, a full-width day agenda, or an all-dates agenda for document-scoped links;
- date-role filtering;
- all accessible documents or one saved View; and
- direct links back to each source document.
Open a day’s dates
Select a day number in the month grid to open its full-width agenda. This lists every exact-day date for that day, keeping the selected Document view and Date role. Month/year placeholders never appear as dates on the first day. More than 500 matching facts use Previous and Next pages. Back to Month YYYY returns to the month you came from with those filters intact. Calendar keeps its month, selected day, View, and role in the URL, so reload and browser Back/Forward retain that context. A day agenda can be linked directly, for example#/calendar?month=2026-08&date=2026-08-06&role=due.
Dates linked from archive research
Open N calendar dates in Archive research opens an agenda for all retrieved documents in that answer, across every month and year. The banner reads Dates from N selected documents · All months and years. Entries appear in chronological order with the full year, source document, and supporting text. The document count in the banner is separate from the number of dates. Date role still filters the agenda. The month controls and Document view selector are hidden because the link already supplies the document scope. Opening a different document-scoped link clears the previous saved View, date role, and page. More than 500 matching dates use Previous and Next pages; they are not limited to the current month. Open full calendar removes the document scope and returns to the unfiltered current-month grid.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. The downloaded file contains one all-day event with the document title, date role, and a link to the source document. It contains no document attachment or source quote. 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
The confidence and automatic-date settings apply to new documents immediately. They also govern new machine output from documents you explicitly rescan. 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 document scope. 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 automatic dates are set as intended.
- Processing: select the document and run Rescan or Extract dates.
- Access: confirm you can read the source 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.