Zero appeals in 6 months: what complete public procurement traceability changes in the balance of power

The email arrives on a Monday morning. An unsuccessful candidate challenges the award. They request the reasons for their offer's rejection, the complete evaluation report, the detailed scores assigned criterion by criterion, and the factors that led to the selection of the chosen offer.

You have 15 days to respond. If your response is deemed insufficient, they will appeal to the administrative court.

In most local authorities we've encountered, this situation triggers the same scenario: three staff members are mobilized for two to three days to locate documents, reconstruct the decision-making trail, verify the consistency of scores with published criteria, and draft a defensible response.

Sometimes they succeed. Sometimes a document is missing. Sometimes the assigned score doesn't exactly match what the report states. And sometimes, the appeal is successful — not because the decision was flawed, but because the documentation was insufficient.

What the appeal truly reveals

A public procurement appeal is almost never a challenge to the decision itself. It's a challenge to the buyer's ability to justify it.

Public procurement law is clear on this point: the buyer must be able to demonstrate that their decisions were made in compliance with fundamental principles — equal treatment, transparency, and free access to public contracts. This demonstration is only possible if the documentary trail is complete, consistent, and accessible.

The problem, therefore, is not the decision. It's the documentation of the decision.

And in most public organizations, this documentation is produced in a scattered manner: evaluation grids in a spreadsheet, committee meeting minutes in a network folder, exchanges with candidates in staff inboxes, the presentation report in a different EDM system. When an appeal arrives, reconstructing this trail in 15 days is a perilous exercise.

Case Study: A Community of Communes, 38 Contracts, Zero Successful Appeals

A community of communes in the Grand Ouest region annually manages 38 public procurement procedures. Three staff members are responsible for public procurement. Until 2024, it faced an average of two to three challenges per year — not all formal appeals, but requests for justification that mobilized the team for days and created constant pressure on ongoing procedures.

“We spent more time justifying our past decisions than preparing for future procedures. Each request for justification was a mini-crisis — finding documents, verifying consistency, drafting a legally sound response. We did it, but it was costly in terms of time and stress.”

In 2025, the local authority deployed Optivalue.ai to centralize and query its public procurement documentation. All procedures are documented in a single system: specifications, evaluation grids, committee reports, correspondence with candidates, award decisions, notifications.

Six months after deployment: zero successful appeals. Two requests for justification handled in less than an hour each. Each response generated directly from source documents — scoring grid, page 3, criterion 2.1, score 14/20, documented reason.

“The second time we received a request for justification, we responded in 45 minutes. The candidate did not follow up. I think they understood we had everything.”

How complete traceability changes the balance of power

The balance of power between the public buyer and the unsuccessful candidate is fundamentally asymmetrical — but not always in the way one might think.

The candidate has time. They have a specialized lawyer. They have experience with multiple appeals. And they know exactly what to look for: an inconsistency between the assigned score and the published criteria, a discrepancy between the presentation report and the evaluation grid, a notification that doesn't mention all required elements.

The public buyer, on the other hand, has 15 days. Three agents. And documentation scattered across four different systems.

Complete traceability reverses this asymmetry. When every decision is documented, sourced, and accessible within minutes, the balance of power shifts. It's no longer the buyer reconstructing under pressure — it's the bidder who must find a flaw in flawless documentation.

And flawless documentation leaves no flaw to find.

The 5 documents that make a difference in case of an appeal

For any public contract, five documents form the foundation of defensibility. If they are complete, consistent, and accessible, an appeal has very little leverage.

1. The complete evaluation matrix, with scores assigned criterion by criterion for each offer and the associated justifying comments. A score without the comment is insufficient — it does not demonstrate that the criteria were applied fairly.

2. The evaluation report, which documents the procedure's progress, the candidates received, the offers analyzed, and the award recommendation. This document must be consistent with the evaluation matrix — any discrepancy can be exploited.

3. The rejection notification, which must state the reasons for rejection and the characteristics and advantages of the selected offer. An incomplete notification on these two points is the primary ground for appeal by specialized firms.

4. The Q&A log during the procedure, with proof that all questions received the same answer, distributed to all bidders simultaneously. An answer given to one bidder and not others is a violation of equal treatment.

5. The minutes of the tender committee (for formalized procedures), signed by all members, with the list of attendees and the formalized decision.

These five documents exist in all well-conducted procedures. The problem is rarely their existence — it's their accessibility and consistency with each other when they are needed.

What traceability unlocks, beyond appeals

Protection against appeals is the most visible benefit. It's not the only one.

Complete and accessible documentation also changes the preparation of future procedures. Evaluation matrices from past contracts become references for similar contracts. Q&As from previous procedures inform the drafting of the next CCTP. Documented reasons for rejection on similar offers help anticipate objections.

It's the same principle as a bid library for sales teams — applied to public procurement. The documented memory of one procedure feeds into the quality of the next.

And this is what the Grand Ouest inter-municipal community observes today: its agents spend less time justifying past decisions and more time preparing future procedures with lessons learned from completed ones.

Where to start

Three concrete actions to strengthen the traceability of your procedures starting this week.

Action 1 — Audit your most recent procedure. Check that the five key documents are present, complete, and consistent with each other. Identify any gaps — these are the vulnerabilities of your next request for justification.

Action 2 — Centralize before the next procedure. Define a single document storage system for each procedure — not five different systems. Centralization is a prerequisite for accessibility.

Action 3 — Test your response time. Simulate a request for justification for a contract awarded 6 months ago. How long does it take you to produce a complete and consistent response? This time is your real vulnerability in the face of an appeal.

**Optivalue.ai centralizes your public procurement documentation and produces responses to justification requests in minutes, sourced document by document. Dedicated private instance, hosted in France.** Request a personalized demo →

A

‍