---
title: "Where must tender questions be submitted?"
description: "Build a cited clarification-channel record before anyone sends a tender question through a portal, email address or meeting."
canonical: "https://zephior.com/insights/verify-the-official-clarification-channel"
last-updated: 2026-09-03
---

# Where must tender questions be submitted?

> Build a cited clarification-channel record before anyone sends a tender question through a portal, email address or meeting.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-03; updated 2026-09-03. 19 minute read.

## Definition

A clarification-channel verification fixes one procedure, notice version, lot, response stage and question class, then identifies the current buyer instruction that governs where and when that question may be submitted. Its output is a clarification_channel_record containing the controlling source and exact anchor, channel kind and locator, account or role requirement, access state, raw and resolved cutoff, stated attachment and publication rules, acknowledgement evidence, conflicts, expiry and next permitted action. It keeps procurement questions separate from portal support, general buyer contacts, bid delivery addresses, complaints, data-protection contacts and private sales conversations. The check is read-only. It never sends the question or treats a convenient address as buyer authorization.

## Problem

A tender page may show a buyer email, a procurement portal, a technical helpdesk, a submission link and a review body on the same screen. Only one may accept pre-bid questions. In another procedure the buyer may divide commercial questions, technical access problems and confidential material between different routes. Search results often surface a central procurement mailbox while the current instructions require an authenticated Q&A form. A notice can also contain a date for requesting additional information without showing the local time, while an amendment changes the tender deadline but says nothing about the question cutoff. Sending to the wrong place can leave no procedure-linked record and consume the only useful answer window.

## Point of view

Verify the route as an instruction, not as contact discovery. Start with the current procedure-specific pack, invitation and amendments. Use the designated operational portal to confirm the actual function and access gate. Treat notice fields as typed evidence: the additional-information deadline, document URL and submission URL describe different facts. General portal guidance establishes what a platform can do, not what this buyer ordered for this tender. Preserve unresolved disagreement instead of picking the easiest route. An agent may inspect public sources and, with authorized read-only access, confirm that the named Q&A area exists. Pressing Submit, emailing the buyer, opening a support case, accepting terms or disclosing bidder information requires separate authority.

## Submit a tender question only through the route authorized for that procedure

The correct channel is the portal function, email address, physical address or scheduled forum named by the current procurement instruction for the relevant question. A buyer’s homepage contact does not become valid because it reaches the same organization. A technical support address does not become valid because it sits inside the same portal. The route must be tied to the procedure and the communication purpose.

Use channel_confirmed when the exact route and current instruction agree and no material access fact is hidden. Use channel_confirmed_access_gated when the route is clear but an account, organization selection, invitation or role is needed to reach it. That state can support access planning, but it does not authorize a question. Use multiple_channels_by_question_class when the buyer expressly separates, for example, procurement questions from encrypted confidential material or technical incidents.

If two current instructions disagree, return instruction_conflict. If the route is clear but the question cutoff cannot be resolved, return deadline_unresolved. If the named private area has not been checked with permitted access, return access_unverified. Channel_not_found means the inspected current pack and designated portal expose no authorized route. Source_unavailable applies when a required instruction cannot be opened. Procedure_identity_unresolved stops the exercise before any channel is attached to the wrong tender.

**Controlled states for a clarification-channel check**

| State | What the evidence supports | Permitted next action |
| --- | --- | --- |
| channel_confirmed | Current instruction, route and scope agree | Prepare an authorized send against the recorded rule |
| channel_confirmed_access_gated | Route is proved and a named access gate remains | Assign an authorized account holder and verify access |
| multiple_channels_by_question_class | Buyer instructions divide communication by purpose | Classify the question before selecting a route |
| instruction_conflict | Credible current instructions point to different routes | Stop sending and resolve the authority conflict |
| deadline_unresolved | Channel is visible but its usable cutoff is not | Run deadline and time-zone verification |
| access_unverified | Private function is named but not inspected | Obtain read-only access authority or keep the uncertainty |
| channel_not_found | No authorized route appears in the checked current sources | Escalate internally before any buyer contact |
| source_unavailable | A required instruction cannot be inspected | Assign retrieval or access ownership |
| procedure_identity_unresolved | Channel evidence is not safely tied to the intended tender | Resolve procedure and version identity first |

## The nearest email address may belong to a different function

