There is a phrase often heard in public procurement reviews: “The file is complete.”
It is offered as reassurance, sometimes as a defense, and occasionally with a degree of pride.
It is also frequently beside the point.
A defensible procurement file is one that allows an independent reviewer to reconstruct and justify every material decision. A complete file and a defensible file are not the same. Confusing the two creates the documentation trap; one that is more widespread, and more consequential, than many practitioners acknowledge.
What “Complete” Actually Means
When practitioners say a file is complete, they usually mean that the required documents are present. The procurement plan is approved. The solicitation document contains the mandatory sections. The evaluation report is signed by the panel members. The contract carries the appropriate signatures.
In other words, the file contains the required outputs of the process.
What it typically does not contain is the reasoning behind those outputs; the thinking, the alternatives considered, the factors that led to one decision over another, and the basis for each judgment. That distinction is not a matter of form. It is the substance of auditability in public procurement.
When an oversight body, a donor’s fiduciary review team, or an investigating authority reopens a file months later, the question is not whether the required forms are present. The question is whether the process can be understood, explained, and justified from what is written in the record.
Most files cannot meet that standard. Not because the procurement was improperly conducted, but because the documentation was designed to satisfy a template rather than to record a decision.
How the Trap Develops
It is often said that a well-kept procurement file should “tell a story”—one that allows a reviewer to reconstruct the process from beginning to end. The idea is sound, but incomplete. The more relevant question is what that story actually contains.
Public procurement frameworks are procedural by design. They define the steps to be followed and the records to be kept. They do not generally prescribe how to document the reasoning behind decisions.
Templates fill part of that gap, but only structurally. They provide a place to record outputs, not a method for capturing judgment.
A well-formatted evaluation matrix does not explain why a technical threshold was set at a particular level. A signed approval memorandum records that a decision was taken, but not why one option was chosen over another. The form is present. The reasoning is absent.
This gap is reinforced by how procurement files are often assembled in practice. Decisions may be made in meetings, discussions, or under time pressure, and the file is then completed afterward to demonstrate that the required process was followed.
This does not necessarily indicate misconduct. In many cases, it reflects operational realities. However, it produces documentation that presents conclusions as though they were the result of the recorded process, when in fact the process reflects decisions taken earlier and elsewhere.
This is retroactive rationalization. It is the mechanism at the center of the documentation trap.
The Questions the File Must Answer
A practical test is whether a public procurement file can answer, on its face and without further explanation, a set of basic questions:
- Why was the selected procurement method chosen over available alternatives, and on what factual basis were any exceptions justified at the time?
- How was the contract value estimated, and what information informed that estimate?
- Why were specific evaluation criteria, weightings, and thresholds selected in light of the requirement?
- On what precise basis were bidders excluded, rejected, or not shortlisted?
- Why was the selected bidder chosen, particularly where the outcome departs from the lowest price or highest technical score?
If these questions cannot be answered from the written record, the file is not audit-defensible, regardless of whether every required document is present.
Compliance and Its Limits
In many systems, the prevailing compliance culture reinforces this problem. When oversight focuses primarily on whether procedures were followed and documentation is complete, it signals that compliance is the primary objective.
Practitioners respond accordingly. Effort is directed toward ensuring that the file appears correct, rather than that the decision trail is intelligible.
Regulatory frameworks often reflect the same emphasis. They specify the records that must be retained but rarely require that the reasoning behind key decisions be explicitly documented. An evaluation report may be required, but the manner in which evaluators resolved close or disputed judgments may not be recorded.
The result is a system that produces complete files without producing transparent decisions. Documentation accumulates. Reasoning remains implicit.
This distinction becomes critical when procurement outcomes are questioned. Where a contract is awarded to a bidder that is not the lowest priced, for example, the file may contain a complete evaluation record and all required approvals. Yet if the rationale for preferring a higher-priced, higher-rated proposal is not clearly stated, the decision cannot be reconstructed from the record alone. The process appears compliant, but the outcome is difficult to defend.
What Defensible Documentation Requires
Addressing this issue does not require new rules. It requires a more disciplined approach to documentation.
At each material decision point, the record should capture:
- the options available
- the factors considered
- the criteria applied
- the conclusion reached
- the authority responsible for the decision
- and the reasons why alternatives were not selected
This reflects established principles of sound administrative decision-making. In public procurement, these principles are often displaced by an overreliance on templates and formal compliance.
Several practical points follow.
Documentation should be prepared at the time decisions are made, rather than reconstructed afterward. Contemporaneous records are inherently more reliable and more credible under scrutiny.
The procurement method decision should be carefully documented. In practice, it is often reduced to a mere formal classification, even though it is one of the most consequential decisions in the process.
Finally, a clear distinction should be maintained between the process record and the decision record. The former demonstrates that required steps were followed. The latter explains why particular choices were made. Both are necessary, but they serve different purposes.
The Audit That Has Not Happened Yet
Public procurement files are often reviewed long after the process is complete; when the individuals involved are no longer available and the original context has been lost.
At that point, the file must stand on its own.
The relevant question is not whether it appeared complete when it was closed, but whether an independent reviewer can understand and justify the decisions that were made.
If that is not possible, the file is not complete. It is a liability.
Stop writing for the template. Start writing for the reviewer.
Method selection—one of the decision points most frequently left undocumented—is examined separately in “Method Selection Is Not a Clerical Step in Public Procurement.”