A confidential clarification decision identifies each item that could be disclosed, the reason protection is requested, the exact buyer rule, the permitted communication route and the bidder response if protection is refused. It treats bidder identity, question wording, attachments and the buyer answer as separate objects. It does not promise secrecy, convert a portal label into a legal determination, or hide information that competing suppliers need to bid on the same basis. This is a procurement control, not legal advice.

A regional transport authority is buying a replacement ticketing back office. One requirement asks the system to reconcile offline validations within an undefined recovery window. A bidder can explain the ambiguity only by referring to a retry method developed for its existing platform and a royalty threshold in a third-party licence. Publishing the raw question would reveal the design choice and a cost floor. Keeping the entire exchange private, however, could give that bidder an answer about the common performance requirement that every competitor needs. The portal offers a field marked confidential, but the instructions say the authority decides whether the request can be treated privately and may invite the bidder to withdraw it.

Do not classify a whole question with one confidential flag. Split the exchange into bidder identity, common procurement issue, bidder-specific premise, supporting material and expected answer. Protect only the specific material for which there is a credible basis and disclosure harm. Give the buyer a neutral version of the common issue whenever possible. Use the route and justification required by the current tender documents, wait for the buyer’s determination, and decide in advance whether to withdraw, redact, authorize publication or stop. A protected channel reduces exposure; it does not create a private right to procurement information.

A clarification contains more than one thing that can be disclosed

The word confidential is too blunt for a clarification record. A portal can conceal the name of the company while showing the complete question to every participant. The buyer may protect an attachment but publish a shortened account of the issue. It may answer privately and later issue a public amendment containing the part that affects the common tender. Record these as different outcomes rather than one yes or no field.

Start with five objects: bidder identity, question wording, supporting material, buyer response and resulting procurement change. Add the information owner and intended audience to each. The ticketing bidder owns its unpublished retry method, but the royalty condition belongs to a licensor and may require separate consent. The authority owns its answer. A changed recovery requirement belongs in the common procurement record even if a private premise caused the question.

Anonymity deserves its own state. Removing the company name prevents direct attribution, but distinctive products, territories, contract history, customer references or design vocabulary can identify the bidder. The public wording therefore needs a fingerprint review. Ask what a knowledgeable competitor could infer from the text, not whether the sender field is hidden.

Objects in one clarification exchange
ObjectPossible treatmentEvidence needed
Bidder identityNamed to buyer, anonymous to participants, or publishedPortal behavior and buyer instruction
Question wordingPrivate, published unchanged, or published in a sanitized formBuyer determination and approved public text
Supporting materialWithheld, restricted, redacted, summarized, or not submittedOwner, protected passage, basis and access group
Buyer responsePrivate answer, common answer, or no answerFormal response and procedure rule
Tender changePublished amendment or revised documentOfficial version, date and affected deadline

The tender instructions decide what the confidentiality label can do

Read the live notice, invitation, clarification schedule, portal help and later amendments together. Extract the normal publication rule, treatment of bidder names, method for requesting confidentiality, required justification, decision maker, response time and available fallback. Some instructions allow the bidder to withdraw after a refusal. Others treat submission as consent to circulation. A generic company policy cannot replace the procedure chosen by the buyer.

Current UK procurement law supplies a boundary, not a private clarification service. Section 12 of the Procurement Act 2023 requires equal treatment in covered procurements and current Cabinet Office guidance links equal treatment with timely information sharing. Section 94 permits information required by the Act to be withheld where it is sensitive commercial information and an overriding public interest supports withholding. The authority applies that test. A bidder cannot produce the outcome merely by typing confidential in a subject line.

Current tender instructions show how that distinction works in practice. A 2026 invitation on Find a Tender states that responses normally go to all tenderers, the authority decides a confidentiality request, and the tenderer may withdraw if the request is refused. Another published instruction allows the authority to circulate a general issue even where the bidder-specific request is withdrawn. Follow the exact procurement in front of you; examples from other competitions explain possible designs but do not amend your tender.

Describe the protected information and the harm with precision

Identify the smallest passage that needs special treatment. “Our question is commercially sensitive” gives the buyer little to assess. A usable request might identify lines 6 to 11 of an attachment as an unpublished retry sequence, name the supplier that controls it, state that competitors could reproduce the method, and request that the authority use only a neutral summary in any shared response. Keep the unmarked remainder available for ordinary handling.

