---
title: "How to close evidence gaps before proposal approval"
description: "Turn each unsupported proposal statement into a bounded evidence task, then support, narrow, qualify, replace, remove or block it before release."
canonical: "https://zephior.com/insights/close-evidence-gaps-before-proposal-release"
last-updated: 2026-09-04
---

# How to close evidence gaps before proposal approval

> Turn each unsupported proposal statement into a bounded evidence task, then support, narrow, qualify, replace, remove or block it before release.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-04; updated 2026-09-04. 19 minute read.

## Definition

A proposal evidence-gap record identifies one buyer-facing statement or answer that lacks the proof required for its intended use. It preserves the exact wording, buyer requirement, consequence, minimum evidence test, current material, reason for the shortfall, closure route, work product, reviewer, deadline and final disposition. A gap closes only when the statement becomes supported at its stated scope, is narrowed or qualified through a permitted route, is replaced by an authorized commitment, or is removed. Silence, elapsed time and general risk acceptance do not create evidence.

## Problem

Norchester Data Transition is answering a council procurement for migration of housing case records. Its executive summary says two full rehearsals reconciled every legacy record with 99.98 per cent field agreement. The evidence link opens a presentation slide containing the same number. The analyst who built it has left. The comparison export is absent, the slide does not state the denominator, and one rehearsal excluded scanned attachments. The response team has three working days before release. It must determine whether the original result can be reconstructed, what the buyer actually asks to see and what wording can survive if the proof remains incomplete.

## Point of view

Start with the exact sentence and the buyer decision it is meant to support. Define what evidence would be sufficient at that scope before hunting for a convenient file. Diagnose whether the gap concerns existence, identity, access, relevance, period, population, calculation, independence, permission or approval. Give the gap a closure route and a latest decision time. Verify the resulting artifact against the original test rather than accepting an attachment count. If the route fails, reduce or remove the statement. A proposal approver may accept the commercial consequence of losing a claim, but cannot approve missing proof as though it existed.

## Close the evidence path or change the statement before approval

An evidence gap is not a task called “find support.” It is a failed relationship between a particular statement and the material required to justify it for a particular buyer use. Freeze the sentence first. If the proposed claim is “every legacy record was reconciled,” the evidence test cannot be satisfied by a project plan, a team recollection or a slide that repeats the percentage.

Write the minimum pass condition before searching. For Norchester, that condition includes both rehearsals, the frozen input and output populations, record and field identifiers, included attachment classes, comparison logic, exceptions, totals and a reviewable result. The buyer may request a report rather than raw personal data, so the evidence package and the buyer-facing attachment can differ while preserving the same conclusion.

A valid ending changes either the evidence state or the claim state. The team can link sufficient proof, reduce “every record” to an accurately measured subset, disclose a permitted limitation, replace a result with an authorized delivery commitment, remove the number or stop release. “Accepted risk” may describe the consequence of removing the claim. It cannot convert an unknown denominator into 99.98 per cent.

Keep the row open until the accepted text appears in every dependent location. A corrected technical section does not close an executive-summary claim, a chart caption or a yes response in the portal.

**Minimum evidence-gap record**

| Field | Required content | Reason |
| --- | --- | --- |
| Statement | Exact words, version, location and linked occurrences | Defines what cannot yet ship |
| Proof test | Buyer use, scope, method, result, status and release form | Prevents convenient evidence substitution |
| Gap | Current material, missing dimension, cause and consequence | Defines the decision that remains open |
| Closure | Route, owner, deliverable, verifier, time and disposition | Shows whether the claim can survive |

## The buyer’s question determines what counts as enough

Read the complete requirement, response instruction, scoring method and requested attachment. Separate a participation document from proof used to score the technical offer. The European Single Procurement Document is preliminary evidence in its stated procurement context and identifies supporting documents that may later be requested. It does not mean that a bidder may leave an evaluated technical claim unsupported because some qualification certificates arrive later.

Decompose the statement into entity, object, action, population, period, result and modality. “Two rehearsals reconciled every legacy record” asserts two completed events, full population coverage and a measured outcome. The phrase also implies that the records belonged to the proposed migration boundary. A report for a different customer, system release or sampling run does not meet that test without narrower wording.