Read the communication section of the current pack before collecting contact details from elsewhere. The current EBRD multi-stage standard makes this separation explicit. ITP 10.1 tells a participant to contact the client in writing as described in the Data Sheet. The works Data Sheet then specifies the ECEPP Message Centre, an alternative paper or electronic clarification procedure where applicable, and the number of calendar days before proposal submission. Separate Data Sheet provisions govern proposal submission. A completed Data Sheet for the live process, not an unfilled model or an address copied from the invitation, supplies the procedure-specific facts.

EU eForms reinforces the functional split. BT-13 records the additional-information deadline at lot or part level. BT-15 is the procurement-documents URL. BT-18 is the electronic submission URL. These fields can appear near one another and sometimes point into the same platform, but they are not interchangeable instructions. The notice can nominate evidence to inspect; the procedure documents and linked operational area still need to establish the exact question workflow.

General legal rules set boundaries without filling every procedure-specific field. FAR 15.201 makes the contracting officer the focal point for exchanges after a US solicitation is released and requires proposal-preparation information disclosed to one potential offeror to be made public promptly. The live solicitation still tells an offeror which named person, system, address and cutoff apply. Likewise, a platform manual can prove that a Q&A function exists while leaving the buyer free to set the particular deadline and access conditions.

**Classify a locator before relying on it**

| Observed locator | Likely function | Evidence needed for clarification use |
| --- | --- | --- |
| Procedure-linked Q&A button | Buyer clarification workflow | Current instruction, matching procedure and access state |
| Named clarification email in the Data Sheet | Buyer clarification mailbox | Exact clause, question class, version and cutoff |
| Buyer website contact page | General organizational contact | Express incorporation into the procurement instruction |
| Portal service desk | Technical access and operation support | Buyer instruction expressly assigning procurement questions |
| Electronic submission URL | Bid or request delivery | Separate messaging function named by the buyer |
| Review body address | Complaint or legal-remedy process | Never reuse for ordinary pre-bid clarification |
| Data-protection or accessibility contact | Specialized rights or access issue | Only the stated specialized purpose |

## A question deadline and a buyer answer period are different clocks

Capture question_deadline_raw exactly as issued, including a named zone, calendar rule and lot or stage scope. If the source gives only a date, do not invent midnight, close of business or the tender deadline’s time. Route the value through a separate time-zone check before producing question_deadline_instant. A date in BT-13 remains a date unless another current instruction supplies the time and zone.

Do not infer the bidder cutoff from the period in which the buyer promises an answer. Article 53(2) of Directive 2014/24/EU says additional information requested in good time must be supplied no later than six days before the tender deadline, or four days in the specified accelerated procedures. “In good time” does not create one universal last day for asking. The procurement may set an earlier question deadline. Record the bidder cutoff and buyer response rule in separate fields.

An amendment that moves the tender deadline does not silently move every other date. Check whether it changes, replaces or expressly preserves the clarification cutoff. Keep both versions and an amendment edge. Until the relationship is stated or otherwise established by the controlling documents, mark the cutoff unresolved rather than applying the same interval to the new tender date.

**Time fields in a channel record**

| Field | Meaning | Do not substitute |
| --- | --- | --- |
| question_deadline_raw | Buyer wording preserved from the source | Normalized date without the original text |
| question_deadline_instant | Resolved timestamp supported by zone evidence | Assumed end of day |
| buyer_answer_rule | Published obligation or target for the response | Bidder’s final sending time |
| tender_deadline | Receipt cutoff for the bid or request | Question cutoff |
| internal_review_by | Team control date before an authorized send | Buyer-issued deadline |

## Prove that the route can be reached without testing it on the buyer

The European Commission’s current Funding and Tenders guidance shows why channel and access are separate facts. Creating a question requires EU Login. The user opens the procedure’s Questions and answers area, chooses Create question and identifies an organization. The workflow can show Submitted, Read and Answered states, and the authority may publish an answer publicly, privately or both. These are documented capabilities of that platform, not a guarantee that every procurement uses identical visibility or timing.

A public check can verify the procedure page, Q&A label, guidance and published cutoff. An authorized account holder can confirm that the intended procedure appears and the function is available. Stop before typing sensitive content or pressing Submit. If merely opening the private area changes a subscription, accepts terms, selects an organization as a represented party or creates a draft visible to the buyer, record that boundary and obtain authority first.

