Sounding Without Steering: Pre-Tender Engagement That Withstands Review

Pre-market engagement is often described as a way to test the market. In practice, it is better understood as an evidence-gathering exercise. Done well, it tells a contracting authority whether its requirement is intelligible, affordable and capable of attracting competition. Done badly, it creates a paper trail that suggests the outcome was settled before the process began.

The distinction matters because the legal risk rarely arises from the fact of consultation. It arises from what the consultation produced, who was involved, and whether the authority can explain how the final documents were shaped by what it heard. Under the Procurement Act 2023 and the wider principles of equal treatment and transparency, engagement is lawful and often desirable. The discipline lies in keeping it from becoming a private channel of influence.

Engagement is an evidence exercise, not a negotiation

A common mistake is to treat pre-market engagement as an early opportunity to negotiate. Suppliers may arrive expecting to shape the requirement to their offer; authorities may leave with a clearer sense of what the market can deliver. Both outcomes are legitimate, but they are not the same. The authority is not buying in the consultation room. It is testing assumptions that will later be written into the tender documents.

That framing changes the conversation. The question is not 'what would you like us to buy?' but 'what should we understand before we specify it?' Engagement should be designed to test the feasibility of a requirement, the capacity of the market, the likely cost drivers and the risks that a specification may inadvertently create. It should not be designed to reach a consensus on a preferred supplier or a preferred solution.

Scope the questions before you open the door

Good engagement begins with a scoping note. That note should identify the purpose of the exercise, the suppliers or representative bodies being invited, the questions to be asked, the format, the timetable and the record that will be kept. It should also state what the authority will not do: it will not disclose confidential information, it will not give one participant a preview of the evaluation model, and it will not treat any discussion as a commitment.

The scope should be proportionate. A large, complex services retender may justify structured market days, written questionnaires and bilateral sessions. A straightforward goods procurement may need only a short questionnaire and a published summary of responses. The legal risk increases where the engagement is informal, undocumented and concentrated among a small group of suppliers who already hold the contract.

Record the conversation, not just the conclusion

A record that says 'market engagement undertaken; specification refined accordingly' is of little value if the authority is later asked why a particular requirement changed. The record should capture the questions asked, the responses received, the themes that emerged and the decisions taken as a result. It should distinguish between information that confirmed the authority's approach and information that caused it to change course.

Records do not need to be verbatim transcripts. They do need to be contemporaneous, attributable and intelligible to someone who was not in the room. A short engagement log, maintained by the procurement lead and reviewed by the project board, is usually sufficient. Where bilateral discussions take place, a note should be shared with the participant to confirm accuracy, subject to any confidentiality constraints.

Manage conflicts and information asymmetry

The most difficult engagement risks are not about what is said, but about what is known. An incumbent supplier will often know more about the service than the authority's own team. A supplier involved in early technical discussions may gain an understanding of the requirement that others do not have. Neither problem is fatal, but both must be managed openly.

Conflict management starts with declarations. Anyone involved in engagement who has a current or recent commercial relationship with a participant should declare it, and the authority should consider whether that person should be involved in drafting the specification or evaluating the tender. Information asymmetry is managed by publishing the substance of what was discussed. If a supplier has helped to test a technical assumption, the authority should be able to show that the resulting requirement was shared with the wider market and that no respondent received a material advantage.

Show how consultation shaped the documents

A defensible engagement record should connect the consultation to the final documents. That does not mean publishing every comment received. It means being able to explain, in summary form, which themes were accepted, which were rejected and why. A short 'you said, we did' note, published alongside the tender documents or included in the procurement file, is a practical way to demonstrate that the process was open and that the authority exercised judgement rather than merely adopting the loudest view.

Where the engagement has influenced the specification, the authority should say so. Where it has not, it should be equally clear. The danger is not that the authority changed its mind; the danger is that the change appears unexplained, or that a supplier can argue that the final requirement mirrors one participant's offering without a transparent rationale.

The predetermination line

Predetermination is rarely proved by a single document. It is inferred from a pattern: a narrow engagement group, an undocumented conversation, a specification that tracks one supplier's language, and an evaluation model that leaves little room for alternative approaches. The antidote is not to avoid engagement altogether. It is to keep the process open enough that a reasonable supplier can see how the requirement was developed and how it can compete.

Authorities should also consider the timing of engagement. Consultation that continues after the tender documents are drafted, or that runs in parallel with evaluation, invites challenge. Engagement should conclude before the procurement is launched, and the record should show that it did.

A short checklist

Before opening the door to the market, confirm that the purpose and scope of the engagement are documented; that participants have been selected on a defensible basis; that conflicts have been declared and managed; that questions are designed to test the requirement rather than to select a solution; that a contemporaneous record will be kept; and that the authority can explain how the consultation influenced the final documents. None of these steps is burdensome. Together they turn a potentially hazardous conversation into a useful and defensible piece of procurement evidence.