Calibrate review to consequence without inventing a universal hierarchy. A minor descriptive sentence may need an owned current record. A scored performance statistic may need source data, calculation logic and independent reproduction. A signed declaration or legal conclusion needs the appropriate authorized reviewer. More evidence is not automatically better: the PCAOB audit-evidence standard, within its financial-audit scope, makes the useful distinction that poor-quality material is not repaired merely by obtaining more of the same kind.

Record whether the buyer asks for the evidence in the bid, on request, before award or during delivery. That timing affects the required attachment, not the truth of the statement. The proposal still needs an internal factual basis for every released claim.

## Name the missing dimension before assigning the work

“Evidence missing” hides several different problems. The record may not exist, may sit in an inaccessible system, may lack a stable identity, may cover the wrong population, may be outdated, may contradict another source, may require a calculation that cannot be reproduced, may contain protected information or may lack factual and external-use approval. Each condition has a different owner and remedy.

Norchester has at least four gaps. The slide is derivative rather than the nearest record. The denominator and comparison method are absent. Scanned attachments were excluded from one run although the wording says every record. The owner’s departure leaves the result without a current validator. Sending one request to the former analyst’s manager would not resolve those four conditions.

Preserve what exists before repairing it. Record file identity, date, creator, source system, query or export parameters, access state and observed limitation. If a dashboard changes continuously, capture an authorized export or snapshot with the observation time. Do not silently overwrite the slide or discard an inconvenient run.

Route adjacent problems to their own decision. A source conflict needs reconciliation. Stale evidence needs a currency assessment. A protected report needs a disclosure decision. A known negative result needs the limitation process. This dossier controls whether the open gap reaches a valid disposition before release.

**Gap types and appropriate routes**

| Gap type | Question to answer | Typical route |
| --- | --- | --- |
| Record absent | Was the event measured or documented at all? | Reperform, retest, narrow or remove |
| Scope mismatch | Which entity, population, version or period is unsupported? | Find complementary proof or reduce wording |
| Method unknown | Can the result and denominator be reproduced? | Recover logic and inputs or rerun a controlled test |
| Use restricted | Can the fact be validated and released in an allowed form? | Controlled review, cleared extract or non-disclosure route |

## Assign a deliverable and test, not a vague chase

An owner receives the gap record, not just the sentence “please confirm.” The request identifies the proposition, buyer use, candidate source, missing dimension, acceptable output, access boundary and latest useful time. The owner may point to a controlled existing record, produce an authorized extract, explain that the record never existed or nominate the person who can reproduce the event. Each response creates a new state for review; none closes the row automatically.

Use independent procedures where the claim warrants them. Inspection can show what a record contains. Recalculation can test arithmetic. Reperformance can test a procedure. Confirmation can establish a statement from a competent party. Inquiry alone may locate evidence but does not prove every underlying fact. These distinctions appear in formal audit standards within their own scope and are useful design references for a bid evidence process.

A retest must answer the same question. Freeze inputs, exclusions, configuration, time and expected output before execution. If the original population cannot be recreated, label the new result accordingly. A successful sample does not revive a full-population claim. A new rehearsal after product changes may demonstrate current capability, but it does not prove what happened in the historical rehearsal.

Work backwards from the release cutoff. Include access approval, extraction, privacy review, calculation, technical validation, wording, translation and final propagation. Set an earlier decision time for changing or removing the claim. A task that finishes after the response is signed is not a closure route for that submission.

## A received file is only a candidate until it passes the test

Check the object that arrived against every field in the proof test. Establish issuer or producing system, version, period, population, method, result, exceptions and approval status. For company-produced data, test accuracy and completeness or the controls that support them. Record transformations between source events, export, workbook, chart and proposal sentence.

Inspect contrary evidence. The relevant set includes information that supports the statement and information that weakens it. A clean result for structured fields does not erase missing attachments. A manager’s confirmation that a rehearsal occurred does not supply its denominator. If a new record reveals an adverse fact, freeze the wording and move that issue to the limitation-disclosure decision rather than declaring the gap closed.

The validator must be competent for the question. A data analyst can reproduce matching logic; a migration lead can confirm service scope; privacy can decide what report form may leave the controlled environment; a commercial or executive authority can approve the resulting bid position. One person may hold several roles where the real mandate allows it, but the decisions remain separately visible.

Attach the evidence version and validation result to the exact claim version. If the sentence changes from “sampled active cases” to “every legacy record,” reopen the test. Approval does not travel to a stronger paraphrase.

**Verification of Norchester’s candidate report**

