How to find buyer consultations and supplier days before an RFP

Search boundary

Start with the market you can serve, not an event keyword

A useful search brief begins with the purchasable capability and the public bodies likely to need it. Record the countries or subnational markets, buyer legal entities and known parent bodies, delivery geography, working languages, relevant classifications, date horizon and the public sources the search may inspect. Add outcome phrases and buyer objects, such as records migration, fleet charging or laboratory sample tracking. “Supplier day” alone is too broad, while one product name is too narrow. The brief should find a buyer discussing the problem even when the supplier’s category never appears.

Set the time boundary just as carefully. Decide how far back to inspect completed engagement for context and how far ahead an event must be to remain operationally useful. Record the search instant in UTC plus the operator’s time zone. The result is a dated discovery artifact, not a claim that every consultation in the market has been found. Missing public feeds, inaccessible buyer pages and unsupported jurisdictions remain visible coverage gaps.

The unit of work is one engagement invitation, not a buyer and not a future tender. A single procurement may contain a questionnaire, an open webinar and selected one-to-one meetings with different rules. Store them under a shared lineage when the buyer provides one, but preserve the action and deadline for each. This prevents an open webinar from making a closed questionnaire look active.

Discovery map

Buyers describe the same early exchange in different ways

Build a terminology matrix for each market. Include formal names such as preliminary market engagement, prior consultation and pre-market consultation. Add operational names: market sounding, supplier day, industry day, meet the buyer, vendor briefing, request for information, Sources Sought, draft RFP comment period, technical dialogue, supplier questionnaire, demonstration, workshop and site visit. Translate the purpose, not merely the words. A local procurement specialist should review terms whose legal or commercial meaning changes across languages.

Match each term family to its likely official home. Search structured notice portals first, then the buyer’s procurement pipeline, procurement news, events calendar, consultation hub and document library. TED’s current eForms documentation defines a voluntary Pre-Market Consultation notice as consultation form E1, separate from planning and competition forms. Its Search API allows unauthenticated systems to search published notices. In the United States, the SAM.gov public API exposes Sources Sought as procurement type “r” and Special Notice as “s”, but it requires an API key and date range. These fields are useful retrieval paths, not proof that a particular response remains open.

Trade bodies, email newsletters, social posts and aggregators can reveal vocabulary or point to an event. Treat them as leads. Resolve the buyer, title, official URL and participation instructions before creating an operational row. If the official page cannot be found, retain source unresolved with the discovery link and a review task. Do not copy the secondary source’s deadline into the operative calendar.

Evidence state

Prove that the buyer is still accepting this kind of participation

Open the current notice, buyer page and linked documents. Capture the official title, buyer legal entity, engagement or notice identifier, publication and update dates, purpose, scope, related procurement identifier, source URL and retrieval time. Then read the verbs addressed to suppliers. “Register”, “submit”, “complete” and “request a meeting” may create actions. “Was held”, “received responses” and “has informed our approach” describe history. A page can contain both, so classify each action rather than the page as a whole.

Current UK guidance makes this distinction explicit: a preliminary market engagement notice may invite suppliers or tell the market that engagement has already taken place. It also says an authority is not obliged to proceed with the procurement and that later requirements need not match the early description. Elsewhere, do not assume the same notice obligations apply. The broader classification still holds: an invitation is open only when the current official source names a participation route whose closing event has not passed.

Preserve uncertainty. If the event page says registration open but the linked form says closed, the row is source conflict, not open. If a buyer announces an intention to consult but gives no route or date, use planned, date unknown. If the tender notice has appeared, close the early action and link a new tender record. Do not silently convert the consultation into a bid because both concern the same planned purchase.

Participation rules

Registration, attendance and written input run on different clocks

Extract every time as an event with its own subject. A registration form may close several days before a webinar. Questions may be due before the meeting, while a questionnaire remains open afterward. One-to-one slots may be assigned on a first-come basis or after the buyer reviews expressions of interest. Record date, clock time, named time zone or offset, channel, receipt rule and the action governed. Keep an expected tender publication month in a planning field. It is not a response deadline.

Read who may participate and on what basis. Capture supplier type, geography, lot or capability focus, limits on attendee numbers, accessibility arrangements, required account, requested declarations and any method for reducing participants. UK guidance, for the procurements it covers, says the notice can state how numbers will be reduced and must include event format details. That does not make a capacity rule universal. Cite the invitation’s own wording and local regime.