If the claim is a trade secret, test the elements rather than borrowing the label. The UK Trade Secrets Regulations define a trade secret by secrecy, commercial value because it is secret, and reasonable steps to keep it secret. Evidence might include limited access, contractual restrictions, version history and the absence of public disclosure. A public product manual, a known industry method or a figure already included in marketing material is a weak candidate.

Other grounds need their own analysis. Personal data, security information, legal professional privilege and third-party contractual confidentiality are not interchangeable with trade secrets. Record the basis without claiming that one automatically proves another. Where legal meaning or a disclosure obligation is material, obtain qualified advice under the applicable jurisdiction and timetable.

Evidence for a narrow protection request
Question for the bidderUseful evidenceWeak assertion
What exact information is protected?Passage, cell, diagram layer or attachment identifierThe whole message is confidential
Who controls it?Named supplier, licensor, partner or customer plus authorityIt came from the bid team
Is it secret now?Public-source check and current access limitsCompetitors probably do not know
What harm would disclosure cause?Specific lost advantage, exposed price floor or contractual breachDisclosure would be bad
How has it been protected?Access record, agreement, marking practice and controlled copiesWe consider it proprietary

Give the buyer a common question without handing over the private premise

The common issue in the ticketing procurement is the undefined recovery window. Every bidder may need that value to size its design and price. The private premise is that one bidder plans a particular retry sequence and faces a licence threshold at a certain transaction volume. Ask first: “What maximum period may elapse between restoration of connectivity and completed reconciliation of offline validations?” That question can be published without the method or cost floor.

Some issues cannot be separated cleanly. The authority may need to inspect an interface trace to understand why two requirements conflict, or a customer contract may restrict the only evidence available. Prepare a layered package: a public question, a private note explaining why further detail exists, and a narrowly redacted attachment offered only if the procedure accepts it. State that the attachment is not required for other bidders to understand the common question.

Do not use separation to hide a bidder-specific concession. If the supplier wants permission for a design that does not meet the stated requirement, the authority needs enough information to classify the request accurately. A neutral public question may ask whether alternatives are permitted, but the private package cannot create a different compliance standard for one bidder. If the answer changes the requirement, request an official common clarification or amendment.

Make a narrow request that the buyer can accept, refuse or modify

Use the portal field, message type, email address or form specified by the current instructions. Put the procurement identifier and question identifier in the required place. In the protection request, name the precise text or attachment, proposed audience, reason, expected duration and disclosure consequence. If the information belongs to another party, attach or record its authorization where the procedure permits. Never send the sensitive material first and negotiate treatment afterward.

Offer a workable public substitute. The buyer may be able to publish the neutral question and common answer while keeping the proprietary annex restricted. It may publish a short account that removes a price or method. It may also decide that answering privately would disadvantage other bidders. A proposed substitute helps the authority protect what matters without suppressing the information needed for equal bidding.

Define the fallback in the same internal approval. For example: accept publication of the neutral text; do not authorize publication of annex A; withdraw if the buyer cannot restrict annex A; refer any request for the royalty figure to legal and commercial owners. The sender should not have to invent the company’s risk tolerance while the buyer’s deadline is running.

A protected route stays pending until the buyer confirms the treatment

A successful upload proves receipt, not confidentiality. Keep the request pending until an authorized buyer response identifies what will remain private, what may be shared, and what happens next. Silence, a closed padlock icon or an unread message does not supply that decision. If the instructions set no determination time, ask a procedural question early enough to preserve the clarification deadline.

The buyer may accept the request in full, accept only a passage, propose a neutral publication, refuse and permit withdrawal, refuse without a revision route, or decline to answer. Capture the exact words and deadline. A private answer also needs a fairness check: if it defines the common recovery requirement, ask the authority to issue the necessary common clarification without the protected premise.

Do not broaden a narrow acceptance. Permission to send one restricted attachment does not make later messages confidential. Approval to hide identity does not cover question wording. A promise to consult before release under freedom of information rules does not guarantee that release will be refused. Apply each decision only to the object, audience, purpose and period it names.

