Taupo Consulting All articles
Professional Services

Assurance on Loan: A 45-Day Review of Supplier Evidence in UK Tenders

Taupo Consulting
Assurance on Loan: A 45-Day Review of Supplier Evidence in UK Tenders

A supplier assurance file has a reassuring weight. It contains a certificate, a completed questionnaire, a policy or two, perhaps an insurance schedule. It is indexed, dated and stored. The difficulty is that none of those documents is a defence in itself. Each is a loan against trust, valid only while it remains current, applies to the right legal entity and matches the obligation the buyer has written into the contract. When the next tender round arrives in 2026, the question is not whether the file exists. It is whether the evidence in it can survive contact with the clauses.

The difference between a document and a defence

UK mid-market firms increasingly rely on supplier assurance material to win work and to renew it. A cyber questionnaire may sit behind a framework award; a certificate may satisfy a pre-qualification portal; a policy may be requested by a buyer’s procurement team. The risk is cumulative and quiet. A certificate issued to a parent company may not cover the trading subsidiary that will deliver the service. A Cyber Essentials certificate may be current but scoped to a single office. An insurance schedule may state a limit that is adequate in isolation but insufficient against the indemnity in the contract.

The review below is deliberately short. It is not a full audit of every supplier in the chain. It is a reconciliation exercise: evidence against requirement, entity against entity, date against date. It is designed to be completed in 45 days by a small team drawn from legal, procurement, finance and operations.

Days 1–10: Inventory the file by clause, not by folder

Most assurance files are organised by document type. That is convenient for storage and unhelpful for tendering. The first task is to rebuild the index around the clauses that create the obligation. Take the buyer’s draft contract, the framework terms or the standard questionnaire and extract the assurance requirements: information security, data protection, business continuity, insurance, anti-bribery, modern slavery, health and safety, subcontractor flow-down and any right-to-audit provision.

For each requirement, record four fields: the clause reference, the evidence currently held, the date of that evidence and the person who supplied it. The output is not a tidy file. It is a map of where the bid is exposed. Expect to find documents that are irrelevant, duplicated or held only in a shared drive with no version control. Expect also to find clauses that nobody has read since the contract was signed.

Days 11–25: Map each certificate to the legal entity and the scope

This is where many files fail. A certificate is not transferable by implication. Check the named entity on the certificate against the entity that will sign the contract and deliver the service. Check the scope statement against the services being tendered. A certification that covers software development may not cover a managed service desk. A policy that applies to a group may not bind a subsidiary without a stated adoption.

The same discipline applies to questionnaires. A completed cyber questionnaire may have been answered by a group IT function about a central estate, while the bid concerns a regional delivery unit with local systems and local subprocessors. If the buyer’s clause requires notification of material changes, check whether any have occurred since the questionnaire was signed. If the clause requires evidence of independent testing, check whether the test report is current and whether it covers the environment in scope.

The objective is not to disqualify the bid. It is to know which statements are supported and which need qualification, remediation or a different contracting entity.

Days 26–35: Test the claims that carry contractual weight

Not every assurance document deserves the same scrutiny. Prioritise the claims that could trigger a breach, a withheld payment or a failed bid. Three tests are usually enough for a mid-market review.

First, the expiry test. List every certificate, policy and insurance schedule by expiry date. A document that expires during the contract term is a live obligation, not a one-off tender requirement. Assign a renewal owner and a calendar date before the next board meeting.

Second, the consistency test. Compare what the certificate says with what the contract requires. If the contract requires a named security standard, does the certificate name the same standard and the same scope? If the contract requires a minimum insurance limit, does the schedule meet it after deductibles and exclusions? If the contract requires flow-down to subcontractors, does the supplier’s own paperwork evidence it?

Third, the sampling test. Select two or three material assertions and ask for the underlying evidence. A policy may be signed but not operated. A business continuity plan may exist but not have been tested. A modern slavery statement may be published but not cover the relevant supply chain. Sampling is not a substitute for assurance, but it reveals whether the file is a record of practice or a record of intention.

Days 36–45: Assign owners, dates and a bid/no-bid rule

Reconciliation without ownership decays quickly. For each gap, record an owner, a remediation action and a date. Distinguish between gaps that can be closed before the next tender submission and gaps that require a contractual qualification. A bid team that knows the difference can make a disciplined bid/no-bid decision rather than discovering the problem at the clarification stage.

There is also a governance point. The board does not need to review every certificate. It does need to know which assurances are material to revenue, who is accountable for them and when they expire. A one-page assurance register, reviewed quarterly, is usually sufficient. The register should show the clause, the evidence, the entity, the expiry date and the owner. If a certificate cannot be mapped to a clause, it is decoration.

The questions a board should ask before the next tender

Three questions are worth putting to management before the 2026 tender round. Which live bids depend on assurance evidence that expires before contract signature? Which certificates name an entity or scope that differs from the delivery entity? And which contractual assurances have no named owner in the business?

The answers will not always be comfortable. They will, however, be more useful than a well-indexed file that nobody has tested. Supplier assurance is not a library. It is a set of promises, and promises need to be kept current.

All Articles

Related Articles

The Forty-Seven Days You Lend for Free: A 30-Day Working Capital Sprint

The Forty-Seven Days You Lend for Free: A 30-Day Working Capital Sprint

The Unmapped Deputy: Stress-Testing Key-Person Dependency in Founder-Led Firms

The Unmapped Deputy: Stress-Testing Key-Person Dependency in Founder-Led Firms

What the Proposal Promised: Reconciling Sales Language With Delivery Reality Before 2027

What the Proposal Promised: Reconciling Sales Language With Delivery Reality Before 2027