Government
A basis of action that can be reconstructed by somebody who was not there.
A basis of action that can be reconstructed years later, from retained sources, by someone who was not there and who is entitled to disagree.
the worked caseA supplier's registered address changed twice in eighteen months. The award file reproduces the address as it stood on the day of award, with the extract.

Two worked cases on this page, both fictional and both built the way a real one is: a value, the document it was read from, the date of reading, and the value it was chosen over.
The questions you get asked
Nobody asks for more information. They ask whether one line can be defended.
These are the questions that arrive after the work is delivered, from the party entitled to disagree with it. Every property on this page exists because one of them has to have an answer that does not depend on the person who assembled the file.
- 01
On what basis was this determination made, and what did the file contain at the time?
- 02
Why was this element withheld from the copy I received?
- 03
The supplier's registered details have changed twice. Which version did you act on?
- 04
Can you produce this file without the officer who assembled it?
Asked by an inspector general, by an appeals board or a court, and by a member of the public exercising a right of access.
The buyer
Programme offices, procurement integrity and oversight
Units whose determinations affect a person, a supplier or an appropriation, and whose files are read afterwards by inspectors, auditors, courts and requesters.
What they fuse
Three kinds of source, one answer
Each kind arrives with different licence terms, different reader restrictions and different reasons to be wrong. The record keeps them distinguishable after the fusion, which is the part that is normally lost.
Applications, determinations and correspondence held in systems of record that never leave the agency.
Commercial registries and data shared under agreement, where the agreement itself constrains who may read what.
Entity registrations, award notices, court dockets, sanctions and debarment lists, published inspection reports.
Worked case one
A past state reproducedAn award file that still reads correctly three years later
By the time an award was challenged, the supplier had moved twice, changed its registered name once, and the registry page that had been read at the time no longer existed. The file did not need the live registry: it carried the retained extract, the date it was read, and the value as of that date.
The figure beside this is what the reader sees: the value, its status, the source it was read from, and the value it was chosen over.
Worked case two
A value the reader may not seeOne determination, three readers, and one element that is withheld
The same case file is read by the officer who wrote it, by an inspector, and by a member of the public under a records request. They are not entitled to the same material, and the record refuses to produce a version in which the restricted element is merely absent. The value is named, the restriction is named, and the basis of the restriction is cited, so a requester can contest a withholding instead of never learning that there was one.
A different failure from the first case, on the same record and under the same four guarantees. Both are fictional; neither is a simplification of how the values are shown.
Why the record has to hold
What the rules ask for, in their own words
These are the recordkeeping obligations that make a defensible value a requirement rather than a preference. We name them because our customers are measured against them; we make no claim to certify anyone against any of them.
Making and preserving records
United States, federal agenciesAgencies must make and preserve records that document the organization, functions, policies, decisions, procedures and essential transactions of the agency.
Electronic records management
United States, OMB and NARAAgencies manage records in electronic form with the metadata needed to retrieve and interpret them, and transfer permanent records to the National Archives electronically.
Contract file content
United States, federal acquisitionThe contract file must constitute a complete history of the transaction, sufficient to support actions taken and to furnish essential facts in the event of litigation.
What changes for this reader
The same work, with the evidence attached at the moment it is read
Not a claim about speed and not a claim about savings: a description of the practice on each side. Everything on the left is what people in this role do today, and almost all of it is done well by people who resent having to do it that way.
The file holds a link to a registry page that has since been revised, moved or withdrawn.
It holds the extract as it was read, with the date of reading, so the file does not depend on a page somebody else maintains.
A check against an exclusion list is recorded as a line on a checklist, initialled.
It is recorded with the list, its version and the date searched, so nothing reads as a clearance that was never granted.
Producing a file for an inspector means asking the officer who worked on it what they remember and hoping they are still in post.
The file reproduces itself as it stood on the day of the action, with no dependence on any individual being available.
Redaction is done on a copy, and the released version shows blank space where the withheld material was.
A withheld element is named as withheld with its basis cited, so a requester can appeal the restriction rather than the silence.
A supplier that changes its name appears as a new party, or is matched back to the old one by hand.
One record carries both names with their dates, and the identifier does not change when the name does.
What you get
What the record guarantees government readers
The four guarantees, stated in the vocabulary of this sector. They are the same four everywhere; read them in general on the guarantees page, and see them applied to a live record on the demonstration.
- One record per supplier, person or facility, with every former name and identifier retained and resolvable.
- Every determination cites the document it rests on, retained as it was read, with the date of reading.
- A check that returned nothing is recorded as a check that returned nothing, naming the list and its version, never as a clearance.
- The file can be reproduced as it stood on the day of the action, for an inspector, a court or a requester.
Primary sources
The texts behind these obligations
Public bodies work under statutes, executive memoranda and procurement regulations that say what a record must contain and how long it must last. The texts below are the ones behind the obligations on this page. They are provided for reading, and our naming of them is not a claim of certification.
- 44 U.S.C. 3101, Records management by agency heads; general duties. The duty to make and preserve adequate and proper documentation of decisions and essential transactions.
- National Archives. Federal agency records management laws (44 U.S.C. Chapter 31). The chapter as published by the National Archives.
- OMB/NARA Memorandum M-19-21, Transition to Electronic Records. Electronic records management expectations for agencies.
- FAR 4.801, General (contract files), acquisition.gov. The contract file as a complete history of the transaction.
Reference pages that apply to this sector
- Unique Entity ID (UEI)
- D-U-N-S Number
- Common Procurement Vocabulary (CPV)
- ISO 3166 country codes
- Data Catalog Vocabulary (DCAT)
- Retaining source copies
- Scoping a first record
- Separating reader clearance
- Data catalog vs system of record