Response to the buyer’s determination
Buyer responseBidder actionStatus to retain
Accepted in fullSubmit only the approved version and audienceProtected treatment confirmed
Accepted in partRemove or separately authorize the refused materialPartial protection with exact scope
Neutral publication proposedCompare word for word and approve or correctPublic substitute pending approval
Refused with withdrawal optionWithdraw, sanitize or consent before the stated timeFallback decision required
No decision or no answerDo not infer protection; follow the procedure or stopUnresolved and not safe to release

Refusal creates a bid decision, not permission to find a side channel

Use the fallback approved before submission. Withdrawal preserves the information but leaves the ambiguity unresolved. Sanitization may keep enough substance for a common answer. Consent to publication may be acceptable if the disclosed competitive harm is smaller than the risk of bidding on an unknown requirement. The final option is not to ask and to record an approved assumption, qualification or bid decision where the tender permits it.

Time controls the available branch. A withdrawal right can expire quickly, while the main clarification deadline may close before a redraft is approved. Record the buyer time and the internal decision time separately. If the issue affects legal rights, regulated data, security or a material contract exposure, route it to qualified counsel or the accountable specialist without representing this guide as a substitute.

Do not call the project contact, use a previous contract relationship or ask an intermediary to obtain the same answer privately. That can breach the communication instructions and create unequal information. If the published process cannot accommodate the issue, request a procedural remedy through that process or base the commercial decision on the unresolved state. The absence of a safe answer is information the bid decision must carry.

Keep the determination, fallback and publication outcome together

The final record should let a reviewer reconstruct what the team knew before transmission. Keep the current instruction and version, each disclosure object, owner, claimed basis, requested treatment, approved public substitute, internal authority, buyer receipt, determination, deadline and executed fallback. Link the exact sent file rather than a working draft. If the buyer edits the question, preserve both texts and the approval of the published form.

Monitor the official question log and amendments until the issue closes. Check whether the bidder name remained hidden, whether the question was shortened accurately, whether an attachment or identifying detail appeared, and whether the answer created a common change. Escalate an unexpected release promptly through the procedure and qualified advisers. Do not erase the evidence that shows what was authorized.

Close only when the publication state is known and every bid consequence has an owner. The common answer may change architecture, price, delivery, risk or compliance. The private premise may remain restricted. Those two results can coexist. A defensible record preserves both without pretending that confidentiality made the procurement consequence private.

Minimum confidential clarification decision record
FieldRecordClosure evidence
Procedure basisDocument, clause, version, route and deadlineCurrent source retained
Disclosure objectsIdentity, wording, material, answer and changeFinal state for each object
Protection claimOwner, passage, basis, evidence, harm and durationOwner approval and buyer decision
Fallback authorityWithdraw, sanitize, publish, escalate or stopExecuted option and timestamp
Publication outcomePublished text, answer, amendment and audienceReconciliation and affected owners

Useful outcomes from confidential tender clarification question

  • Every proposed clarification has separate disclosure states for identity, wording, attachments and answer.
  • Each protection request identifies the exact passage, information owner, claimed basis and likely harm from disclosure.
  • The common procurement fact is separated from the bidder-specific method, economics or customer evidence.
  • The team uses only the buyer’s stated channel, deadline, label and supporting format.
  • The buyer’s decision is recorded as pending, accepted in full, accepted in part or refused rather than inferred from silence.
  • The bidder has an approved response for publication, sanitization, withdrawal, escalation or non-submission.
  • No unofficial side conversation is used to obtain an answer unavailable to other suppliers.
  • Published wording and answers are reconciled against the approved version and applied to the bid.
  • Third-party information is not disclosed without the authority needed from its owner.

How to run the work

  1. 01

    Read the clarification and disclosure rules

    Locate the current tender instructions, portal guidance, confidentiality clause, publication rule, question deadline and any right to withdraw or revise a question.

  2. 02

    Split the exchange into disclosure objects

    Record the bidder identity, exact question text, supporting facts or files, buyer answer and any resulting amendment separately.

  3. 03

    Test the claimed confidential information

    Identify what is not public, who controls it, why secrecy has commercial value or another protected basis, and what specific harm disclosure would cause.

  4. 04

    Extract the common procurement issue

    Rewrite the buyer-controlled uncertainty without the proprietary method, price threshold, customer identity or other premise that is not needed for a fair answer.

  5. 05

    Prepare a narrow protection request

    Name the exact field or attachment, requested treatment, justification, proposed public substitute and acceptable fallback under the buyer’s procedure.

  6. 06

    Obtain internal release authority

    Secure approval from the information owner and the people accountable for legal, commercial, technical and bid consequences before transmission.

  7. 07

    Submit and wait for a determination

    Use the authorized channel, preserve the receipt and treat the request as unresolved until the buyer confirms what will remain private.

  8. 08

    Execute the approved fallback and close

    Withdraw, sanitize, consent to publication, seek qualified review or decline to ask as authorized, then reconcile any published question, answer or amendment.

