Legal Tools
Sign in

User Guide · Timeline

How to use Timeline.

A step-by-step walkthrough of every control — from choosing your engine and focus filter to reading the output and understanding the evidence trail.

In this guide

  1. Choose your engine
  2. Focus filter
  3. Confidence filter
  4. Background events
  5. Date types
  6. Upload files
  7. Pasted text & context notes
  8. Reading the timeline
  9. Evidence trail, uncertainty & next step
  10. Tips & gotchas
1

Choose your engine

The engine controls the AI model used for extraction. Both engines use Azure OpenAI (West Europe). gpt-4o-mini costs 1 credit; gpt-4o costs 2 credits.

Engine Speed Best for
Azure gpt-4o-mini ★ Fast (~15 s) Default. Everyday extractions, long documents, first pass.
Azure gpt-4o Best quality (~45 s) Complex documents, overlapping events, ambiguous or poorly formatted source text.
2

Focus filter

The focus filter scopes what kinds of events the AI looks for. Found in the Advanced settings panel (click to expand).

Mode What it extracts When to use
All events ★ Every temporal reference in the document — background, operational, deadlines, narrative Building a complete chronology from scratch
Legal deadlines Filing deadlines, appeal windows, statutory time limits Checking whether you've missed a deadline or when you must act next
Court hearings Tribunal sessions, mediation dates, court appearances Preparing for a hearing or reconstructing hearing history
CPS milestones Barnevernet interventions, akuttplassering, tiltaksplan milestones, Fylkesnemnda proceedings Child welfare cases needing a CPS-specific chronology
3

Confidence filter

Controls whether uncertain events appear in the output. Also in the Advanced settings panel.

Setting What it does
Show all events ★ Returns all extracted events including LOW-confidence ones (shown in grey). Use for a complete picture — decide yourself what to trust.
Hide low-confidence Suppresses any event the model isn't reasonably certain about. Use when you need a clean, defensible timeline for court or legal filing.

LOW-confidence events are typically those where the date is implied rather than stated, relative to an unclear reference point, or extracted from a degraded or ambiguous section of the source.

4

Background events

Default: ON (checked). When checked, historical context dates are included — dates like "born 30.07.2015", "met around 2011/2012", "married in 2009". These establish the narrative and biographical context of a case.

When to uncheck: if you only want operational events and decisions — not biographical background. Unchecking substantially reduces event count in case notes that mix history with current proceedings. Useful when you're building a deadline tracker or action list rather than a full chronology.

5

Date types

Default: ON (checked). When checked, relative references ("tre uker etter vedtaket"), recurring patterns ("each Monday", "every 6 months"), and conditional dates ("if no response within 14 days") are included alongside absolute dates.

When to uncheck: if you need only exact calendar dates — for example when exporting to a calendar app, a deadline tracker, or a court submission that requires hard dates only. Unchecking removes all events without a resolvable absolute date.

6

Upload files

Timeline form showing engine selection, advanced settings panel, and file upload zone

Drag files onto the upload zone or click browse. A file list appears below with a Clear button to remove files.

Supported formats: PDF, DOCX, TXT. One file per run.

Files are extracted to text in memory. Nothing is written to disk. Nothing is retained after the session ends.

Uploaded file and pasted text can be combined — the AI reads both together as a single input. For cases spanning multiple documents, paste additional text into the text area alongside the uploaded file.

7

Pasted text & context notes

Paste up to 128,000 characters of text into the main text area — approximately 90–100 pages of A4. This can include case notes, decision letters, correspondence, or any document containing dates.

Context notes (optional, up to 2,000 characters): use this field to guide the AI on ambiguities in your document. These notes are passed directly into the extraction prompt and are not stored. Good examples:

  • "All dates are in 2024 unless stated otherwise."
  • "D refers to the defendant, M is the mother, BV is Barnevernet."
  • "The document is a summary of events, not in chronological order."
  • "'Vedtaket' always refers to the omsorgsovertakelse decision of 12.03.2024."
  • "Focus on the father's actions. Ignore events relating to the sister."
8

Reading the timeline

Timeline output showing date cards with ABSOLUTE badge, HIGH confidence, actor names, event descriptions, and source excerpts

Each event card in the timeline contains:

  • Date: the resolved date. Absolute events show a formatted date (e.g. 2025-04-09). Relative events show the expressed reference (e.g. "three weeks after the decision"). Periods show start–end.
  • Date type badge: one of ABSOLUTE / RELATIVE / RECURRING / CONDITIONAL / PERIOD. Tells you how the date was expressed in the source.
  • Confidence badge: HIGH (green — clearly stated), MEDIUM (amber — inferred), LOW (grey — ambiguous). LOW events appear greyed out when "Show all" is selected.
  • Actor: the person, institution, or body the event is attributed to (named or by role).
  • Event description: a concise one-sentence summary of what happened on that date.
  • Source excerpt: the exact text from your document that produced this event.

Sorting: use the sort toggle above the timeline to switch between Document order (the order events appear in your source) and Chronological (oldest to newest).

Search: type any keyword to filter events. The search matches against date, actor, description, and source excerpt simultaneously.

Detailed timeline events with Barnevernet social workers Judith and Trude, meetings in April and May 2025
9

Evidence trail, uncertainty & next step

Evidence Trail section with three source documents listed, What Remains Uncertain bullet list, and Next Practical Step recommendation

Three sub-sections appear below every timeline:

  • Evidence Trail: lists every source document (or paste) that contributed events, with a title and excerpt identifying the source. Use this to verify that all your documents were processed and to trace any event back to its origin.
  • What Remains Uncertain: a bulleted list of dates the AI could not fully resolve — undated events, events with ambiguous years, relative dates with no resolvable anchor. This is what you still need to verify or obtain manually.
  • Next Practical Step: a single AI-generated recommended action based on the overall timeline — for example: "Verify whether the 6-week appeal window from the 12.03.2024 omsorgsovertakelse has elapsed and document any missed deadline formally."

The disclaimer at the bottom confirms that Timeline provides preparation support, not legal advice.

10

Tips & gotchas

Use context notes for abbreviations. If your document uses internal abbreviations (D, M, BV, BH, the father, the case worker) consistently, naming them in the context notes dramatically improves actor attribution across all events.
Combine upload and paste for best coverage. Upload the main decision letter and paste related case notes into the text area. The AI reads all sources together and produces one unified timeline.
Run All events first, then re-run with focus. Start with the default "All events" mode to see the full picture. Then re-run with a specific focus mode (e.g. Legal deadlines) if you need a filtered view for a submission.
Date types off for clean deadline lists. If you're exporting to a calendar or deadline tracker, uncheck "Date types" to return only resolved calendar dates — no relative or recurring entries to sort through.
Use gpt-4o for complex or heavily contested cases. The higher-accuracy engine handles overlapping timelines, ambiguous phrasing, and dense source text better than gpt-4o-mini. Costs 2 credits.
LOW confidence isn't wrong — it's uncertain. A LOW confidence event may still be correct and important. Read the source excerpt for each LOW event before dismissing it — the AI may have found a real date that was just expressed ambiguously.

Ready to try it?

Free for Do Better Norge members.

Sign in to use Timeline → Register free How it works under the hood