Define acknowledgement before the send. On the Funding and Tenders portal, a Submitted state is documented after submission. In an email procedure the expected evidence may instead be the sent message plus a delivery or buyer acknowledgement named by the instructions. Never relabel a local Sent folder as buyer receipt. After an authorized send, preserve the procedure identifier, question text, attachment fingerprints, channel-generated identifier, timestamp and status separately.

**Read-only access checks and their boundary**

| Check | Evidence gained | Stop before |
| --- | --- | --- |
| Open the public procedure page | Procedure identity and visible Q&A route | Following a link that accepts new terms |
| Inspect current portal guidance | Platform capability and documented statuses | Applying generic guidance as tender-specific authority |
| Use authorized read-only login | Procedure visibility and access gate | Creating a question or choosing a represented organization |
| Observe a blank question form | Allowed fields and stated file rules | Entering bidder strategy or personal data |
| Review a prior authorized receipt | Actual identifier and status behavior | Assuming an old procedure has the same current rules |

## A completed Data Sheet can displace the address that looked obvious on the notice

Consider a fictional multi-stage works procurement using the current EBRD standard structure. Its public invitation lists procurement-office@example.org under “further information.” The completed Data Sheet for ITP 10.1 instead says that all clarification requests must use the procedure’s electronic clarification room and must arrive 14 calendar days before initial proposals. A separate Data Sheet provision identifies the electronic proposal route. The portal homepage also lists a service desk.

The record classifies the invitation email as an information contact, the electronic clarification room as the buyer-question route, the proposal route as submission-only and the service desk as technical support. The controlling anchor is the current completed Data Sheet, ITP 10.1, tied to the procedure and initial-proposal stage. Because the clarification room requires an authorized invitation and has not yet been inspected, the state is channel_confirmed_access_gated, with access_unverified recorded as a condition rather than a competing final state.

Now suppose Corrigendum 2 extends the initial-proposal deadline by seven days but does not mention the clarification deadline. The team does not recalculate “14 calendar days” automatically unless the Data Sheet defines the cutoff relationally and the corrigendum leaves that rule in force. If the published cutoff was a fixed date, it remains a separate observation. The record changes to deadline_unresolved until the current documents establish the relationship.

**Fictional EBRD-style clarification channel record**

| Field | Recorded value |
| --- | --- |
| procedure_id | WB-2026-041, fictional example |
| notice_version | Invitation plus Corrigendum 2 |
| response_stage | initial_proposal |
| question_class | procurement_content |
| controlling_source | Completed Data Sheet, ITP 10.1 |
| channel_kind | authenticated_electronic_clarification_room |
| access_requirement | invited authorized user |
| question_deadline_raw | 14 calendar days before initial-proposal deadline |
| question_deadline_instant | null pending amendment relationship and zone |
| channel_state | deadline_unresolved |
| prohibited_action | Do not email, open support or submit without authority |
| recheck_trigger | Clarification-room access or buyer deadline clarification |

## Expose the evidence path, not only the chosen URL

A useful record lets another agent reconstruct the decision without trusting the prose. Store assessment_id, procedure_id, notice_id, notice_version, lot_ids, response_stage, question_class and checked_at first. For every instruction candidate, retain source_url, source_role, document_version, anchor, exact_text, retrieved_at and applicability. The accepted route then points to the evidence item that supports it.

Keep channel_kind, channel_url, channel_address, portal_area, access_requirement and required_role separate. Use null for an unknown value. Add question_deadline_raw, question_deadline_instant, deadline_zone_basis, attachment_rules, publication_behavior, acknowledgement_method and fallback_channel. A fallback exists only when the buyer expressly supplies one for the same failure or question class.

Finish with conflict_evidence, channel_state, conditions, allowed_action, prohibited_action, valid_until, review_owner and recheck_trigger. Citations belong at field or evidence-item level. A bare source list does not show which page supports the route, deadline or publication claim. Keep private portal observations access-controlled while exposing the public authority basis wherever possible.

**Minimum machine-readable clarification channel fields**