| Dimension | Required check | Failure response |
| --- | --- | --- |
| Population | All included record and attachment classes are enumerated | Narrow the stated population |
| Calculation | Counts, denominator, exclusions and matching rule reproduce | Correct, rerun or remove the percentage |
| Comparability | Both rehearsals used the described migration boundary | Report results separately |
| Release | The report exposes no prohibited case data and has approval | Use a cleared summary or withhold the attachment |

## Supported is one outcome, not the default outcome

Use states that change release behavior. Supported means the identified evidence passes the recorded test for the exact wording. Narrowed means a smaller proposition is supported and the stronger one is prohibited. Qualified means the procurement permits an explicit limitation and the complete wording has approval. Commitment approved means the answer is about a future deliverable and the company has authorized that obligation. Removed means the response no longer relies on it. Blocked means no permitted truthful response is ready.

Do not use “risk accepted” as a synonym for supported. Management may decide to continue a bid after removing a differentiator. It may approve a clearly labeled future commitment if the organization can deliver it. It cannot accept the risk that an unverified historical statistic will be presented as fact. If legal interpretation or buyer compliance is uncertain, a qualified reviewer must decide the permitted route.

Any qualification must live where the buyer will understand it. A footnote in a remote annex cannot cure an unconditional headline. A future commitment must use future language and align with solution, price, schedule, acceptance and contract. A removed proof point must also leave win themes, graphics and rehearsed presentations.

Preserve the rejected wording and reason internally. This prevents the same unsupported sentence from returning through an older answer-library version or a colleague’s local file.

## Close the row only after the final package matches the decision

Trace the statement into technical answers, summaries, tables, captions, case studies, response matrices, annexes, slide decks and portal fields. Search exact text and meaning-equivalent variants. Give each occurrence an approved wording or removal state. The evidence-gap record stays open while any stronger copy remains.

Check attachments in both directions. Every cited item must be present, current and permitted. Every attachment must have a response purpose and current authority. A replaced workbook should not remain in the package beside the corrected report. File names and document properties must not suggest a stronger scope than the text supports.

Run the check after rendering and upload preparation. Conversion can drop footnotes, split a qualification from its table or substitute an older chart image. Portal character limits can truncate the boundary of a claim. Compare the previewed output with the approved proposition rather than assuming source documents survived.

Archive the final disposition, evidence identity, validator, approved wording, affected occurrences and reopen conditions. A source correction, changed buyer question, larger claim, new population or expired authorization reopens the relationship.

**Release states and their effect**

| State | What is established | Release effect |
| --- | --- | --- |
| Supported | Named evidence passes the exact proposition test | Approved wording may proceed |
| Narrowed or qualified | A bounded proposition or permitted limitation is approved | Only the complete bounded text may proceed |
| Commitment approved | A future obligation is feasible and authorized | Future wording and dependent offer changes proceed together |
| Removed or blocked | No adequate permitted evidence path exists | Delete the claim or stop the dependent release |

## Norchester rebuilds the comparison and gives up the global number

The bid manager freezes the 99.98 per cent sentence, chart and portal summary. The evidence test identifies both rehearsals, all housing case records, scanned attachments, the field-comparison rule, exceptions and an approved report. Repository history recovers the migration manifests and comparison code. The first rehearsal output can be reproduced. The second lacks the attachment export and used a different matching rule.

The data lead reruns the current comparison against preserved authorized extracts, records file hashes, populations, rules and exceptions, and has another analyst reproduce the totals. The new report separates structured case fields from attachments and distinguishes the historical first run from the present rerun. Privacy approves an aggregate report without resident information.

The result supports a high agreement rate for the specified structured fields, not “every legacy record across two full rehearsals.” Norchester removes the global percentage from the executive summary. The technical answer states the tested population and result, identifies the attachment validation still required during implementation and gives the proposed acceptance control as a future commitment approved by delivery and commercial owners.

The row closes only after the old number disappears from the chart and portal field. If the tender required a completed full-population rehearsal as a pass condition, this wording change would not solve the requirement. The response would remain blocked or the bid decision would need to change.

## Useful outcomes

- Every material unsupported statement has its own identifier, exact wording and response location.
- The buyer requirement and evaluation use define the needed proof instead of a generic evidence label.
- Existing files are assessed for source, scope, population, period, method, status and permission.
- The reason for the gap is classified before work is assigned.
- Each closure route names an owner, deliverable, dependencies, test and latest useful time.
- New evidence is checked independently before it can support the response.
- Failed routes produce narrower wording, a permitted qualification, an authorized commitment, removal or a release block.
- The final package contains no statement whose only support is an unanswered request or an internal approval.

