Partial-fit biddability assessment determines whether a supplier can submit an eligible, truthful and deliverable offer when current capability does not fully match the tender. It classifies each gap by formal consequence, confirms whether alternatives or qualifications are permitted, tests the feasibility and authority of any cure, and checks when compliance must exist. It does not calculate the opportunity’s overall strategic attractiveness, write future-product commitments or assume that a weighted percentage can offset a mandatory failure.
Teams say they meet 85 or 90 percent of an RFP as though requirements were interchangeable units. They are not. One missing signature, license, certification, data-residency condition or core service may prevent evaluation, while twenty minor scored weaknesses merely reduce points. Product leaders promise a feature before confirming delivery, commercial teams hide an exception in assumptions, and writers describe a manual workaround as native capability. The match percentage creates false comfort because it ignores consequence, timing, dependency and whether the buyer permits any departure.
Decide at gap level before deciding at opportunity level. Preserve the controlling requirement and classify it as participation, technical pass-fail, scored, contractual, delivery, evidence or presentation. State the exact current shortfall. Then test compliant interpretation, permitted alternative, evidence recovery, partner coverage, delivery cure, formal deviation or stop. Every cure needs an owner, proof, latest date, cost, dependency and authority. A gap is not curable because someone believes it probably will be solved. It is curable only when the resulting offer remains permitted, truthful and feasible at the required time.
Classification
Replace the fit percentage with a consequence map
Create the gap set from the controlled tender baseline, including annexes, forms, contract schedules, clarifications and portal fields. For each gap, quote or locate the requirement, state its instruction verb, mandatory language, evaluation treatment and required time. Then write the current state in falsifiable terms. “Partial fit” is not enough. “Current service exports the data daily; requirement 7.4 asks for an event within sixty seconds” defines a testable difference.
Classify consequence before discussing solution. Participation conditions and technical pass-fail requirements can stop the bid from being evaluated. Scored requirements affect competitive position but may permit a lower score. Contractual gaps may be negotiable, prohibited or acceptable only through a stated deviations process. Delivery gaps can exist even when the answer is formally compliant. Evidence gaps mean the capability may exist but the required proof is absent. Presentation gaps concern format or explanation rather than substance. Do not let labels replace the exact procurement rule.
The EU public-procurement directive distinguishes selection conditions, technical specifications, award criteria and contract performance conditions. The governing tender remains decisive, but that separation explains why a single match score is unsafe. A supplier can satisfy eligibility while offering a weaker scored feature, or have an excellent solution while failing a participation condition. Report counts by consequence and show each hard gap individually. Never say “97 percent compliant” without exposing the remaining three percent.
| Class | Primary question | Decision treatment |
|---|---|---|
| Participation or pass-fail | Can the bid be evaluated? | Must pass or have an explicitly permitted route |
| Scored capability | How many evaluated points are exposed? | Model score and differentiation effect |
| Contract | Can the obligation be accepted? | Use prescribed exception and authority |
| Delivery | Can the promise actually be performed? | Require feasible design and acceptance |
| Evidence | Can the true capability be proved? | Recover admissible current proof |
Current state
Separate missing capability, missing proof and ambiguous interpretation
Ask the accountable product, delivery or policy owner to demonstrate the current state against representative conditions. A sales statement or roadmap slide is not evidence. Record product edition, configuration, geography, environment, scale, dependencies and known failure modes. A capability available only through custom work or a third party is different from a standard function. A feature in testing is different from one approved for the proposed service. Describe exactly what exists on the date of assessment.
If capability exists but proof is missing, define the admissible record: demonstration, test output, certificate, customer acceptance, policy, operating report or signed declaration. Check recency and scope. Do not redesign the product to fix a documentation problem. Conversely, do not manufacture a screenshot or assertion to disguise a substantive shortfall. Evidence recovery should confirm an existing fact; it cannot create the fact.
Some gaps arise from interpretation. Terms such as real time, standard, local, automated, supported or equivalent may be undefined. Map the plausible readings and consequence. Search definitions and related clauses, then ask a neutral clarification through the permitted channel if the answer affects biddability. Do not choose the easiest meaning privately and present it as buyer fact. Until resolved, retain the gap as conditional and set a stop date before material response investment.
- Demonstrate the current state in the proposed configuration.
- Record conditions, dependencies and failure modes.
- Use evidence recovery only for an existing capability.
- Keep ambiguous interpretations visible.
- Set an expiry for clarification-dependent pursuit.
Treatment
Test remedies without turning them into disguised noncompliance
Use a disciplined order. First test whether a better reading of controlled documents removes the gap. Second, seek clarification where permitted. Third, test a compliant alternative that meets the same stated outcome without violating a prescribed method. Fourth, test partner or other-entity capacity under the participation rules. Fifth, test a delivery cure that will exist by the required date. Last, use a formal qualification or deviation only when the tender allows it and the authorized commercial position accepts the consequence.
A workaround must be assessed against the requirement, not against internal enthusiasm. A manual review may deliver the required accuracy but fail an automation or response-time instruction. A partner may own the capability but lack a signed commitment, permitted role, security approval or priced scope. A custom development may be technically possible but need data, architecture, testing and buyer acceptance that cannot be secured. Record the full operating and contractual effect, not merely the functional endpoint.
Do not hide deviations in assumptions, footnotes or solution prose. If the response form asks compliant or noncompliant, answer truthfully according to the buyer’s definitions. If alternatives are permitted, label the compliant base and alternative clearly. If exceptions need a schedule, reconcile it with narrative, price and contract response. A caveat placed where evaluators are unlikely to see it does not reduce the commitment; it increases misrepresentation and delivery risk.
| Treatment | Evidence required | Common failure |
|---|---|---|
| Clarified interpretation | Published buyer answer and mapped clauses | Private convenient reading |
| Compliant alternative | Outcome equivalence and permission | Changes a prescribed method |
| Partner capability | Permitted role and binding evidence | Uncommitted logo in team chart |
| Delivery cure | Plan, resources, tests and required date | Roadmap aspiration |
| Qualification | Permitted schedule and authority | Hidden caveat in prose |
Decision
Require proof of closure before calling the tender biddable
For every curable gap, record the closure state, not only activity. Name accountable owner, funded resources, technical and external dependencies, acceptance method, evidence artifact, cost, risk, latest internal decision and buyer-required date. Distinguish bid-time, award-time, contract-signature, mobilization and service-start requirements. A cure delivered after the relevant condition is still a failure. Include the cure in solution, implementation, price, risk and contract positions so it cannot remain an uncosted side promise.
Obtain approval from the authority that bears the consequence. Product may approve a development plan but not a customer commitment. Delivery must accept feasibility and operating ownership. Security or compliance owners must approve control claims. Finance must accept cost and margin. Commercial or legal delegates handle qualifications and contract exposure. The opportunity owner cannot aggregate those approvals into existence. Preserve conditions and reopen the decision when dates, scope or evidence change.
Issue the biddability decision only after reviewing every hard gap. Proceed means all hard conditions pass or possess a permitted, approved and evidenced treatment. Conditional proceed names closure evidence and a near-term expiry while limiting further investment. Hold prevents commitment until a decisive fact arrives. Stop records the failed condition and prevents sunk effort from relabelling it later. The wider bid or no-bid decision can then consider probability, economics, capacity and strategy from an honest capability baseline.
- Define closure evidence rather than a list of activities.
- Align cure date with the buyer’s required state.
- Price and contract every accepted treatment.
- Use the authority that owns each consequence.
- Stop when a hard gap lacks a permitted proven route.
What good looks like
Useful outcomes from bid when not meeting all tender requirements
- Each gap is linked to the exact requirement and its procurement consequence.
- Hard failures are not diluted by an overall fit percentage.
- Evidence gaps remain separate from missing capability.
- Alternatives, qualifications and partner solutions are used only when permitted.
- Every cure has authority, proof, cost, dependencies and a decision date.
- The final pursue or stop decision does not depend on hidden future promises.
Operating model
How to run the work
- 01
Build the gap set
Compare the controlled requirement baseline with current evidenced capability and record one precise shortfall per entry.
- 02
Classify consequence
Separate participation and pass-fail conditions from scored weakness, contract exposure, delivery risk and missing proof.
- 03
Test permitted treatments
Examine interpretation, clarification, compliant alternative, partner, evidence recovery, cure and declared qualification in that order.
- 04
Prove the cure
Require an accountable plan, acceptance evidence, cost, dependencies, authority and a date earlier than the buyer’s required state.
- 05
Issue the biddability decision
Proceed only when every hard gap passes or has a permitted, approved and evidenced treatment.
Evaluation
Questions that change the decision
- Is the apparent gap real, or does a controlled clarification change the interpretation?
- What happens if the requirement is not met: exclusion, lost score, contract exception or delivery risk?
- At what moment must the capability or evidence exist?
- Does the tender permit alternatives, equivalent evidence, partners or qualifications?
- Can a workaround satisfy the required outcome without changing an instruction?
- Who can authorize the cost, delivery work and external commitment?
- What evidence will prove the gap is closed before the decisive deadline?
- Which unresolved gap imposes a stop regardless of the remaining fit?
Failure modes
Where teams lose control
A mandatory condition may be averaged together with scored requirements.
Missing documentation may be mistaken for missing capability, or the reverse.
A manual process may not satisfy a requirement for automated or real-time behavior.
A partner may be proposed without permitted reliance or a binding commitment.
A future capability may be promised without approved scope, resources or acceptance.
A qualification may be hidden in narrative when the tender requires a deviations schedule.
A technically possible cure may arrive after bid, award or service-start need.
Closing one gap may create inconsistency in price, security, contract or implementation.
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.
- gaps classified by procurement consequence
- hard gaps with a permitted treatment
- evidence gaps closed from controlled records
- cure plans approved by delivery and commercial authority
- partner-dependent gaps backed by binding evidence
- conditional decisions closed by their expiry
- late proposal changes caused by hidden capability gaps
Questions
Common questions
Is a 90 percent fit normally enough to bid?
No percentage is enough by itself. One unmet pass-fail condition can outweigh many scored matches. Review every gap by consequence and treatment.
Can a manual workaround count as compliance?
Only when it meets the exact required outcome and method, remains permitted, feasible and properly disclosed. It cannot satisfy an explicit automation condition by renaming manual work.
Can we promise to build the missing feature?
Only if the tender permits the future state, the capability will exist by the required date, dependencies and acceptance are controlled, and authorized product, delivery and commercial owners approve the commitment.
Should a scored capability gap stop the bid?
Not automatically. Estimate the score loss, effect on differentiation, delivery implications and treatment cost. The wider qualification decision can then judge whether the opportunity remains competitive.
Sources
Primary references
- Directive 2014/24/EU on public procurement EUR-Lex
- The Sourcing Playbook UK Cabinet Office
- World Bank Project Procurement Framework World Bank
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.