TL;DR
- -��Track when a file arrived separately from the period its information describes.
- -��Use effective dates, source versions and owner decisions to resolve competing facts.
- -��Leave unknown timing visible instead of inferring it from file order.
On Wednesday, a client uploads a glossy profile saying the company has 18 regional offices. On Monday, the operations director approved a spreadsheet showing 16. The profile is the newer upload, so the writer uses 18 in a press release. Later the team discovers that the profile was designed nine months earlier for an expansion that changed.
The upload timestamp answers when the communications team received a file. It says nothing by itself about when the contents were true, whether they remain true or which definition produced them. Treating recency of receipt as recency of fact can make an old document silently overrule a current decision.
Give each date one job
Receipt date
When did this workspace receive the file or statement? This helps with lineage and handoffs. It cannot establish the period described inside the material.
Source date and version
When was the document created, issued or revised, and which version is it? If the document lacks a reliable date, record that gap instead of substituting the upload time.
Relevant or effective period
When was the assertion true or intended to take effect? A report issued in April can describe results through December. A policy signed today may begin next month. Store a range or boundary where a single date would mislead.
Review and decision date
When did an authorized owner assess the fact for the intended use? A recent review improves visibility but does not rewrite the historical period of the source.
Test the fact against the draft’s time frame
Write the proposed claim with its time meaning exposed. “The company has 18 offices” is a current-state assertion on the publication date. “The company planned to reach 18 offices by June” describes a plan at an earlier point. Those sentences can come from the same source and require different evidence.
Ask the owner whether the fact is a snapshot, a period total, a cumulative figure, a forecast or a standing policy. Check definitions as well as dates. One document may count staffed offices while another includes partner premises. A date match cannot reconcile a scope mismatch.
When facts conflict, keep both records and describe the precise disagreement. Do not overwrite the earlier one or choose the latest upload automatically. Ask the responsible owner to accept one for the current assertion, retain both with distinct scopes or hold the claim pending clarification.
Chronology: receipt, revision, effective period, decision
Consider a fictional food distributor. A brochure uploaded April 8 says it serves 40 towns. Its file metadata identifies a January 15 revision. The page gives no effective date. An operations note issued March 30 says deliveries currently reach 36 towns and four proposed routes await approval. These details are invented to illustrate the method.
The chronology should record: brochure received April 8; brochure revision January 15; brochure fact period unknown; operations status effective March 30. It should also record the different wording and the owner asked to resolve it. The recent upload does not displace the later-dated operational status.
If the owner confirms that deliveries currently reach 36 towns, current copy can use that approved fact. Keep the four proposed routes as separate planning information; their count does not establish how many towns they would serve. The 40-town statement remains part of the record with its uncertain timing and rejected current use. If a historical article needs to describe the January plan, the brochure might still be relevant after its meaning and permission are checked.
Design for uncertainty rather than hiding it
A missing effective date is information. Mark it unknown, assign a clarification owner and show which drafts depend on the answer. For urgent work, the release owner can narrow or remove the claim. Inventing a date from context makes the record look complete while weakening it.
Add review triggers for facts that change after appointments, openings, reporting cycles or policy decisions. The extra fields require maintenance, so reserve detailed tracking for reusable or material claims. A chronology that leaves an effective date visibly unknown is more reliable than a tidy record that borrows the upload date.
QuoteIt is being developed to support dated, provenance-aware context for persona-led drafting. Join the waitlist if that workflow matters to your team.
Join Waitlist