## Workflow

1. **Freeze the proposed statement.** Capture its exact words, location, version, owner and dependent summaries, tables and form answers. Mark each occurrence unavailable for release.
2. **Define the proof test.** Read the buyer question and decide which entity, service, population, period, method, result, authority and disclosure form the evidence must cover.
3. **Inventory what exists.** Preserve candidate records, systems, owners and access conditions. Record what each item shows and which required dimension it leaves open.
4. **Classify the shortfall.** Distinguish absent, inaccessible, unverified, stale, differently scoped, incomplete, contradictory, unreleasable and unauthorized material.
5. **Choose a closure route.** Retrieve a controlled record, obtain confirmation, reproduce a calculation, rerun a test, secure release permission or change the claim.
6. **Verify the result.** Have the competent reviewer test authenticity, completeness, scope, method, exceptions, wording and permitted external use.
7. **Apply the disposition.** Mark supported, narrowed, qualified, commitment approved, removed or blocked and propagate the exact approved text to every occurrence.
8. **Reconcile the release set.** Compare the evidence register with the rendered response, attachments and portal fields. Reopen any claim changed after the evidence decision.

## Key decisions

- What exact buyer-facing proposition is unsupported, and where does it appear?
- What buyer instruction, criterion or reasonable reading determines the necessary evidence?
- Which entity, product, service, configuration, population and period must the proof cover?
- Is the gap about the underlying fact, the record, the method, external release or decision authority?
- Can an existing authoritative record close the gap without changing its meaning?
- Would a new calculation or test be reproducible and comparable before the safe cutoff?
- If proof arrives, who is competent and authorized to validate it?
- If it does not arrive, what narrower statement remains supported?
- Does the procurement permit a qualification or a future commitment at this location?
- Which dependent response elements must stay blocked until the final disposition propagates?

## Risks

- Calling a slide, email or dashboard a source when it only repeats the proposed claim
- Changing the evidence threshold after seeing which records are easy to obtain
- Counting an unanswered request as work completed
- Using more low-quality copies to compensate for the absence of a reliable underlying record
- Rerunning a favorable test on a smaller or cleaner population without preserving the change
- Treating permission to view confidential evidence as permission to attach it
- Allowing a senior approval to substitute for factual validation
- Leaving the unsupported wording in an executive summary after narrowing the detailed answer
- Assuming the buyer will ask for a missing document or allow correction after submission
- Closing a register row without checking the rendered final package

## Metrics

- Number of open evidence gaps by response section, consequence and latest decision time
- Percentage of gaps with an explicit minimum evidence test and named verifier
- Median time from gap discovery to a tested disposition
- Percentage closed through existing records, new evidence, narrower wording, qualification, commitment or removal
- Number reopened because received evidence failed the stated scope or quality test
- Number of requests still awaiting an owner after the first escalation point
- Percentage of approved claims linked to the exact evidence version used at release
- Unsupported occurrences found after PDF rendering or portal entry
- Post-submission challenges caused by a gap marked closed without sufficient proof

## Frequently asked questions

### Can a manager accept the risk of missing evidence?

A manager can accept the consequence of narrowing or removing a claim within their authority. Approval cannot make an unsupported factual statement true or satisfy a document the buyer requires.

### Is an email confirmation enough to close a gap?

Only if the proof test calls for a statement from that competent person and the email covers the exact scope. It does not replace source data, a calculation or formal document when those are required.

### What if the evidence owner does not respond?

Escalate against the last useful time, then use the predetermined fallback. Narrow, qualify where permitted, replace with an authorized commitment, remove or block the statement.

### Does attaching more material make the claim safer?

No. Each item must add relevant and reliable support. Repeated summaries and uncontrolled copies do not repair a missing underlying record and may create contradictions.

### Can we rerun a test after discovering the gap?

Yes, if the new test is properly authorized, controlled and relevant. Describe it as the event it is. It cannot prove a different historical result or a population it did not test.

### What is the difference between narrowing and qualifying?

Narrowing changes the proposition to the scope the evidence supports. Qualifying states a material limitation or condition and requires a response form the procurement allows.

### Should we wait for the buyer to request the evidence?

