Record version desk case: finding the controlling contract

What to take away

• This fictional case demonstrates a document-control method.
• Four official-looking files answer four different questions.
• The signed contract is not the last word after an amendment.
• Invoice totals do not equal the contract ceiling.
• The article states both the supported finding and its limit.

The fictional City Ledger receives a PDF labeled "Harbor Sensor Contract Final" from a source. Page 18 lists $3.2 million. A city spending export shows $2.6 million paid to the vendor. A council packet links to a $2.9 million agreement. The tip says officials secretly added $300,000.

The numbers are real within this invented exercise, but they do not yet support the tip. Jumping past that gap is the eighth of the public records reporting problems: claiming more than the record shows.

Inventory before interpretation

The records editor gives each file a neutral label:

Item	Source	Date	Status	Amount shown
File A	emailed PDF	March 2	unsigned draft	$3.2 million
File B	council packet	March 18	signed agreement	$2.9 million
File C	procurement portal	June 7	signed amendment	$3.2 million ceiling
File D	spending export	through August 31	recorded payments	$2.6 million

The file name "Final" is not a status. Signatures, dates, repository history, and linked amendments determine which terms were in force. That is why the policy tools comparison warns against calling a ceiling the final cost.

Authenticate the public copies

The editor retrieves the agreement and amendment from the official procurement record rather than relying on the emailed copies. The team saves record URLs, identifiers, hashes, download times, and page counts. It checks that every exhibit named in the agreement is present.

Digital signatures can help establish integrity when a publisher uses them. GovInfo explains that its signed PDFs provide evidence of source identity and whether a file changed after certification, while noting that validation may require opening the file in suitable software. The GovInfo authentication instructions support treating a valid signature as provenance and integrity evidence. They do not prove that every factual statement inside a signed publication is true.

The city's portal does not use the GovInfo system, so the newsroom does not claim that GovInfo authenticated these fictional files. It applies the broader distinction between file integrity and content accuracy.

Trace the legal sequence

The March agreement sets a base price of $2.9 million. The June amendment adds optional equipment with a maximum authorization of $300,000. It does not state that the full option was ordered or paid.

The correct sequence is:

1. the city and vendor sign a $2.9 million agreement;
2. a later amendment permits up to $300,000 in optional work;
3. the resulting ceiling becomes $3.2 million;
4. the payment export lists $2.6 million through August 31.

The draft happened to contain the later ceiling, but it was not itself proof that the city adopted that amount.

Separate four money questions

The reporter creates a definition box:

Term	Meaning in the case
Base price	Amount in the original signed agreement
Authorized ceiling	Maximum after the signed amendment
Ordered amount	Work the city directed under the available authority
Paid amount	Disbursements recorded through the export date

The available records establish base price, ceiling, and recorded payments. They do not establish the full ordered amount because the relevant work orders are missing. Bounded findings of this shape are the endpoint of the public records reporting guide.

Request the missing records

The desk requests option notices, work orders, invoices, acceptance records, and payments after August 31. It names the contract number, vendor, procurement office, and date range. It asks for native spreadsheet data and a field guide. The request follows the public records request checklist almost line by line.

Records-management terminology also helps the newsroom ask for the right copy. A National Archives glossary defines an official or record copy as the original or retained copy maintained under an organization's records policy and retention schedule. The NARA records-management glossary supports asking which copy is designated for retention. It does not determine the fictional city's local policy.

Publish the bounded finding

The final article says:

A signed June amendment raised the Harbor Sensor contract's authorized ceiling from $2.9 million to $3.2 million by allowing up to $300,000 in optional equipment. City payment data lists $2.6 million paid through August 31. The records reviewed do not show how much optional work the city ordered.

The story does not say officials secretly spent $300,000. It reports the documented authorization, the paid amount, and the missing evidence.

Desk lessons

• Never treat a descriptive file name as proof of version status.
• Build a document sequence before comparing amounts.
• Define ceiling, obligation, invoice, and payment separately.
• Retrieve the source copy from the responsible repository.
• List missing records beside the claims they prevent.
• Update totals with a stated through-date.

Common questions

Why not report the $3.2 million draft first?

The unsigned draft did not establish approved terms. Later signed records supplied the authority and sequence.

Did the amendment prove that $300,000 was spent?

No. It authorized a maximum for optional work. Orders, invoices, acceptance records, and payments would answer later stages.

Is a valid digital signature proof that a report is correct?

No. It can support file identity and integrity. The contents still require reporting and interpretation.

Why include the payment export's cutoff date?

Payments after that date are outside the file. Without the cutoff, readers could mistake an interim total for a final one.