What is the technical specification, and why respond to it point by point?
The technical specification, called the CCTP in France, is the part of the tender documents that describes the buyer's technical requirement, requirement by requirement. Responding to it point by point means addressing each requirement separately, in the order it appears, rather than countering it with a general narrative. This method serves two purposes: it proves compliance, and it makes the evaluator's job easier, since they can tick off each point as they read.
Responding to the specification with a continuous piece of prose that does not follow its structure forces the buyer to hunt for the answers; responding point by point delivers them exactly where expected.
Why is an unaddressed specification requirement a risk?
An unaddressed requirement in the technical specification is a risk because it can make the bid non-compliant. A bid that fails to meet the requirements of the tender documents is generally treated as non-compliant (in the United States, under the Federal Acquisition Regulation; in the United Kingdom, under the Procurement Act 2023). A forgotten requirement is therefore not just a missed scoring point: depending on its nature, it can disqualify the entire bid. Responding point by point is the guarantee that nothing is left unanswered.
The cost of a forgotten requirement is discovered too late, when bids are opened; point-by-point treatment makes it visible before submission.
How do you structure a point-by-point response?
Structuring a point-by-point response means matching each response to an identified requirement, with its evidence. The table links the type of specification item, the expected response, and the evidence to attach.
| Specification item | Response to give | Evidence to attach |
|---|---|---|
| Mandatory requirement | explicit, unqualified compliance | reference, document, process |
| Scored requirement | argued, differentiating response | method, resources, track record |
| Optional requirement | a proposal, if it strengthens the bid | material justifying the value |
| Ambiguous requirement | a question raised with the buyer before submission | a record of the answer received |
Reusing the specification's own numbering or vocabulary in your responses helps the evaluator find each point: form serves compliance as much as substance does.
How do you handle an ambiguous or impossible-to-meet requirement?
Handling an ambiguous requirement starts with a question to the buyer, raised within the deadline set by the tender rules, whose answer is binding on all bidders. For a requirement you cannot meet as written, it is better to say so and propose an equivalent solution than to work around it silently, because the gap will show up in the evaluation. The rule is documented transparency: a clear response, backed by the buyer's written answer, protects you better than a vague formula.
When does a general treatment suffice, and when is point by point required?
For a statement of intent or an early-stage exchange, a general treatment of the requirement is enough, because nothing is scored. For the submitted technical proposal, point by point is required: it is what demonstrates compliance requirement by requirement and earns the technical-value points. Generic AI can summarize a specification to understand it; exhaustively extracting its requirements and matching them to evidence is compliance work. The line is submission itself.
On the Optivalue.ai platform, which publishes this site, every response gets a confidence score from 0 to 100 and cites the source behind it, so the human expert can focus review on the most uncertain points.
Mistakes that lose points on the technical specification
- Responding with a general narrative: a continuous text that does not follow the requirements leaves the evaluator searching.
- Forgetting a mandatory requirement: depending on its nature, it can make the bid non-compliant.
- Asserting without proof: compliance claimed without a document or process scores poorly.
- Working around an awkward requirement: the gap shows up in the evaluation and counts against you more than an acknowledged equivalent solution.
- Ignoring the questions and answers: the buyer's answers to bidders' questions become part of the tender documents and are binding.
Frequently asked questions
Do you need to copy out every clause of the specification in your response?
Copying out the clauses is not required, but reusing their numbering or wording helps the evaluator connect response to requirement. A compliance matrix can serve this mapping purpose.
What do you do if two requirements in the specification contradict each other?
Ask the buyer within the deadline set by the tender rules. Its written answer is binding and applies to every bidder.
Can you propose an alternative to a requirement?
Only if the tender rules allow variant bids. Outside that framework, deviating from a requirement exposes the bid to being found non-compliant.
Does the technical specification, as such, exist outside France?
CCTP is a French term. In other markets, the technical requirement appears in the equivalent part of the tender documents; the point-by-point response method still applies.
Respond to a real technical specification on your own documents
Bring a real set of tender documents and its technical specification. You will see requirement-extraction coverage, sources cited on every page, and a gap analysis of your response, not a prepared demo.
Written by the compliance and presales team at Optivalue.ai. Last reviewed: 5 September 2026. This page does not constitute legal advice.
Sources cited
- Public procurement rules treating a bid that fails to meet the requirements of the tender documents as non-compliant (in the United States, the Federal Acquisition Regulation; in the United Kingdom, the Procurement Act 2023); the applicable rule in each market should be verified.