Questions that change the decision

  • Which tender document and version controls confidentiality and clarification publication?
  • Does the portal hide the bidder’s name, the question text, the attachment, the answer or only some of them?
  • What exact words, figures, diagrams or files are claimed to need protection?
  • Is the information already public, generally known in the market or readily inferred from the supplier’s published offer?
  • Who owns the information and who may authorize its disclosure to the authority?
  • What commercial, legal, security, privacy or contractual harm would follow from the stated audience seeing it?
  • Can the buyer answer the common requirement after the private premise is removed or summarized?
  • Would a private answer give this bidder material information that other suppliers need?
  • Does the procedure let the bidder withdraw or revise the question if confidentiality is refused?
  • Who can authorize the final fallback before the question deadline expires?

Where teams lose control

01

A team mistakes removal of its company name for protection of the strategy visible in the wording.

02

The entire question is marked confidential without identifying any protected passage or disclosure harm.

03

A trade secret claim is made for information that is public or has not been subject to reasonable protective measures.

04

Third-party customer, partner or licensor information is sent without permission from its owner.

05

The bidder receives a private interpretation of a common requirement and relies on it even though competitors were not informed.

06

A buyer publishes the question after a warning because the bidder failed to withdraw it in time.

07

The team assumes silence means acceptance of confidentiality and sends an attachment with irreversible detail.

08

An unofficial call or email creates no reliable decision about treatment and breaches the prescribed communication rule.

09

Over-redaction removes the premise needed for the authority to understand the issue and produces a misleading answer.

10

A later freedom of information request is treated as though the bidder’s original marking guarantees an exemption.

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.

  • Clarifications with separate identity, text, attachment and answer disclosure states
  • Protection requests tied to a current tender clause and authorized channel
  • Claims that identify a specific protected passage, owner, basis and disclosure harm
  • Questions with a buyer-usable public substitute prepared before submission
  • Buyer confidentiality decisions recorded before sensitive material is relied upon
  • Refused requests resolved before the buyer’s withdrawal or clarification deadline
  • Published questions that differ from the approved public version
  • Private answers containing common procurement information escalated for buyer confirmation
  • Closed items with receipt, determination, fallback authority and publication check

Common questions

Does marking a clarification confidential guarantee private treatment?

No. The mark normally asks the buyer to assess the request under the tender rules and applicable law. Record the buyer’s explicit determination before treating any material as protected.

Is an anonymous clarification the same as a confidential one?

No. Anonymity may hide the sender field while the full question and answer remain visible. Distinctive wording, facts or product details can still identify the bidder or reveal its strategy.

Who decides whether the question can stay private?

The contracting authority applies the procurement documents and applicable rules. The bidder identifies the material, provides its justification and decides how to respond if the requested treatment is unavailable.

Can the buyer publish part of a confidential issue?

Yes, where the procedure and law permit. The buyer may protect the bidder-specific premise while sharing the common requirement, neutral substance or amendment needed for equal treatment.

What should the justification contain?

Identify the exact passage, owner, current secrecy, claimed basis, protective measures, likely disclosure harm, requested audience and period. Add a public substitute if one can answer the common issue.

Can we withdraw the question if confidentiality is refused?

Only when the current tender procedure or buyer decision permits it. Preserve the deadline and the withdrawal confirmation. Do not assume a right found in another authority’s instructions applies here.

Does a private buyer answer change the tender for our bid?

It may inform the bidder, but a material common requirement should have an official basis that applies fairly to the competition. Ask the authority to publish the necessary neutral clarification or amendment.

Can a freedom of information request override our marking?

The authority applies the relevant disclosure law and any public-interest test. A supplier marking can support that assessment but does not guarantee an exemption. Obtain qualified advice for a material case.

Primary references

Tony Kim

Tony Kim

Founder and CEO

Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.

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.