A person-claim evidence record ties every tender assertion about one proposed individual to the exact buyer requirement, a current source, the fact that source can establish, any limitation or conflict, the person and employer confirmations required, an approved claim strength, an expiry point and a release decision.
A fictional bidder, Northmere Flood Systems Ltd, proposes Mara Ellison as telemetry integration lead for a coastal warning network. The draft says that she has eleven years of relevant experience, led four comparable live deployments, holds the required current professional registration and is available at 70% from contract start. Her CV carries the headline claims, but the project records show one lead assignment, two substantial engineering assignments and one bid-support role. The registration is current today but expires during the planned contract. A resource plan shows 80% nominal capacity, while 30% remains committed to an existing client and another 20% release is only proposed. The team needs a claim-by-claim evidence decision, not a polished biography.
A CV is an index of claims, not proof of every line it contains. Verify the individual’s own role rather than borrowing the company’s project history, distinguish present availability from a future staffing promise, and treat permission to name a person separately from the lawful basis for processing their data. The safe output is a bounded evidence record that says exactly what the bid may claim, what remains conditional and when each fact must be checked again.
Begin with the personnel test the buyer will apply
A buyer may use staff evidence for several different decisions. The evidence might establish technical or professional capacity, earn points for the people assigned to delivery, explain the proposed organization, or become a contract commitment. Those uses are not interchangeable. UK Procurement Act guidance distinguishes conditions of participation from award criteria. EU Directive 2014/24 likewise permits qualifications and experience of assigned staff as an award criterion when staff quality can significantly affect contract performance. The German and French rules cited below contain comparable routes. The tender itself decides which route applies to this procurement.
Copy the complete requirement before reviewing a CV. Include the role title, minimum and scored attributes, acceptable equivalents, reference period, location, language, estimated input, contract dates, required forms, signatures and any substitution rule. Note whether the buyer asks for one named person per role, allows a team total or assesses the bidder’s general staffing. An impressive fact can be irrelevant when it answers the wrong test.
Northmere’s coastal warning tender asks for one telemetry integration lead, at least eight years of relevant systems-integration work, evidence of leadership on three comparable live deployments, current professional registration accepted in the place of performance, and 70% input for the first four contract months. Each phrase becomes its own test. The record also captures the tender version and evaluation use, because an amendment to the start date or role definition can change the result without changing the CV.
One profile contains several kinds of claim
Break the proposed profile into atomic propositions. Identity and relationship establish who the person is and which entity can supply them. Role evidence shows the assignment proposed for this tender. Experience evidence concerns dated work and the responsibility actually performed. Qualification evidence concerns an award or current status within a defined scope. Availability evidence concerns capacity during a future window. Disclosure evidence concerns what the bid may communicate and under which controls.
Each source has a limited job. A payroll or contract record can support an employment relationship without proving competence. A project acceptance certificate can establish that the project reached acceptance without naming every contributor. A professional register can confirm current registration without proving that the person is free for this contract. A manager’s allocation approval can reserve time without validating the CV. Keep those source boundaries in the record.
Use a status for each proposition, not one green mark for the person. Direct support means the source establishes the claim at the stated strength. Supported with scope means a narrower formulation is defensible. Verification pending and source conflict keep uncertainty visible. Availability conditional, authorization missing and personal data review required identify different blockers. Claim removed prevents an unsupported line from returning through an older CV.
| Claim type | Example proposition | Useful evidence | Boundary |
|---|---|---|---|
| Identity and relationship | Mara Ellison can be supplied by Northmere for this role | Current employment or supplier record and authorized entity confirmation | Does not prove experience or capacity |
| Personal experience | She led three comparable live deployments | Dated project records naming her activities and responsibility | Company delivery alone is insufficient |
| Qualification | Her professional registration is current and in scope | Issuer record, authoritative register and credential terms | Does not prove tender-specific experience |
| Availability and commitment | She can provide 70% input from the stated start date | Dated allocation, conflict check, person confirmation and assignment approval | Planned release remains conditional |
| Permitted disclosure | The bid may submit the required profile fields | Purpose, lawful basis, notice, minimization and internal release authority | Person confirmation is not the whole privacy decision |
Use the CV to locate evidence, then test its lines
A current CV is the working index. Preserve the version received, its author or confirmer, date, intended use and relationship to the required buyer form. Split every material sentence into facts that another record can answer. “Eleven years leading critical telemetry programmes” contains a duration, responsibility level, service type and implied continuity. Those elements may need different sources.
Test chronology before adding experience. Normalize month and year, full-time or part-time status, gaps and overlapping assignments. Concurrent projects may show breadth, but the same six months are still six calendar months unless the tender expressly defines another calculation. Record relevant work rather than every job. The World Bank’s February 2025 consulting-services form, for example, asks for employment relevant to the assignment, dates, employer, title, activities, location and reference contacts, and it asks the expert to certify the CV and availability. That form is a useful concrete example, not a universal requirement.
Resolve differences with the person and the source owner. An internal biography may say “programme lead” because that was the person’s later account role, while a project chart records “integration engineer” during delivery. Preserve both records, determine the role held in the relevant period and narrow the claim if the evidence cannot support leadership. Never fill a missing month, client permission or responsibility level from memory.
Company experience cannot be assigned to a person by association
For each cited assignment, identify the customer or permitted descriptor, dates, operational setting, delivered scope, contract outcome, the person’s title at the time, activities they performed, authority they held and the source for each point. Good sources include signed role plans, project organization charts, controlled time records, authored deliverables, approval workflows, meeting decisions, client references that name the person and personnel records. Apply confidentiality and access limits to all of them.
Comparable does not mean identical. Compare the attributes named by the buyer: live public-warning operation, integration responsibility, multi-site telemetry, commissioning, cutover risk or another stated feature. Then distinguish leadership from material contribution. A technical lead who owned interface decisions may support one leadership example. An engineer who configured gateways provides relevant experience but not another lead assignment. Preparing the earlier proposal does not establish delivery work.
Northmere’s first pass changes the headline. Seaborough supports a lead claim. East Fen supports deputy leadership with responsibility for interface acceptance. Stour Gate supports hands-on integration, not leadership. Moorhaven supports no delivery claim because Mara only assisted the bid. The defensible record is one led deployment, one deputy-led deployment and one additional comparable engineering assignment. The tender requires three led deployments, so the minimum is not met on this evidence and the original sentence is removed.
| Assignment | Corporate record | Person-level evidence | Approved use |
|---|---|---|---|
| Seaborough warning network | Northmere delivered telemetry integration and cutover | Project chart, interface decisions and acceptance record name Mara as technical lead | One comparable lead deployment |
| East Fen sensor renewal | Northmere replaced gateways across 23 sites | Role plan names Mara as deputy lead responsible for interface acceptance | Comparable deputy-lead experience, not lead credit |
| Stour Gate telemetry upgrade | Northmere integrated the operational data path | Time and deliverable records show configuration and test work | Relevant engineering contribution only |
| Moorhaven resilience programme | Northmere won and delivered the programme | Bid records show Mara supported the proposal; delivery sources do not name her | No personal delivery claim |
A qualification proves only its stated scope and status
Record the exact credential name, holder, issuing body, scheme or legal basis, level, specialty, jurisdiction, issue date, expiry date, status and verification route. Use the issuer’s register or competent authority where one exists. A copied certificate can preserve an award but may not reveal suspension, expiry, renewal or scope limits. ISO/IEC 17024:2026 sets requirements for bodies that certify people and for certification schemes; it does not make every course certificate equivalent to professional registration.
Match the credential to the buyer’s wording. A degree can establish education without proving a current right to practise. A vendor certificate may cover one product version, while the tender asks for a professional authorization. A registration in one jurisdiction may not transfer to the place of performance. The European Commission’s regulated-professions database can help locate competent authorities and recognition rules, but the specific authority and procurement documents remain controlling.
Mara’s registration is verified as current on the review date and covers the discipline requested by the buyer. It expires seven months into the planned eighteen-month contract. The team may state the current status and attach the accepted evidence. It may not describe renewal as complete. If the tender requires validity throughout performance, renewal needs a dated condition, owner and check point, or Northmere must propose another compliant arrangement permitted by the documents.
Availability needs dates, arithmetic and assignment authority
State the proposed input in the buyer’s unit: percentage, days, person-months, named milestones, on-site periods or working pattern. Build the same timeline for existing client work, operating cover, approved leave, training, travel, internal duties and protected contingency. Gross capacity is not available capacity. A forecast release is evidence of a plan, while approved release is evidence of a decision.
Northmere’s resourcing system shows 80% nominal project capacity for Mara. Thirty percentage points remain committed to an existing flood-control client during the first four months. Her manager has proposed releasing another 20 points, but the client transition and internal approval have not occurred. Confirmed net capacity is therefore 50%, not the 70% stated in the draft. The extra 20% is a condition with an owner and deadline.
Availability also differs from commitment. The person confirms that the role, dates, working pattern and disclosed facts are understood and accurate. The employing entity or authorized partner confirms that it can assign the person. Follow the exact solicitation: the World Bank form cited here requires the expert and consultant representative to sign, while US federal procurements may specify letters of commitment or particular availability language. GAO decisions show that evaluators apply the wording of the solicitation and that material changes to proposed key personnel can require action. Copy the current tender rule rather than generalizing from another procedure.
| Capacity item | Percentage | Evidence state | Treatment |
|---|---|---|---|
| Nominal project capacity | 80% | Current workforce plan | Starting point only |
| Existing client commitment | -30% | Approved assignment through month four | Deduct from capacity |
| Proposed release from existing work | +20% | Transition and approval pending | Keep conditional; do not count yet |
| Confirmed net capacity | 50% | 80% less the active 30% commitment | Below the tender’s 70% requirement |
Person confirmation and data protection solve different questions
Ask the proposed person to review the exact profile that will leave the organization. They should confirm factual accuracy, the proposed role, dates and awareness of the disclosure. That control prevents surprise and catches mistakes. It does not by itself determine the lawful basis for processing employee data. The controller must record the purpose and lawful basis under the applicable law. ICO guidance warns that employment consent can be inappropriate where the power imbalance means it is not freely given.
Apply purpose limitation, minimization and accuracy. GDPR Article 5 requires those principles, and Article 6 requires a lawful basis. Include the fields necessary for the controlling form and evaluation. A tender may need name, relevant employment, assignments, education and professional status. Home address, private contact details, family information, identity-document copies, unrelated employment and full date of birth should not flow into every response merely because an old CV contains them. If a required form demands a sensitive or unusual field, restrict it to that form and route the issue to the privacy or legal owner.
Source records can contain more data than the released CV. Keep the evidence behind access controls and cite it internally by stable reference. Record recipients, transfer route, retention trigger and correction process. A client reference contact also deserves review: confirm permission or another lawful route before publishing a personal telephone number. The evidence record can prove the claim without reproducing all underlying personal data.
Release a bounded claim and keep it current until submission
The final record contains each proposition, buyer test, source, source date, verification result, limitation, person confirmation, assignment decision, privacy treatment, claim owner and reviewer. It records wording the bid may use and wording it must not use. The approved text then moves into the required CV, personnel schedule, technical answer, pricing and delivery plan through one controlled source.
Northmere cannot release the original profile. Mara’s eleven relevant years can remain if the normalized chronology supports that exact calculation. The four-lead-deployments sentence is removed and replaced by the narrower project history. Current registration can be stated with its date and renewal condition. Availability remains conditional because only 50% is confirmed. Since the tender requires 70%, the team must resolve the resource condition, nominate another eligible person if permitted, or record that the proposed profile does not meet the stated test.
Recheck at named events, not only at final proofreading. Triggers include an amended start date, extension of proposal validity, changed existing assignment, withdrawn person confirmation, altered professional status, new project evidence, role redesign or substitution. Propagate every change across the CV, organization chart, methodology, work plan, price and forms. Stop before contacting a credential issuer or reference without authority, exposing restricted records, assigning a person, promising renewal, changing employment terms, interpreting an unclear legal rule or submitting the bid.
| Proposition | Decision state | Permitted wording | Next control |
|---|---|---|---|
| Eleven years of relevant integration experience | directly_supported | Use the normalized period and relevant activity scope | Recheck if tender method or chronology changes |
| Led four comparable live deployments | claim_removed | One lead, one deputy-lead and one engineering assignment | Do not restore without new person-level evidence |
| Current professional registration | supported_with_scope | Current on the stated verification date and in the required discipline | Confirm buyer validity rule and monitor expiry |
| Available at 70% from contract start | availability_conditional | 50% confirmed; another 20% subject to approved release | Resolve before any unqualified commitment or submission |
What good looks like
Useful outcomes from prove key personnel claims in a tender
- The controlling buyer requirement, evaluation use, role, period and required evidence form
- A separate row for each identity, relationship, role, experience, qualification, availability and disclosure claim
- Person-level project evidence that distinguishes lead, contributor, reviewer and bid-only involvement
- Qualification evidence with issuer, award basis, scope, status, jurisdiction and relevant dates
- Availability arithmetic that deducts existing commitments, leave, travel, operating duties and unapproved release
- Documented confirmation from the proposed person and assignment authority from the employing or supplying entity
- A privacy decision that records purpose, lawful basis, minimization, access, retention and any required notice
- One of directly_supported, supported_with_scope, verification_pending, availability_conditional, authorization_missing, personal_data_review_required, source_conflict or claim_removed
- Approved wording, prohibited wording, owner, reviewer, evidence anchors, expiry and change triggers
Operating model
How to run the work
- 01
Fix the buyer’s personnel test
Copy the role definition, minimum conditions, scored attributes, named forms, dates, evidence instructions and replacement rules. Record whether the fact is used for participation, evaluation or contract delivery.
- 02
Split the profile into propositions
Turn identity, employer relationship, proposed role, years, assignments, activities, qualifications, registration, languages, location and availability into separate claims. Do not verify a whole CV with one status.
- 03
Collect the nearest source for each fact
Use employment records, signed project records, deliverables, client-approved roles, issuer registers, current certificates, allocation records and the person’s confirmation. Preserve source date, owner and access limits.
- 04
Test role and experience at person level
Match dates, client, project, scope, actual activities and responsibility. Separate work the company delivered from work the individual performed and remove double-counted or overlapping periods.
- 05
Verify qualification scope and currency
Check the issuing body or authoritative register where available, credential holder, level, specialty, jurisdiction, status, award date, expiry and any continuing condition. Record what the credential does not prove.
- 06
Reconcile availability and authority
Map the tender period and proposed input against confirmed commitments and non-project duties. Obtain the person’s confirmation and the employer or partner approval needed to assign them; mark planned release as conditional.
- 07
Minimize and authorize disclosure
Include only the personal data the tender and evaluation need. Record purpose, lawful basis, notice, access and retention separately from the individual’s confirmation that the facts are accurate and that they may be named.
- 08
Approve, publish and monitor the bounded claim
Release only supported wording through the required form. Keep prohibited wording, evidence anchors, approvers and expiry, then reopen after a changed assignment, credential status, tender date, role, source or person confirmation.
Evaluation
Questions that change the decision
- Is the personnel fact a condition of participation, an award criterion, a requested description or a future contractual commitment?
- Does the tender evaluate the named individual, the team as a whole or the bidder’s organizational capacity?
- Which exact activities and responsibility level make a past assignment relevant to this role?
- Does a source prove the individual’s work or only the company’s involvement in the project?
- Are overlapping assignments, part-time periods and gaps counted consistently in any years-of-experience total?
- Does the qualification cover the required specialty, jurisdiction and contract period?
- What capacity is confirmed after existing work and non-project obligations are deducted?
- Who can confirm the person’s facts, and who can authorize their assignment and external naming?
- Which personal fields are expressly required or demonstrably needed for evaluation?
- Must the claim be narrowed, made conditional, escalated for verification or removed before release?
Failure modes
Where teams lose control
Copying a company case study into a personal CV without evidence of the individual’s role
Calling contribution, review or bid support project leadership
Adding overlapping engagements to inflate years of experience
Treating a certificate image as proof of current status, scope or registry standing
Claiming availability from nominal headcount capacity without deducting current obligations
Confusing an employee’s acknowledgement with management authority to assign the person
Assuming a signature or consent statement supplies the data-protection lawful basis
Including birth dates, home details, personal contacts or identification documents without need
Letting a late personnel change leave inconsistent CVs, pricing, schedules or forms
Promising a named individual while a material qualification, availability or authorization fact remains unresolved
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.
- Percentage of material personnel propositions with a current person-level source
- Number of corporate project claims narrowed after the individual role was checked
- Percentage of credentials verified against an issuer or authoritative register where available
- Percentage of proposed input supported by dated capacity arithmetic and assignment authority
- Number of personal fields removed because the tender did not require them
- Median age of CV, availability and credential evidence at release
- Count of unresolved source conflicts or conditional availability rows at each review
- Number of post-review changes propagated to every affected bid artifact
- Personnel claims reopened before submission because a source, date or commitment changed
Questions
Common questions
Is a signed CV enough evidence for every personnel claim?
No. A signed CV is valuable confirmation by the person and may be the form the tender requires. It does not independently prove every project role, current registration, employer authority or future capacity. Link material claims to the nearest available source and retain the signed CV as one part of the record.
Can a company reference prove that a named person led the project?
Only if the reference or another reliable project record identifies that person and the relevant responsibility. A contract awarded to the company proves company involvement. It does not allocate credit among the people who sold, managed, reviewed or delivered the work.
How should overlapping projects count toward years of experience?
Do not add concurrent calendar time twice. Record the date range, workload and relevant activity for each assignment, then apply the tender’s stated calculation. If the buyer gives no method and the result affects eligibility or scoring, seek an authorized interpretation or clarification.
Does current availability mean the person is committed to the contract?
No. Availability is a dated capacity fact. A commitment also needs the individual’s confirmation, employer or partner assignment authority, a defined period and the tender’s required form. Conditional release from another project stays conditional until the authorized decision is recorded.
Can we submit a credential that expires during the contract?
Check the tender’s required validity period and the credential’s renewal conditions. State its present status accurately. Do not promise renewal as a completed fact; record renewal as a controlled condition, or propose a different compliant basis if the buyer’s rule permits it.
Should the person consent to being named in the tender?
Obtain a documented confirmation that the facts are accurate and that the person understands the proposed role and disclosure. Data protection requires a separate purpose and lawful-basis decision. Employment consent may not be freely given in every setting, so do not use a signature as a shortcut for that analysis.
What if the tender form asks for more personal data than our normal CV?
Verify that the field belongs to the controlling form and is required for this procedure. Restrict the data to that form and purpose, apply access and retention controls, give any required notice and involve the privacy or legal owner when necessity or lawful basis is unclear.
Can software mark the whole personnel profile as verified?
It can compare dates, find missing evidence, check registered status where a reliable service exists and flag conflicts. The release decision remains claim-specific. Software should not infer project leadership, create assignment authority, disclose extra personal data or convert conditional availability into a promise.
Sources
Primary references
- Procurement Act 2023, section 23: award criteria UK Legislation
- Assessing Competitive Tenders under the Procurement Act 2023 UK Cabinet Office
- Procurement Act e-learning module 6: supplier selection UK Cabinet Office
- Directive 2014/24/EU on public procurement European Union
- European Commission Regulated Professions Database European Commission
- GDPR Article 5: principles relating to processing European Union
- GDPR Article 6: lawfulness of processing European Union
- GWB section 122: eligibility Federal Ministry of Justice and Federal Office of Justice
- GWB section 127: award Federal Ministry of Justice and Federal Office of Justice
- VgV section 46: technical and professional ability Federal Ministry of Justice and Federal Office of Justice
- VgV section 58: award and award criteria Federal Ministry of Justice and Federal Office of Justice
- French Public Procurement Code Article R2152-7 Légifrance
- Order of 22 March 2019 on candidate information and documents Légifrance
- Employment recruitment and selection data-protection guidance Information Commissioner’s Office
- CNIL recruitment guidance Commission nationale de l’informatique et des libertés
- FAR 15.305: proposal evaluation Acquisition.gov
- Clear Global Solutions GAO decision B-419402 US Government Accountability Office
- World Bank Project Procurement Framework and current standard documents World Bank Group
- World Bank February 2025 RFP for consulting services, including key-expert CV form World Bank Group
- ISO/IEC 17024:2026 certification of persons International Organization for Standardization
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.