| Field group | Required fields | Reason |
| --- | --- | --- |
| Identity | procedure_id, notice_version, lot_ids, response_stage, question_class | Prevents reuse across the wrong procurement scope |
| Authority | controlling_source, instruction_anchor, applicability, precedence_basis | Explains why the route governs |
| Route | channel_kind, locator, portal_area, access_requirement, required_role | Separates discovery from usable access |
| Time | question_deadline_raw, instant, zone_basis, checked_at, valid_until | Preserves source wording and freshness |
| Behavior | attachment_rules, publication_behavior, acknowledgement_method | Prevents unsupported interface assumptions |
| Control | channel_state, conflicts, allowed_action, prohibited_action, owner, trigger | Bounds automation and routes uncertainty |

## Channel verification ends before communication begins

Hand channel_confirmed to the question owner with the exact cutoff, access requirement and acknowledgement expectation. Hand channel_confirmed_access_gated to the authorized account owner early enough to resolve access. Send drafting questions to the separate wording and disclosure review. Send an unanswered question to the assumption, qualification or no-bid process. A channel record does not decide any of those matters.

Keep technical incidents on the support route named by the platform and keep their tickets out of the procurement Q&A log unless the buyer’s instructions join the processes. A failed login does not justify sending a specification question to support. A missing buyer channel does not justify using sales, a contracting officer’s old thread or a personal address. Escalate internally with the evidence gap and deadline exposure.

Recheck after a new notice, invitation, amendment, Q&A announcement, portal migration, access-rule change or question deadline. Expire the record at the earlier of valid_until and a defeating event. Once an authorized question is sent, create a separate transmission record. That record can refer back to this assessment, but it should not rewrite the evidence that supported the channel choice.

## Useful outcomes

- Each record is bound to one procedure, notice version, lot, response stage and question class.
- The governing instruction is quoted by source location and retrieval time.
- Buyer clarification, portal support, general contact, submission and remedies routes remain distinct.
- Portal login, organization and role requirements are visible before drafting creates a false sense of readiness.
- The original deadline wording is preserved beside any resolved instant and time-zone evidence.
- An email address is accepted only when the current procurement documents authorize it for the question class.
- Conflicting instructions produce a stop state rather than an unrecorded choice.
- Publication, confidentiality and acknowledgement behavior are reported only when a source states them.
- Every result names what an agent may inspect and which external acts remain prohibited.
- Rechecks run after amendments, invitation changes, portal changes or deadline movement.

## Workflow

1. **Fix the communication question.** Record the procedure, current notice or invitation, lot, response stage and whether the issue concerns procurement content, technical access, confidentiality or a legal remedy.
2. **Collect instruction candidates.** Inspect the communication clause, Data Sheet, invitation, current amendment, notice fields and procedure-linked portal area while retaining every exact source anchor.
3. **Classify each route by function.** Mark whether a locator accepts buyer questions, solves portal faults, receives bids, handles reviews or merely supplies general organizational contact details.
4. **Test access without sending.** Using public pages or authorized read-only access, confirm the named function, required account, organization association and role without entering or submitting a question.
5. **Resolve the cutoff separately.** Preserve the raw date, scope and source. Resolve time and zone only with evidence, and keep the buyer answer period separate from the bidder question deadline.
6. **Issue a bounded channel record.** Return a controlled state, citations, conflicts, acknowledgement method, validity boundary, owner and the next action that is permitted under the available authority.

## Key decisions

- Which procedure, notice version, lot and response stage does the proposed question concern?
- Is this a procurement-content question, a portal fault, a confidential disclosure issue or a challenge?
- Which current document or invitation tells bidders where this question class must go?
- Does a later amendment replace, narrow or preserve that instruction?
- Does the notice expose a question deadline, document address or submission address, and which fact does each field represent?
- Does the designated route require login, organization selection, invitation or a specific role?
- Can the route and its access gate be confirmed without transmitting content?
- What is the exact raw cutoff, time zone, lot scope and question class?
- What receipt, status or sent-record evidence will exist after an authorized submission?
- Does the buyer state whether the question or answer may be published or restricted?
- Do any credible procedure-specific instructions disagree?
- When does this verification expire and who owns the authorized send decision?

## Risks

- A general buyer email is mistaken for the tender Q&A route.
- A portal helpdesk receives a specification question it cannot answer for the authority.
- The bid submission URL is used as though it were a messaging channel.
- A complaint or review address is confused with pre-bid clarification.
- A notice-level date is applied to the wrong lot, stage or information request.
- The buyer response deadline is presented as the last day on which a bidder may ask.
- A portal is named but the account, organization or invitation gate remains untested.
- An older instruction survives after a corrigendum or revised invitation.
- A prior email exchange is treated as permission to bypass the published route.
- An agent opens a draft form or submits contact data without the account holder’s authority.
- An acknowledgement screen is assumed to prove buyer receipt when the platform does not say so.
- Confidential treatment is promised without an express procedure rule.

