An RFP evidence request is a controlled question sent to the person who owns or can locate a source needed for one buyer-facing claim. It identifies the tender requirement and answer location, the exact proposition the team may state, the entity, service, population, geography and period it must cover, the preferred evidence object and acceptable alternatives, required fields, disclosure limits, response deadline, reviewer and possible outcomes. The request is complete when the recipient supplies traceable material, narrows or contradicts the proposed claim, identifies the correct owner, or confirms that no suitable record exists. The expert reply is input to source review. It is not automatic permission to insert the wording or attachment into the bid.
A municipal energy authority is procuring operations for 312 public electric-vehicle charge points. One scored question asks how the supplier will restore failed units and requests evidence of performance on comparable estates during the last 12 completed months. The proposal writer sends the service director a message saying, “Please add proof that our support is excellent by tomorrow.” The director replies with a slide showing 98.7% availability, a dashboard screenshot and two customer names. The slide covers a different service, the screenshot has no date or denominator, availability is not restoration time, and neither customer has approved disclosure. The team has received plenty of material but still cannot support the answer the evaluator will score.
Ask for an evidence object, not confidence, copy or a favourable number. Begin with the buyer’s exact proposition and decide what the response must let an evaluator verify. Convert that need into a bounded request containing the candidate claim, relevant scope, source type, minimum metadata, confidentiality route and latest useful response time. Do not lead the expert toward the desired result. Invite exceptions, missing records and counterevidence. The proposal team owns the request and subsequent review; the source owner explains the record; the authorized claim owner approves what may be said. A response closes only after the evidence is inspected and its permitted use is recorded.
Direct answer
Ask for proof the evaluator can inspect, not prose the writer can paste
A useful request begins with a test: what would let a reviewer decide whether this exact proposition is supportable? If the answer is a monthly service report, ask for that report and the metric definition. If it is a signed acceptance record, name the project phase and acceptance event. If the answer needs a reference example, identify the capabilities and period that make the example comparable. “Send evidence” leaves all of those decisions with a busy recipient who may not have read the tender.
The candidate claim is a question, not a script for the expert. Write “We are considering the statement that the offered support operation restored at least 95% of priority-two charger incidents within four hours during each of the last 12 completed months. Please provide the underlying record or tell us where this statement fails.” Do not write “Please confirm that we achieved 95%.” The first wording makes a negative result usable. The second rewards agreement and hides the population, calculation and exceptions.
The expert does not have to produce the final tender sentence. Source custodians are often best placed to locate the report and explain its definitions. A proposal writer can then draft within the buyer’s answer format, while operations, compliance, legal or another authorized owner approves the relevant facts and disclosure. Keeping those acts separate prevents a polished email from becoming unsupported evidence.
| Field | What to record | Why it matters |
|---|---|---|
| Answer need | Buyer text, source locator, response field, criterion and limit | Keeps the request tied to the work the evaluator will assess |
| Candidate claim | One proposition marked as proposed, not yet approved | Allows evidence to support, narrow or contradict it |
| Proof envelope | Entity, service, population, geography, period, definition and exclusions | Prevents a nearby but irrelevant record from being substituted |
| Evidence object | Preferred source, acceptable alternatives, native format and required fields | Makes the response inspectable rather than anecdotal |
| Control | Custodian, access route, disclosure limit, due time and reviewer | Protects the material and reserves time for a use decision |
Answer contract
Derive the request from the buyer’s answer contract
Read the requirement, instructions, scoring descriptors, definitions, appendices and response field together. They may ask different things: demonstrate current capability, describe a future method, provide a certificate, quantify past performance, identify named staff or attach a buyer form. Evidence suitable for one act does not automatically satisfy another. A policy can explain a method but cannot establish a measured result. A historic report may support experience but not a present configuration.
Official procurement regimes express this boundary in different ways. UK award criteria must be clear, measurable and specific, and the published assessment methodology governs assessment. FAR Part 15 separates proposal instructions from evaluation factors, then directs evaluation to the factors and subfactors in the solicitation. EU, German and French rules likewise distinguish selection evidence, offer content and award criteria. Those rules govern buyers, but they teach the bidder an operational lesson: request the evidence the actual procurement asks the evaluator to use.
Write an internal answer contract before contacting the expert. Record the buyer proposition, required response act, evidence expressly requested, scoring use, format, location, limit and date. Add the smallest internal decision the evidence must enable. If the buyer asks how the team will control restoration, the answer may need a method and current operating evidence. If it asks for a performance figure over 12 months, the request must preserve the calculation period and population. Do not inflate a method question into a request for a flattering statistic.
Ownership
Find the source custodian before chasing a department of experts
Subject knowledge and source custody are different. The service director may understand incident operations, while the reporting analyst owns the metric logic, the platform team owns exported records, customer success owns reference permissions and the contract owner knows disclosure limits. Sending the same broad message to all four creates duplicate work and contradictory attachments. Route the source request to the custodian, then name the interpreters and approvers who may be needed later.
Ask who generated the object, which system or process produced it, who can explain changes, and who may authorize external use. W3C PROV separates entities, activities and agents for the same reason: a report, the process that generated it and the person responsible for that process are related but not interchangeable. The proposal record does not need to implement an ontology. It does need a stable link among source object, derivation, custodian and use decision.
When ownership is unknown, send a routing request rather than the evidence question. Include the claim need and ask for the custodian of the named record. Set `wrong_owner` when the recipient can explain the topic but cannot locate or authorize the source. That response is progress. Do not leave the request assigned to the most senior person merely because they can pressure others to answer.
| Role | Contribution | Authority not implied |
|---|---|---|
| Requester | Defines the answer need and tracks closure | Truth of the proposed claim |
| Source custodian | Provides the native object and provenance | Permission to publish every field |
| Subject expert | Explains definitions, context and operating exceptions | Final legal or commercial wording |
| Evidence reviewer | Tests scope, integrity and fitness for the claim | Ownership of the underlying operation |
| Claim owner | Approves the supported external statement | Release of restricted attachments |
| Disclosure owner | Decides access, redaction and permitted external use | Accuracy of the proposal interpretation |
Specification
Specify both the proof envelope and the evidence object
The proof envelope describes the slice of reality the proposed claim covers. For an operating metric it can include legal entity, service edition, delivery model, customer population, incident class, geography, period, numerator, denominator, exclusions and aggregation rule. For a project example it may require contract scope, relevant work, completion event and permission status. For a staff claim it may require person, proposed role, qualification, experience period, availability and consent. Ask only for dimensions that change the answer.
The evidence object is the inspectable record. Prefer the closest authorized source: a controlled report, system export, signed acceptance, current certificate, approved reference record, test result or documented decision. Name the native format when formulas, filters, signatures or metadata matter. A cropped screenshot can help locate a dashboard, but it rarely preserves enough context to prove a calculation. A slide that quotes a number is not the underlying measurement merely because an executive presented it.
Offer bounded alternatives so the request does not stall on one unavailable file. For example: monthly incident report with definition and export date; an approved annual service review containing the same population and formula; or the record owner’s statement that no equivalent report exists. An alternative must answer the same evidence need. A customer compliment cannot replace a restoration-time dataset, and a current total cannot replace a month-by-month threshold when the claim says “each month.”
Response states
Make limiting and contrary evidence valid responses
A proposal request often contains an unstated incentive: return something the writer can use. Remove it. Tell the recipient to identify periods below threshold, changed definitions, excluded populations, missing records and known conflicts. Ask whether the candidate claim is too broad. A response that reduces “all services” to one managed platform may protect the bid from a larger unsupported statement. A response showing 92% rather than the hoped-for 95% is evidence, not poor cooperation.
Use explicit states. `supplied` means the requested object and minimum metadata arrived. `partial` names the missing dimension or field. `contradictory` preserves evidence against the candidate claim. `unavailable` states that the object does not exist or cannot be produced by the useful time. `protected` means the material exists but requires another access or disclosure decision. `wrong_owner` routes the request. None of these states means that the final claim is approved.
Do not ask an expert to manufacture retrospective support. A new explanatory memo can document how an existing process works and identify its sources; it cannot turn an unmeasured historic result into a measured one. If a calculation must be produced, record the approved method, input objects, period, exclusions, author, reviewer and generation time. The result remains a derived object and should not impersonate a contemporaneous operating report.
| State | Meaning | Next action |
|---|---|---|
| Supplied | Requested object and required context arrived | Inspect scope and decide permitted claim use |
| Partial | A relevant object arrived with a named gap | Request the missing field or narrow the claim |
| Contradictory | The source conflicts with the candidate claim | Preserve both and send the conflict to the proper review |
| Unavailable | No suitable object exists or can arrive in time | Replace, qualify where permitted, or remove the claim |
| Protected | Existence is known but access or disclosure is restricted | Use the approved review and disclosure route |
| Wrong owner | Recipient lacks custody or authority | Route to the named custodian without copying the whole pack |
Information boundary
Request the minimum material and separate access from disclosure
Give the expert enough tender context to understand the evidence need, not the entire procurement workspace. A requirement excerpt, source locator, candidate claim and scope envelope are usually more useful than hundreds of pages. Remove unrelated pricing, competitor material, personal data and customer content. If the evidence involves people, GDPR data minimization requires personal data to be adequate, relevant and limited to what is necessary for the purpose. The tender may impose additional rules, and company or customer policy may be stricter.
Separate four permissions: the proposal team may know that a record exists; a reviewer may inspect it; the writer may quote or summarize approved facts; the bidder may attach or identify the source to the buyer. A confidential service report may support an internally reviewed statement without becoming an attachment. A customer name may remain prohibited even if aggregated performance can be approved. Redaction itself needs an owner and a check that the remaining material is not misleading.
Do not move protected evidence through an ordinary chat or personal inbox merely because the deadline is short. State the approved repository, access group, naming rule and notification path. The request record can carry a controlled locator and a description of what was reviewed rather than the sensitive object. If no authorized review can occur before the cutoff, mark the claim unsupported. Urgency does not create access or disclosure authority.
Worked case
Rebuild the charge-point request around restoration evidence
The team returns to the buyer’s scoring table. It asks for the restoration method, escalation for priority incidents and evidence from comparable managed estates over the last 12 completed months. The writer splits the work into a method input and an evidence request. The evidence request proposes no customer name and no target result. It asks the operations reporting custodian for monthly priority-two restoration records covering the managed public-charge-point service, with the incident definition, population, clock start and stop rules, exclusions and export date.
The custodian explains that 98.7% measured connector availability across all hosted devices. It does not answer the restoration proposition. A separate incident report covers 286 public charge points for ten complete months. Two earlier months used another priority definition. Nine incidents paused while site owners restored mains power. The report contains site identifiers and customer details. The evidence state is `partial`, not supplied and not rejected. The discrepancy prevents the team from claiming 12-month performance on one basis.
Operations approves a narrower statement about the ten comparable months after the metric and exclusions are reviewed. The writer describes the restoration method separately and explains the boundary of the historic data without naming customers. The protected report stays in controlled review; the buyer-facing answer receives an approved aggregate and methodology note only if the tender permits that form. The original 98.7% slide is not cited. The request closes with the source link, reviewer, approved wording and the reason the broader claim was removed.
| Request element | Recorded value | Review consequence |
|---|---|---|
| Buyer need | Restoration approach plus comparable performance over 12 completed months | Method and historic proof are reviewed separately |
| Candidate claim | Priority-two restoration performance on managed public charge points | No percentage is assumed in the request |
| Preferred object | Monthly incident report with definitions, population, exclusions and export date | Availability dashboard does not substitute |
| Response | Ten comparable months; two months use another definition; protected identifiers present | State is partial and protected |
| Use decision | Approved ten-month aggregate and bounded method note where permitted | Twelve-month claim and customer names are removed |
Closure
Close the request only after review decides what the bid may use
On receipt, compare the source object with every requested dimension. Preserve title, owner, version, generation or collection time, period, population, definitions, filters, calculations, exceptions and access class. Record how the source was obtained and whether the expert supplied interpretation separately from the record. Government data-quality guidance distinguishes completeness, timeliness, validity, accuracy and consistency; a file can be complete yet inaccurate, current yet outside the needed population, or validly formatted yet irrelevant to the claim.
Route the next question to the right specialist and authority. A questionable number needs statistical validation. Uncertain company, service or period coverage needs a scope check. Old material needs a freshness decision. Two incompatible records need source-conflict review. A certificate requires certificate-specific interpretation. The evidence request ends after it produces a reviewable package and the review result is linked. It does not replace any specialist decision that the package may trigger.
Close with one of four use outcomes: approved evidence supports bounded wording; evidence supports narrower wording; another source or claim is required; or no support exists and the claim is removed or escalated. Record the final answer location, wording identifier, attachment decision, approver and conditions. Reopen the request if the buyer requirement, claim, source object, scope, period, permission or answer version changes. An inbox reply is not closure. A traceable use decision is.
What good looks like
Useful outcomes from ask subject matter expert for RFP evidence
- Each request supports one atomic proposal claim or one clearly named answer decision.
- The recipient sees the buyer wording, answer location and evaluation purpose without receiving unrelated tender material.
- Entity, service, population, geography, period and measurement basis are explicit before evidence is collected.
- The preferred source object and acceptable alternatives are named with the fields needed for review.
- Experts can answer supplied, partial, contradictory, unavailable, protected or wrong owner without being pushed toward approval.
- Personal, customer-confidential and security-sensitive material follows a minimum necessary access and disclosure route.
- Request, response, source object, interpretation, review and final use remain separately attributable.
- The deadline reflects time needed for inspection and drafting rather than the tender deadline alone.
- Unsupported wording is narrowed, qualified where permitted, replaced or removed before release.
Operating model
How to run the work
- 01
Fix the answer need
Record the current buyer requirement, response field, evaluation criterion, limit and decision that the evidence must support.
- 02
Write one candidate claim
State the narrow proposition under consideration without presenting it as true or asking the expert to endorse it.
- 03
Define the proof envelope
Name the relevant entity, service, environment, population, geography, period, metric definition and exclusions.
- 04
Route to the source owner
Find the custodian or accountable owner of the record instead of sending the question to a broad expert mailing list.
- 05
Specify the evidence object
Request the native report, record, certificate, calculation, acceptance document or other inspectable source plus required metadata.
- 06
Set access and timing
Use the approved channel, minimize protected content and set a reply time that leaves room for review, correction and approval.
- 07
Inspect the response
Compare the supplied object with the request, record gaps and contrary facts, and send specialist questions to the correct reviewer.
- 08
Close with a use decision
Link the reviewed evidence to approved wording or record why the claim was narrowed, replaced, omitted or left unresolved.
Evaluation
Questions that change the decision
- Which exact buyer proposition or scoring descriptor creates the evidence need?
- What single claim would the evidence have to support, limit or disprove?
- Which company, service edition, operating model, population, geography and period must match?
- Is the required object a source record, calculation, approval, certificate, reference, example or explanation of method?
- Who owns the underlying record, and who is merely knowledgeable about the subject?
- Which fields, definitions, exclusions and contrary observations must accompany it?
- What may the proposal team access, quote, summarize, redact or attach?
- When is the last useful reply time after allowing for evidence review and answer approval?
- What alternative treatment applies if the record is partial, contradictory or absent?
- Who decides whether the reviewed evidence permits the final buyer-facing claim?
Failure modes
Where teams lose control
The request asks for a persuasive paragraph, so the expert supplies opinion without a source.
A leading question asks the recipient to confirm a number that has not been measured on the relevant scope.
One request combines several claims with different owners, periods and acceptable evidence.
The expert sends the nearest dashboard even though its service, population or metric differs.
A screenshot or copied cell loses the report definition, filters, collection time and source owner.
The proposal deadline is used as the response deadline, leaving no time to inspect or correct the material.
Customer names, personal data, findings or private system details are distributed beyond approved need.
No-evidence and contradictory responses are treated as failure, encouraging optimistic substitutions.
The expert’s seniority is mistaken for authority to approve an external claim or disclosure.
The request closes when an attachment arrives even though the claim-use decision remains open.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- open evidence requests by answer, owner and latest useful response time
- requests containing one atomic claim and a complete proof envelope
- requests routed to the accountable source custodian on the first attempt
- responses classified as supplied, partial, contradictory, unavailable, protected or rerouted
- supplied objects with source identity, period, scope, definition and owner intact
- evidence responses received before the review cutoff
- candidate claims narrowed or removed because the response did not support them
- protected evidence handled through the approved access and disclosure route
- closed requests linked to a reviewed source and final use decision
Questions
Common questions
What should an RFP evidence request contain?
Include the buyer proposition and answer location, one candidate claim, the required scope, preferred source object and alternatives, minimum metadata, access limits, response time, reviewer and valid response states.
Should the subject-matter expert draft the proposal answer?
Not by default. The expert may explain the source and operating context. The proposal writer shapes the answer, and the relevant fact, claim and disclosure owners approve its use.
How do I avoid leading the expert toward the number I want?
Mark the claim as proposed, ask for the underlying record and explicitly invite missing periods, exceptions, contrary results and a statement that no suitable evidence exists.
Is a dashboard screenshot enough evidence?
Usually not on its own. Ask for the metric definition, population, filters, period, extraction time and accountable source. The screenshot may help locate that record.
What if the expert says the evidence does not exist?
Record that result. Find another source that meets the same need, narrow the wording, qualify only where the tender permits, remove the claim or escalate the gap to the authorized decision-maker.
When should the evidence response be due?
Set the deadline before the answer freeze by enough time to inspect scope, resolve gaps, obtain permissions, revise the response and complete approval. The tender deadline is too late.
Can restricted evidence support a proposal claim?
It may support an internally reviewed, bounded statement if access and use are authorized. Permission to inspect, summarize, quote, identify and attach the source must be decided separately.
When is an evidence request closed?
Close it when the response and source are preserved, reviewed against the request, and linked to an approved use decision or a recorded decision not to use the claim.
Sources
Primary references
- Procurement Act 2023, section 23 on award criteria and assessment methodology UK Legislation
- Cabinet Office guidance on assessing competitive tenders, updated August 2026 Cabinet Office
- Cabinet Office guidance on assessment summaries, updated August 2026 Cabinet Office
- Directive 2014/24/EU, including Articles 56, 60 and 67 and Annex XII EUR-Lex
- German GWB section 127 on award criteria and effective verification German Federal Ministry of Justice
- German VgV section 46 on evidence of technical and professional ability German Federal Ministry of Justice
- German VgV section 48 on requested suitability documents and timing German Federal Ministry of Justice
- French Public Procurement Code Article R2143-11 on participation evidence Légifrance
- French Public Procurement Code Article L2152-7, current from 22 August 2026 Légifrance
- FAR 15.204-5 on proposal instructions and evaluation factors Acquisition.gov
- FAR 15.305 on proposal evaluation and past-performance context Acquisition.gov
- World Bank Procurement Regulations, seventh edition, September 2025 World Bank
- UNCITRAL Model Law on Public Procurement, including Articles 9 to 11 United Nations Commission on International Trade Law
- W3C PROV-O recommendation on entities, activities, agents and derivation World Wide Web Consortium
- UK Government Data Quality Framework Government Data Quality Hub
- General Data Protection Regulation, Article 5 data-minimization principle EUR-Lex
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Ziva
Proposal software for source-grounded RFP, RFI, DDQ and questionnaire response work.
Bid, proposal, presales, security and compliance teams. Start with the workflow, constraints and evidence you already have.