Follow the tender’s evidence timing, but do not make an internal factual claim without support. Never assume the buyer will permit a missing required item to be supplied later.

### What can software do in an evidence-closure workflow?

It can inventory occurrences, route requests, track deadlines, compare versions and test that approved wording propagated. Competent people still validate facts, permissions, commitments and release.


## Primary sources

- [Procurement Act 2023, section 19 on award against published criteria and requirements](https://www.legislation.gov.uk/ukpga/2023/54/section/19), UK Legislation
- [Procurement Act 2023, section 30 on incomplete, inaccurate or misleading supplier information](https://www.legislation.gov.uk/ukpga/2023/54/section/30), UK Legislation
- [Current Procurement Act guidance for the procure phase](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase), Cabinet Office
- [Official supplier information and guidance collection](https://www.gov.uk/government/collections/information-and-guidance-for-suppliers), Cabinet Office
- [Sourcing Playbook on evidence-based sourcing and bid evaluation](https://www.gov.uk/government/publications/the-sourcing-and-consultancy-playbooks/the-sourcing-playbook-html), Cabinet Office and Government Commercial Function
- [Bid evaluation guidance in the Procurement Pathway](https://www.procurementpathway.civilservice.gov.uk/documents/best-practice/bid-evaluation-sourcing-playbook), Government Commercial Function
- [European public procurement directive, including supporting evidence under Article 59](https://eur-lex.europa.eu/eli/dir/2014/24/2024-01-01/eng), EUR-Lex
- [Commission regulation establishing the European Single Procurement Document](https://eur-lex.europa.eu/eli/reg_impl/2016/7/oj/eng), EUR-Lex
- [European Commission guidance on the ESPD and eCertis](https://single-market-economy.ec.europa.eu/single-market/public-procurement/digital-procurement/european-single-procurement-document-and-ecertis_en), European Commission
- [World Bank Procurement Regulations for IPF Borrowers, seventh edition](https://thedocs.worldbank.org/en/doc/c84273d1b230aeb2b0b8134de5dc8cd7-0290012025/original/Procurement-Regulations-7th-Edition-Sep-2025.pdf), World Bank
- [World Bank guidance on evaluating bids and proposals using rated criteria](https://documents.worldbank.org/en/publication/documents-reports/documentdetail/099325208202512194), World Bank
- [UNCITRAL Model Law on Public Procurement and documentary qualification evidence](https://uncitral.un.org/sites/default/files/media-documents/uncitral/en/2011-model-law-on-public-procurement-e.pdf), United Nations Commission on International Trade Law
- [PCAOB AS 1105 on sufficient, relevant and reliable audit evidence](https://pcaobus.org/oversight/standards/auditing-standards/details/AS1105), Public Company Accounting Oversight Board
- [PCAOB implementation guidance for electronic external information](https://pcaobus.org/news-events/news-releases/news-release-detail/pcaob-publishes-staff-guidance-providing-examples-of-the-application--of-paragraph-10a-of-as-1105--audit-evidence), Public Company Accounting Oversight Board
- [PCAOB AS 1215 on documenting evidence and conclusions](https://pcaobus.org/oversight/standards/auditing-standards/details/AS1215), Public Company Accounting Oversight Board
- [NIST SP 800-53A Rev. 5 on assessment plans, procedures and findings](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final), National Institute of Standards and Technology
- [NIST SP 800-171A Rev. 3 on assessment evidence and determination statements](https://csrc.nist.gov/pubs/sp/800/171/a/r3/final), National Institute of Standards and Technology
- [GAO Green Book 2025 on quality information, deficiencies and corrective action](https://www.gao.gov/products/gao-25-107721), United States Government Accountability Office
- [GAO Government Auditing Standards 2024 Revision](https://www.gao.gov/products/gao-24-106786), United States Government Accountability Office
- [National Archives records-management policy and guidance](https://www.archives.gov/records-mgmt/policy), United States National Archives and Records Administration


## Related articles

- [How to close unresolved tender questions before approval](https://zephior.com/insights/close-unresolved-tender-questions-before-release)
- [How to build an evidence hierarchy for RFP claims](https://zephior.com/insights/build-an-evidence-hierarchy-for-rfp-claims)
- [How to ask an expert for usable RFP evidence](https://zephior.com/insights/ask-an-sme-for-rfp-evidence)
- [Who is allowed to approve each kind of proposal evidence?](https://zephior.com/insights/assign-ownership-for-proposal-evidence)