List preparation before deciding that the event is lightweight. The buyer may ask for a questionnaire, presentation, technical diagrams, indicative pricing, case studies or written comments on a draft specification. Record file formats, page limits and naming rules when supplied. Mark each requirement as mandatory, optional or unclear only from the source. If unclear participation rules could change what the supplier discloses or commits to, a person reviews them before any external action.

Response preparation

Answer the buyer’s planning question without turning it into a sales pitch

Create a response map from each buyer question to an approved fact, named evidence owner and disclosure class. Explain what the market can deliver, where a requirement would restrict competition, which dependencies affect cost or timing, and which alternatives the buyer asked to compare. Use ranges or assumptions only when the buyer requests them and the supplier has approved their basis. Do not imply that an indicative response is a binding tender, but do not hide behind disclaimers that make the input useless.

Protect material that should not leave the company. Mark public facts, approved customer evidence, confidential business information, intellectual property, product roadmap detail, personal data and unapproved commercial positions separately. Read the buyer’s confidentiality and publication terms before attaching anything. UK guidance recommends that authorities plan how confidential information and intellectual property will be handled; FAR 15.201 also protects certain confidential business-strategy information. Neither source guarantees that every statement a supplier labels confidential will be withheld under every applicable law.

Participation must not seek a private advantage that depends on undisclosed information. EU Directive Articles 40 and 41 allow consultation but require measures against distorted competition, including sharing relevant information and allowing adequate tender time where prior involvement matters. FAR 15.201 likewise requires certain proposal-preparation information disclosed to some potential offerors to be made public to avoid unfair advantage. A supplier should keep its own record of what it received, asked and provided, and escalate any exchange that appears to confer unequal access.

• Answer only the stated question and label assumptions.
• Link factual claims to material approved for external use.
• Separate indicative market information from a contractual commitment.
• Remove personal, customer-restricted and security-sensitive material.
• Record confidentiality requests without promising their legal effect.
• Stop when the buyer’s request or access route creates a fairness concern.

Calendar artifact

One row should explain the invitation and the next permitted action

The calendar row identifies buyer, engagement ID and title, jurisdiction, capability match, official publisher and URL, source version, publication and retrieval times, engagement type, purpose, current state and related procurement lineage. It then records audience, eligibility, reduction method, participation channel, registration close, event instant, questions close, written-input close, required preparation, confidentiality terms, missing facts, owner, reviewer and next action. Store evidence passages or field references beside the claims they support.

Make the record readable by systems without hiding uncertainty. Use ISO 8601 instants with offsets, stable field names, enumerated states and explicit null values. Preserve the source language for legally significant terms and add a reviewed interpretation rather than replacing the original. The public version can expose source facts, state and method while withholding credentials, private contact notes, restricted documents and internal strategy. A public-source row should never contain portal tokens or personal API keys.

OCDS gives useful interoperability patterns rather than a complete supplier calendar. Its planning block can carry documents and milestones; the milestone codelist includes preProcurement and engagement; related processes can connect planning with a later tender. Map those concepts where the publisher supplies them, but retain the buyer’s original identifiers and evidence. A custom field with a precise source is safer than pretending an absent standard field was published.

Agent authority

Let agents search and maintain evidence, then stop before external action

An agent can expand approved search terms, query public portals and APIs, inspect public buyer pages, deduplicate records, normalize verified times, extract participation rules, identify conflicts, draft an internal response map and monitor published changes. It should return the query, sources inspected, retrieval times, excluded candidates and reason for each state. Coverage claims stay bounded to the sources and languages actually checked.

Registration, accepting portal terms, requesting a meeting, contacting a buyer, uploading a questionnaire and disclosing company information are external acts. They require the named authorization set by the supplier. Pricing, product commitments, legal interpretations, confidentiality decisions and claims about customer work also require qualified review. The agent may prepare a proposed packet but cannot turn “open for input” into permission to send it.

Stop automatic work when the official source cannot be resolved, instructions conflict, eligibility is unclear, participation is capped, a portal asks for terms or credentials, the buyer requests non-public material, or the exchange raises an unequal-access concern. Reopen the row when a page changes, a deadline passes, a registration confirmation arrives, an outcome is published or a linked tender appears. Preserve prior states so the record shows what was known when each action was considered.

• Public search and evidence extraction may run under approved source limits.
• Drafting stays internal until content and disclosure review are complete.
• Account creation, registration, contact and submission need explicit authority.
• Conflicts, caps, confidentiality and competition concerns stop automation.
• Every change retains its source, time and previous state.