A tender clarification assignment and approval record identifies one person who is accountable for taking a selected question to a final disposition. It then names the specialists who supply facts, the authorities who approve the consequences within their remit, the person who may authorize release, and the operator who may use the buyer’s designated channel. The record binds every approval to a specific wording version, source issue, lot and disclosure boundary. Ownership is responsibility for closure. It is not automatic permission to decide a legal position, accept commercial exposure or contact the buyer.
A regional housing provider is procuring repairs and compliance services across four lots. The bid team has selected six clarification questions. One concerns access to occupied homes containing known asbestos, one asks which employee data will be supplied for a possible workforce transfer, and another addresses conflicting indexation dates in the pricing schedule. All six sit in a shared spreadsheet under “Bid team.” The safety lead believes legal will send the asbestos question. Legal expects the solution lead to resolve it. Finance comments on an older price question while the bid manager shortens the current draft. On the morning of the buyer’s cutoff, nobody can show who owns each question, which version was approved or who is permitted to release it.
Assign accountability at question level, then route approval according to the decision or exposure created by the answer and by the disclosure itself. A technical specialist validates technical truth. Legal approves a legal interpretation or contractual position. Finance or commercial authority accepts price and margin consequences. A privacy or information owner controls personal or confidential material. The bid lead checks that the question remains necessary, neutral and consistent with the pursuit. A named release authority decides whether the exact version may leave the organization. Work backwards from the official cutoff, require affirmative decisions and reopen approval after a material change.
Accountability
Give one person responsibility for closing the question
A question owner is the person who must move one selected clarification from its current state to a recorded outcome before the internal deadline. That person confirms the source issue, obtains specialist input, makes sure the correct authorities decide, protects the approved wording from accidental change and records whether the question is released, merged, withdrawn or blocked. The owner does not need to write every sentence or possess every decision right.
Use a person’s name, not “Legal,” “Solution,” “Consortium” or “Bid team.” A functional mailbox may receive notifications, but it cannot notice that two reviewers are waiting on each other. Naming one owner also exposes load. If one bid manager owns forty questions due on the same afternoon, the assignment is visible as a capacity problem rather than hidden inside a shared list.
Ownership begins only when the person accepts it with the question identifier, required outcome and deadlines. Forwarding a spreadsheet or mentioning a name in a meeting is not acceptance. If responsibility moves, record the reassignment time and the new owner’s acceptance. Keep the earlier history so the team can explain delay and recover the next action.
Role design
Separate ownership, expertise, approval and release
Four jobs are often collapsed into one ambiguous “responsible” column. The question owner drives closure. A contributor supplies or validates a bounded fact. An approver makes a decision within delegated authority. The release authority confirms that the assembled question may leave the bidder. A fifth role, the sender, performs the authorized channel action. One person may hold more than one job in a small organization, but the jobs should still be recorded separately.
A safety engineer can confirm that the asbestos access wording would alter the planned method. That expertise does not necessarily authorize contractual acceptance of the access risk. Counsel can approve the legal position without validating the proposed method or its cost. The bid director can confirm that the question remains consistent with the pursuit, but cannot approve an unbudgeted price exposure unless the company’s delegation says so.
The release authority reviews completeness rather than repeating every specialist judgment. It verifies that the right people decided, their conditions are reflected, the wording version is fixed and the timing remains valid. Channel operation remains separate because access to a portal or buyer mailbox is a technical capability, not proof of authority to communicate.
Decision rights
Route approval by consequence, not by the question’s label
A question about a technical schedule may have a commercial consequence. A staffing-volume question may expose personal information. A short query about a contract definition can change the delivery design. Route approval from the plausible answers and disclosed context, not from the folder in which the question was first logged. Record each material consequence and the authority that owns it.
Use explicit triggers. Legal approval is required when wording states or implies a legal interpretation, exception, reservation, liability position or employment consequence. Commercial or finance approval is required when an answer can cross an approved price, margin, cash or indexation boundary. Safety, security, privacy and regulated-service questions go to the authority for that exposure. A consortium member approves any fact, undertaking or disclosure that belongs to its entity unless the consortium agreement has delegated that power clearly.
Not every question needs every function. A pure request for a missing drawing may need the engineering owner and bid release authority only. Adding legal and executive reviewers to every item slows the route and weakens attention. Conversely, seniority is not a substitute for the correct remit. The chief executive may approve the pursuit while the data protection lead remains the proper authority for including personal data.
| Trigger in the question or plausible answer | Required authority | What that decision covers |
|---|---|---|
| Technical method, performance or feasibility | Technical or operational authority | Accuracy, feasibility and permitted technical position |
| Contract meaning, reservation, liability or workforce duty | Legal or contracts authority | Legal position and permitted external wording |
| Price, margin, indexation, cash or financial capacity | Commercial or finance authority | Financial boundary and acceptable consequence |
| Personal, security-sensitive or confidential information | Privacy, security or information owner | Need, minimization and permission to disclose |
| Partner fact, commitment or identity | Authorized partner representative | That entity’s fact and commitment only |
| Bid or no-bid gate or exceptional exposure | Delegated pursuit or executive authority | Whether the pursuit may continue under the stated boundary |
Version control
An approval covers one identifiable version, not a topic
“Approved the TUPE question” is too weak. The decision should identify the question number, wording version, procurement and lot, source baseline, disclosed facts, attachments and any approval conditions. A timestamp and decision maker make the record usable. A content hash or controlled revision identifier can help, but the approver must still be able to read the exact text covered by the decision.
Define the changes that reopen approval. A spelling correction that cannot change meaning may follow a documented minor-edit rule. Adding a figure, changing “calendar days” to “working days,” broadening the lot, quoting a partner or replacing a neutral request with an assumption is material. Reopen the affected technical, legal, commercial or disclosure decisions as well as release authorization. Do not erase the superseded approval.
Batch approval is acceptable only when each question remains independently inspectable. The decision record must show which items were approved, approved with conditions, rejected or left open. One signature on a PDF containing twenty questions cannot turn a blank status or an unresolved comment into consent. If the batch changes after sign-off, identify the changed items and reopen them rather than recirculating an indistinguishable file.
Timing
Build an approval clock backwards from the official cutoff
The buyer’s question cutoff is an external constraint, not the team’s drafting deadline. Work backwards through channel handoff, release review, domain approvals, wording freeze and contributor input. The intervals depend on the portal, time zone, question volume and availability of decision makers. Preserve the official cutoff exactly as verified elsewhere and state the internal times separately so nobody mistakes a management buffer for a buyer rule.
Give each approver a decision deadline, not only a meeting invitation. The request should include the exact decision required, relevant source, plausible consequences, current wording and what happens if approval is withheld. A legal reviewer asked to “take a look” cannot know whether the team needs factual correction, legal advice or permission to release by 15:00.
Set an escalation time earlier than the point at which no safe action remains. Escalation can appoint an authorized replacement, narrow the question, withdraw it or revisit the underlying bid decision. It cannot invent authority. Until the buyer officially changes a deadline, continue to plan against the published cutoff. A question that misses internal approval remains unsent even when someone has technical access to the channel.
Resilience
Prepare for absence without creating pretend authority
A deputy needs a defined scope, effective period and source of delegation. The record should show whether the deputy can provide facts, approve a risk, authorize release or send through the channel. Access to the same documents and current comments is also necessary. Naming a deputy who cannot see the evidence or whose financial limit is too low only postpones the failure.
Small teams do not need a ceremonial chain of reviewers. They do need clarity when one person holds several roles. Record that the founder is both commercial authority and release authority, for example, while a qualified engineer validates the safety fact. Where independence is important but no second internal person exists, use the organization’s authorized external adviser or record the compensating review. Never manufacture a second approval that carries no decision right.
For consortium and subcontractor questions, the lead bid team can coordinate the clock and final draft. It cannot silently approve another entity’s confidential data or commitment. Name the partner authority, the exact fact or undertaking it controls and the deadline. If the partner misses it, hold or remove that content and reassess the question. Do not let a broad coordination clause stand in for entity-specific power.
Control record
Keep the matrix short enough to decide from
The clarification record needs the procurement and lot, current source version, question identifier, unresolved fact, buyer-facing wording version, accountable owner, contributors, approval triggers, named authorities, decision deadlines, conditions, release authority, permitted sender, current state and next action. Link supporting analysis rather than pasting an entire legal or technical review into the matrix.
Use states that describe evidence, not optimism: assignment incomplete, input pending, approval pending, blocked by missing authority, approved for release, withdrawn, superseded or expired. “Green” is not enough when one legal condition remains open. Approved for release means every required affirmative decision covers the same current version. It does not mean the question has been transmitted or received.
Keep public procurement rules within their jurisdiction. UK record-keeping duties, German documentation rules, French electronic-communication provisions, EU principles, US federal rules and development-bank procedures govern different actors and scopes. They demonstrate why controlled questions and records matter, but they do not create one universal bidder approval chart. The tender documents, applicable law, corporate delegations and partner agreements determine the actual authorities.
| Field | Required entry | Release test |
|---|---|---|
| Identity | Procedure, lot, question ID, source and wording version | All decisions point to the same item |
| Ownership | Named owner, acceptance time and authorized deputy | One person owns closure |
| Inputs | Named contributor, requested fact and due time | Necessary facts are present and current |
| Approvals | Trigger, authority, decision, conditions, time and version | Every material consequence has an affirmative decision |
| Release | Release authority, decision and expiry | This exact wording may leave the bidder |
| Handoff | Authorized sender, verified route and handoff time | Release and channel operation remain distinct |
| Disposition | Current state, next action and effect if unsent | No question or underlying issue disappears |
Worked case
Six shared questions become six owned decisions
In the fictional housing-repairs procurement, the bid manager assigns Q-14 on asbestos access to the mobilisation lead. The safety engineer validates the operational fact; legal approves the proposed contract interpretation; the commercial director accepts the cost boundary; and the bid director holds release authority. Q-22 on workforce data belongs to the people-transition lead, with employment counsel and the privacy lead as separate authorities. Q-31 on indexation belongs to the pricing lead and requires finance plus contract approval. The other questions receive their own routes rather than inheriting these reviewers.
The matrix records a buyer cutoff of Monday 12:00 and an authorized-sender handoff at 10:30. Domain approvals are due Friday 14:00, release decisions at 16:00. When finance approves Q-31 version 3, the decision covers the two stated index dates and no volume assumption. The bid manager later adds an annual value to explain the consequence. That disclosure is material, so the commercial and release approvals reopen. The old decision stays visible as superseded.
At 09:00 on Monday, Q-14 and Q-22 are approved for release. Q-31 remains blocked because the commercial deputy’s delegation does not cover the exposure. The bid director withdraws Q-31 from the send set and reopens the pricing assumption and bid decision. The sender receives only Q-14 and Q-22 with their fixed versions and verified channel record. No one treats the missing Q-31 approval as consent, and the unresolved indexation issue remains visible in the offer work.
What good looks like
Useful outcomes from tender clarification approval process
- Every selected clarification has one accountable question owner rather than a team or department.
- Fact contributors and decision authorities are named separately.
- Approval is triggered by technical, legal, commercial, privacy, partner or corporate consequences.
- The release authority can see the exact wording, source issue, disclosure boundary and affected bid decisions.
- Each approval records the approver, decision, time, scope, conditions and question version.
- Internal milestones leave usable time before the buyer’s official question cutoff.
- A deputy acts only under recorded authority and receives the same controlled material needed for the role.
- Missing approval produces a visible hold, escalation or withdrawal rather than approval by silence.
- The authorized sender receives only questions that are approved for release through a separately verified channel.
Operating model
How to run the work
- 01
Freeze the question identity
Record the procurement, lot, question identifier, source issue and current wording version before assigning responsibility.
- 02
Name one question owner
Choose the person accountable for inputs, decisions, timing and final disposition. Record acceptance and a deputy where formal authority exists.
- 03
Route specialist input
Ask named contributors for the facts within their competence. Do not turn consultation into shared accountability.
- 04
Identify approval triggers
Map the question and plausible answers to compliance, safety, legal, price, delivery, privacy, partner and corporate authority.
- 05
Approve the exact version
Capture an affirmative decision against the actual buyer-facing wording, source, scope and permitted disclosure, including any conditions.
- 06
Authorize release separately
Have the designated authority confirm that all required decisions are present and that this version may be handed to the authorized sender.
- 07
Control change and expiry
Reopen affected approvals after material wording, source, lot, consequence or timing changes. Expire the release when its conditions no longer hold.
- 08
Close every unsent item
Record withdrawal, merger, missed authority or escalation explicitly so an unresolved question cannot disappear from the bid.
Evaluation
Questions that change the decision
- Who is personally accountable for closing this question?
- Which facts require a named technical, operational, pricing or evidence contributor?
- Which plausible answer could change compliance, safety, contract, price, margin, delivery or the bid decision?
- Does the question disclose personal data, confidential information, partner identity or private bid strategy?
- Which person holds delegated authority for each material consequence?
- Who may authorize release and who may operate the official communication channel?
- What exact wording version and source baseline does each approval cover?
- Which changes are material enough to reopen approval?
- What is the last internal decision time that preserves a safe handoff before the buyer cutoff?
- What happens if the owner, approver or sender is unavailable?
- How will a deferred or withdrawn question affect the underlying bid decision?
Failure modes
Where teams lose control
A department name appears as owner, leaving no person accountable for closure.
The most senior reviewer is asked to approve matters outside their competence or delegation.
The writer, approver and sender use different versions of the question.
A technical approval is mistaken for acceptance of legal or commercial consequences.
A question reveals employee, customer, partner or pricing information without the proper disclosure decision.
An approver’s silence is treated as consent as the cutoff approaches.
A deputy is named but lacks the authority, evidence or channel access needed to act.
Batch sign-off hides one question whose conditions or required approver remain open.
A small team adds ceremonial reviewers while no one holds the necessary decision right.
A late wording edit changes the requested rule after approval.
The question is not sent, but the affected assumption quietly enters the offer.
Measurement
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.
- selected questions with one named owner who has accepted responsibility
- questions with every consequence-specific approval completed by its internal deadline
- approvals linked to the exact released wording version
- questions reopened after a material post-approval change
- questions held because authority or disclosure approval was missing
- minutes between release authorization and the official question cutoff
- deputy activations supported by recorded delegation
- batch approvals with an inspectable decision for every individual question
- unsent questions with an explicit effect on assumptions and bid decisions
- released questions handed only to the separately authorized sender
Questions
Common questions
Should the bid manager own every clarification question?
Not automatically. The bid manager may coordinate the full register, but each question needs an owner with the capacity and proximity to drive its inputs and decisions. Concentrating every item on one person can hide overload.
Is the question owner also the approver?
Only when that person holds the required delegated authority. Ownership means accountability for closure. It does not by itself authorize legal, technical, privacy, commercial or corporate decisions.
Does every tender question need legal approval?
No. Route legal review when the wording or plausible answer affects legal interpretation, contract position, liability, employment duties, a reservation or another matter within legal authority. Routine factual requests should not wait for irrelevant reviewers.
Can silence count as approval when the deadline is close?
No. Use an affirmative decision from the proper authority. Escalate early, appoint an authorized deputy, narrow or withdraw the question, or revisit the underlying bid decision. Channel access does not cure missing approval.
Can several tender questions be approved as one batch?
Yes, if every question and version remains individually inspectable and receives an explicit decision. Conditions, rejections and open items must be visible at question level.
When must a clarification approval be repeated?
Reopen the affected approval when wording, disclosed facts, source, lot, plausible consequence, attachment, deadline or authority changes materially. Preserve the old decision as superseded.
Can the person with portal access send an approved draft?
Only if that person is separately authorized to use the verified channel for this procurement. Technical access does not establish communication authority, and approval for release does not prove transmission.
What happens to a question that cannot be approved in time?
Record it as held, withdrawn or blocked and route the unresolved issue back to the affected assumption, qualification, price, solution or bid decision. Do not let it disappear merely because it was omitted from the send set.
Sources
Primary references
- Procurement Act 2023, section 12 on covered procurement objectives The National Archives
- Procurement Act 2023, section 31 on modifying a procurement The National Archives
- Procurement Act 2023, section 54 on time limits The National Archives
- Procurement Act 2023, section 96 on electronic communications The National Archives
- Procurement Act 2023, section 98 on record-keeping The National Archives
- UK guidance on covered procurement objectives UK Cabinet Office
- UK guidance on competitive tendering procedures UK Cabinet Office
- UK guidance on modifying a competitive procurement UK Cabinet Office
- UK guidance on procurement time periods UK Cabinet Office
- UK guidance on electronic communications UK Cabinet Office
- UK guidance on publication information and procurement records UK Cabinet Office
- HM Treasury Orange Book on roles, delegation and risk decisions HM Treasury
- Directive 2014/24/EU, including Articles 18, 22, 47 and 53 EUR-Lex
- German GWB section 97 on procurement principles German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 8 on procurement documentation German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 9 on communication German Federal Ministry of Justice and Federal Office of Justice
- German VgV section 20 on time periods and extensions German Federal Ministry of Justice and Federal Office of Justice
- French Public Procurement Code communications chapter, current 1 April 2026 Légifrance
- French DAJ guidance on digital public procurement Direction des Affaires juridiques
- Federal Acquisition Regulation Part 14 on bidder communications Acquisition.gov
- World Bank Procurement Regulations for IPF Borrowers, seventh edition World Bank
- UNCITRAL Model Law on Public Procurement, Articles 15 and 16 United Nations Commission on International Trade Law
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Ziva
Proposal software for source-grounded RFP, RFI, DDQ and questionnaire response work.
Bid, proposal, presales, security and compliance teams. Start with the workflow, constraints and evidence you already have.