Build a source-linked chronology from a document pack

A chronology is useful when every event can be traced to a source. It should preserve conflicting accounts rather than turn them into a single confident narrative.

Prepare the input

Use a shareable document pack with stable references. Specify whether dates are document dates, event dates, or receipt dates. Keep undated material in the pack rather than forcing it into an invented timeline.

Run the workflow

Ask for event, stated date, date type, source, and uncertainty. Separate what a document says from what the reviewer has verified. Put disputed or contradictory statements side by side.

Prompt to copy

Build a chronology from: [documents].
Columns: stated event, explicit date, date type, source section,
account or speaker, and uncertainty.
Do not infer missing dates, legal deadlines, or causation.
Preserve conflicting accounts as separate entries.
List undated events and reviewer questions after the table.

Review a worked example

Illustrative pack: a letter dated 8 May says a delivery occurred “last week”; another record states 2 May. Keep the letter date and its wording distinct from the explicitly recorded delivery date. Do not silently calculate an exact day from “last week.” Check every date against its source.

Inspect events with several dates. A document can be written, sent, received, and acknowledged on different days. Keep each date attached to its stated event. Do not choose the earliest date merely to make sorting easier. Where the source only gives a month, preserve that precision rather than manufacture a day.

Use it again

Let counsel resolve the significance of conflicts and add verified corrections. The output is preparation, not a finding of fact. Explore Bot or contact Golub for a separately scoped document workflow.