## Metrics

- channel records with procedure, version, lot, stage and question class
- accepted channels carrying a precise current source anchor
- locators classified as clarification, support, submission, review or general contact
- authenticated routes with verified account and role requirements
- cutoffs retaining raw wording, scope and resolved-zone evidence
- instruction conflicts stopped before external communication
- authorized sends that later produce the expected procedure-linked acknowledgement
- records refreshed after a relevant amendment or portal event
- questions diverted from unapproved informal addresses

## Frequently asked questions

### Can we send a tender question to the buyer email shown in the notice?

Only when the current procurement instruction authorizes that address for the relevant question. A general contact or further-information address is not enough when the pack names a portal Q&A route.

### Is the portal helpdesk an acceptable fallback?

Only for the technical issue the helpdesk is assigned to handle, unless the buyer expressly makes it a clarification route. Record the incident there and preserve the procurement question for the buyer channel.

### Does the tender submission link also accept questions?

Not by default. Submission and clarification are separate functions even when they use the same portal. Require a named messaging or Q&A function before treating it as a question route.

### What if the notice and the tender instructions name different channels?

Preserve both instructions and inspect their versions, scope and amendments. Do not choose by convenience. Return instruction_conflict until the current authority basis supports one route.

### Does an additional-information deadline always include a time?

No. Preserve a date-only field as issued. Resolve an instant only from a source that supports the time and zone; otherwise return deadline_unresolved.

### Can an AI agent test the question form?

It may inspect public guidance and, with explicit read-only authority, confirm the accessible interface. It must stop before accepting terms, selecting a represented organization, entering sensitive content, creating a buyer-visible draft or submitting.

### Can we rely on a colleague’s previous email exchange with the buyer?

Use it as an instruction candidate only if it is authentic, current, procedure-specific and authorized to change the published route. Otherwise preserve it as context and follow the controlling procurement instruction.

### Does the verified channel prove the buyer received our question?

No. Channel verification proves the route before sending. Receipt or status evidence belongs to a separate authorized transmission record created after the question is submitted.


## Primary sources

- [How to create and submit a question on the Funding and Tenders portal](https://wikis.ec.europa.eu/spaces/FTPortal/pages/106692790/How%2Bto%2Bcreate%2Band%2Bsubmit%2Ba%2Bquestion%2Bon%2Bthe%2BFunding%2Band%2BTenders%2Bportal), European Commission
- [TED eForms business terms, including clarification, document and submission fields](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/index.html), Publications Office of the European Union
- [TED eForms BT-13 additional-information deadline](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-13.html), Publications Office of the European Union
- [EBRD multi-stage Instructions to Participants, clarification rule at ITP 10.1](https://www.ebrd.com/content/dam/ebrd_dxp/assets/pdfs/project-procurement/standard-procurement-documents/english/goods/multi-stage/sections/I-Instructions-to-Participants-Multi-Stage.pdf), European Bank for Reconstruction and Development
- [EBRD multi-stage works Data Sheet, clarification and proposal routes](https://www.ebrd.com/content/dam/ebrd_dxp/assets/pdfs/project-procurement/standard-procurement-documents/english/works/multi-stage/sections/II-Data-Sheet-Multi-Stage-W.pdf), European Bank for Reconstruction and Development
- [FAR Subpart 15.2, solicitation exchanges and amendments](https://www.acquisition.gov/far/subpart-15.2), Acquisition.gov
- [Directive 2014/24/EU, Article 53 and additional information](https://eur-lex.europa.eu/eli/dir/2014/24/2024-01-01/eng), EUR-Lex


## Related articles

- [How to authorize an agent to submit a tender](https://zephior.com/insights/authorize-an-agent-to-submit-a-tender)
- [Can a tender clarification be kept confidential?](https://zephior.com/insights/handle-a-confidential-tender-clarification)
- [Could portal maintenance affect the submission window?](https://zephior.com/insights/plan-for-tender-portal-maintenance)
- [How to verify that a tender was actually received](https://zephior.com/insights/verify-tender-submission-receipt)