How to build an evidence hierarchy for RFP claims

Claim design

Define what must be believed before ranking the proof

Break a broad sentence into atomic propositions. “Our certified platform reduces processing time by 40 percent and will meet 99.99 percent availability” contains at least four claims: certification, applicability of the certificate to the offered platform, a measured outcome and a future service commitment. Each has a different source, boundary and approval path. One logo or case study cannot inheritably prove the whole sentence.

Write a claim card with proposition, type, subject, entity, product or service, configuration, geography, population, measurement period, conditions and intended tender location. Record whether the wording describes current fact, past outcome, forecast, target or binding offer. Qualifiers such as “for the hosted service,” “during the 2025 reporting period” and “subject to the proposed dependency” are not decoration. They determine alignment.

Rate consequence before searching. A minor statement about meeting cadence may need an approved operating description. A data-residency statement, minimum staffing promise, regulatory assertion or service-level target can affect eligibility, contract exposure and delivery. Consequence is not rhetorical importance. A dramatic differentiator may create little obligation, while one annex line can create a serious commitment.

Evidence strength

Rank applicability and control, not document prestige

Evaluate each source on seven dimensions. Authority asks whether its creator owns or can attest to the fact. Directness asks whether it proves the proposition rather than a nearby fact. Scope match covers entity, product, geography, population and conditions. Recency checks whether it remains valid. Reliability examines accuracy, completeness and method. Independence considers whether a separate party tested the fact. Approval confirms permission to use the source and wording in this bid.

The dimensions prevent rigid source worship. An external audit report can provide high independent assurance but does not prove a control outside its examination boundary. An internal production record may be the most direct proof of a service metric if its data lineage and calculation are controlled. A signed expert attestation can resolve a precise architecture fact, yet it is weak support for a market-wide comparison or an outcome the expert did not measure.

GAO guidance describes data reliability through accuracy, completeness and applicability for the intended purpose, using a risk-based assessment. Applicability matters in bids: information can be accurate in its original setting and still be unsuitable for the proposed sentence. NIST control-assessment guidance also tailors assessment procedures to risk tolerance. Use these as design principles, not claims that a bid review is an audit or security assessment.

• Authority: the source creator is competent and accountable for the fact.
• Directness: the artifact proves this proposition rather than an adjacent one.
• Scope: entity, service, configuration and population match the offer.
• Recency: the fact remains valid for the stated period or future use.
• Reliability: method, completeness and data lineage can be examined.
• Independence: corroboration does not merely repeat the same origin.
• Approval: disclosure and offer wording are authorized.

Assurance levels

Raise the threshold as the cost of being wrong rises

Define a few consequence classes with minimum rules. For low-consequence descriptions, one current approved source owned by the relevant function may suffice. For scored claims about method, benefit or experience, require a direct source with clear scope and owner confirmation. For claims affecting eligibility, regulation, safety, price, contractual performance or material buyer risk, require controlled primary evidence, independent verification where available and explicit offer authority.

Do not confuse a hierarchy with an automatic pass. Level A evidence for one proposition may be Level C for another. A certificate is primary evidence that a named entity holds a certification within its stated scope and dates. It is only indirect support for the claim that every proposed service control is effective. A customer report can directly prove what that customer measured, but not what every future customer will achieve.

Complementary evidence is useful when items close different gaps. A control description establishes design, a test report establishes operation during a period, and an approved solution statement maps that control to the offered service. This is a chain, not a vote. Three brochures derived from one product page do not create independent sources. Record common origins so repetition is not mistaken for corroboration.

Decision control

Change the claim when the evidence cannot carry it

For every material claim, record the selected evidence, owner, date, version, relevant extract, applicability boundary, approval and reviewer decision. A source is not stronger because the full file sits in a folder. The exact passage and its relation to the sentence must be inspectable. If confidentiality prevents attaching the record, decide what permissible representation, attestation or controlled access preserves evaluative value without implying the buyer has seen unavailable proof.

When evidence falls short, first seek a better primary record or responsible confirmation. If neither exists before the deadline, narrow the proposition. Replace “all implementations reduce time by 40 percent” with an approved, contextual observation from the measured project, if disclosure is permitted. Label a forecast as a forecast and a target as a target. Route any exception to an authority who sees both the proposed wording and the missing assurance.

Review the hierarchy after major amendments and before submission. Changes to solution scope, legal entity, subcontractors, hosting, service level or price can break applicability without changing the evidence file. FAR treatment of past performance illustrates the discipline: currency, relevance, source and context all matter. The hierarchy does not exist to make a library look orderly. It stops the final offer from claiming more than the organization can responsibly prove.

• Link the exact supporting extract to the exact claim.
• Record scope, date, owner, version and permission to use.
• Seek stronger primary proof before adding secondary material.
• Narrow fact, period or population when support is limited.
• Revalidate applicability whenever the offered solution changes.