A procedure classification and bidder-consequence record is a dated, source-linked reading of one procurement under its stated jurisdiction and legal basis. It retains the official procedure label and code, the notice and version that state them, the governing regime, any buyer-defined stages, the present stage, who can enter, what object is due next, how suppliers progress, whether dialogue or negotiation is provided, whether an initial tender may be final, and which deadline controls the next act. A separate operational access family can describe the route as open, selective, limited or direct for cross-source retrieval, but that family is an index, not a substitute legal classification. `confirmed_prescribed` means official sources identify a prescribed procedure and the stage model is consistent. `confirmed_bespoke` applies when the regime permits a buyer-designed procedure and the documents disclose enough of that design to identify the next supplier act. `procedure_label_conflict`, `stage_conflict`, `insufficient_public_evidence` and `superseded` preserve a problem rather than guessing. The record explains the consequence for this opportunity. It does not decide whether the buyer lawfully selected the procedure or give case-specific legal advice.
A listing can call an opportunity open because its deadline has not passed even when the procurement uses a selective first stage. An RFP can be the name of a document inside an open procedure, a negotiated process or a private competition. A framework, dynamic market, electronic auction and accelerated timetable can change how a procurement runs without being interchangeable with its procedure type. Current UK competitive flexible procedures can reproduce a shortlist, dialogue, negotiation, demonstrations or several tender rounds under one broad legal label. A legacy database may still translate that label into restricted or competitive dialogue. That translation can tell a supplier to prepare a full tender when only a request to participate is invited, promise a negotiation the documents never offer, or dismiss a public entry route as invitation-only. The procedure field is useful only when it leads to the right next act.
Read procedure type as a local legal fact and stage design as an operational fact. Start with the accepted current notice, record its legal basis and published procedure field, then read the associated documents that describe participation, shortlisting, tender rounds, dialogue, negotiation and award. Preserve the source label even when a normalized access family improves search. Never use a familiar foreign label as a legal translation. “Open opportunity” is a status phrase, not proof of an open procedure. “Competitive flexible” describes a legal family, not a fixed sequence. “Negotiated” does not promise that every interested supplier may enter or that every term can change. An agent may extract, reconcile and explain public instructions. It must not register, submit, contact the buyer, invent a missing stage or judge the legality of the buyer’s choice without separate authority and suitable legal review.
Direct answer
A useful classification tells the supplier what can happen next
The procedure is the published route by which this buyer moves from competition to contract. Confirm it from the current official notice under the stated legal regime, then read the associated documents for the actual sequence. The output should answer a practical question: who may send what, by which deadline, and what happens before a final tender or award?
TED eForms stores the procedure type in `BT-105`. Its current codelist includes open, restricted, negotiated with a prior call for competition, negotiated without a prior call, competitive dialogue, innovation partnership and other single-stage or multi-stage procedures. That code is strong evidence for notices within its scope. It still needs the notice version, legal basis and documents. A current correction may change the displayed label or the instructions that give the label operational meaning.
The next act depends on both type and stage. In a prescribed open procedure, any interested supplier may ordinarily submit a tender. In a prescribed restricted procedure, any interested supplier may request participation, but only selected suppliers may tender later. A buyer-designed procedure may invite either a request to participate or a first tender at publication. A direct-award transparency notice can be public without inviting any supplier response.
Do not stretch the task into a legal conclusion. A notice can prove what procedure the buyer declared. It cannot by itself prove that the buyer satisfied every condition for using that procedure. Where legality affects a challenge, eligibility or material investment, hand the sources and the narrow question to qualified counsel.
| Question | Field to record | Evidence needed |
|---|---|---|
| What does local law call it? | `local_procedure_label` and `local_procedure_code` | Current notice and legal basis |
| Who may enter now? | `entry_population` | Notice invitation and participation rules |
| What is due now? | `current_supplier_act` and `submission_object` | Current stage instructions |
| What interaction follows? | `dialogue`, `negotiation` and `rounds` | Procedure design and invitation documents |
Classification model
Keep the local procedure and the access pattern in separate fields
Cross-market search benefits from a small common vocabulary. The Open Contracting Data Standard uses open, selective, limited and direct. In that model, open means all interested suppliers can submit a tender; selective means only qualified suppliers are invited to tender; limited means the procuring entity contacts suppliers of its choice; and direct means award to one supplier without competition. These values are useful for retrieval and broad routing.
They are too coarse to replace the local procedure. A competitive dialogue and a restricted procedure can both have selective entry, yet dialogue changes how the need and solution develop. A UK competitive flexible procedure can begin with open entry and later shortlist, negotiate defined matters, request demonstrations and invite a final tender. Calling all three `selective` without the official label and stage graph erases the differences a bidder needs.
Record at least three layers. `legal_classification` preserves the regime, official label and code. `access_family` supports common search. `stage_graph` records the buyer’s disclosed sequence, gates and permissions. The legal layer answers what the procedure is called here. The access layer answers how entry broadly works. The graph answers what this supplier must do now.
Add a mapping rationale and confidence to every normalized value. If the notice says competitive flexible but the documents do not yet reveal whether publication invites participation or a tender, keep `access_family` unresolved. A broad label does not license an invented route.
| Published concept | What it describes | Common mistake |
|---|---|---|
| Procedure type | Legal route to an award | Replacing it with a foreign near-equivalent |
| Framework or dynamic market | Purchasing technique or commercial vehicle | Assuming establishment and call-off use one procedure |
| Accelerated procedure | Timetable treatment within an applicable route | Treating acceleration as a separate access family |
| RFP or ITT | Document or invitation label | Inferring legal procedure from the filename |
| Open status | Whether a stated act is currently available | Calling every live opportunity an open procedure |
Bidder consequence
Reconstruct gates, rounds and permissions from the documents
Start the graph with the act invited by the current notice. A request to participate is an application to enter or progress, not a tender for the contract. An initial tender is a commercial and technical offer even when later negotiation is planned. A final tender follows the close of dialogue or negotiation only when the published design provides that stage. Use the buyer’s nouns and define each one.
For every edge, capture the rule that allows movement. A supplier may progress by satisfying conditions of participation, ranking within a stated maximum, surviving an intermediate assessment, completing a demonstration or receiving an invitation. Record whether a criterion is pass or fail, scored or merely informational. The procedure name rarely contains that detail.
Model interaction by subject and timing. `clarification` may explain an instruction without changing an offer. `dialogue` may help define or develop the requirement in a procedure that provides it. `negotiation` may cover only named elements. Never infer that minimum requirements or award criteria are negotiable. If the documents reserve award on initial tenders, expose that field beside the planned negotiation so the first offer is written as awardable.
Bind every deadline to its object. A participation deadline, initial-tender deadline, dialogue meeting and final-tender deadline are different events. If the graph knows the procedure but cannot identify which object the visible date controls, return `stage_conflict` or `insufficient_public_evidence`. A plausible date is not a safe routing instruction.
| Stage field | Question answered | Safe null condition |
|---|---|---|
| `entry_population` | Who can take the next step? | Invitation rule is absent |
| `submission_object` | What must be sent? | Notice and portal disagree |
| `progression_gate` | How does the supplier advance? | Criteria are not disclosed |
| `interaction_mode` | What exchange is permitted? | Only generic contact details exist |
| `award_on_initial_tender` | Can round one win? | Reservation is not stated |
| `deadline_anchor` | When is this object due? | Date has no stage or lot scope |
Worked UK example
Competitive flexible is a family, so the notice must expose the route
Consider a fictional 2026 procurement by North Quay Transit Authority for depot energy software. The tender notice states “competitive flexible procedure.” The associated document invites any interested supplier to submit a request to participate. Five suppliers will be shortlisted against three conditions of participation and a published scoring method. Shortlisted suppliers submit an initial tender, attend one solution demonstration and may negotiate only implementation sequencing and service-credit bands. Minimum cybersecurity requirements and award criteria are fixed. The disclosed route ends with an invitation to submit final tenders.
Current UK guidance reflects section 20 of the Procurement Act 2023: an open procedure is single-stage and does not restrict who may submit tenders; a competitive flexible procedure is another procedure the authority considers appropriate. The guidance says a competitive flexible notice can invite a request to participate or a first or only tender. It also explains that the older restricted, competitive-with-negotiation and competitive-dialogue labels are no longer separate procedures under this regime, even though a buyer can design similar stages inside a competitive flexible procedure.
The correct current answer is not “submit the RFP.” It is `submit_request_to_participate`. The local classification is `competitive flexible procedure`; the broad access family is `selective` because public entry leads to a shortlist; and the stage graph preserves the later initial tender, demonstration, bounded negotiation and required final tender. A system that labels the opportunity “restricted procedure” has produced a tempting but legally inaccurate translation.
Every name, date and identifier in this example is fictional. The legal sources are current public materials; the scenario is an illustration, not a report of a live procurement. In a real record, quote the exact notice and document anchors instead of borrowing these facts.
| Field | Recorded value | Consequence |
|---|---|---|
| `legal_classification` | UK competitive flexible procedure | Do not relabel as legacy restricted |
| `access_family` | Selective | Any supplier may seek entry; only shortlisted suppliers tender |
| `current_stage` | Participation | Prepare the requested participation evidence now |
| `later_interaction` | Demonstration plus bounded negotiation | Do not assume every term is open |
| `award_on_initial_tender` | False in the disclosed route | Track the required final-tender invitation |
| `state` | `confirmed_bespoke` | Use until a correction or stage transition supersedes it |
Evidence and conflict
A structured code wins only within the right notice and regime
Prefer the current official competition notice and its structured procedure field, but qualify that preference. Confirm the procedure identifier, notice version, legal basis, buyer and lot. Then inspect the associated tender documents and later corrections. A portal search card, aggregator label or document filename is discovery evidence. It should not silently override the official source.
Issue `procedure_label_conflict` when current authoritative sources assign incompatible types to the same procedure and scope. Issue `stage_conflict` when the type is stable but the notice, documents or portal demand incompatible next objects. For example, a competitive flexible notice may invite a request to participate while the portal labels its upload area “final tender.” Preserve both observations, timestamps and source locations.
`insufficient_public_evidence` fits a broad procedure label whose operative stages are unavailable or incomplete. `superseded` retires a record after a correction or new stage notice changes the facts. A prescribed EU-style code with coherent documents can use `confirmed_prescribed`; a buyer-designed route with enough disclosed steps can use `confirmed_bespoke`. Neither state certifies legal validity.
Do not resolve a conflict by importing the usual sequence from a textbook. The next check should name a public object: the latest correction, the procedure timetable, the participation section or the invitation. Contacting the buyer is an external act and needs separate authority, even if a clarification channel is public.
| Evidence | Use | Limit |
|---|---|---|
| Current official notice | Procedure code, legal basis and invited act | May need documents for bespoke stages |
| Associated tender documents | Stage sequence, gates and interactions | Must belong to the same notice version |
| Correction or stage invitation | Current change or transition | Scope it to affected lot and supplier population |
| Official legal text or guidance | Meaning under the named regime | Does not supply missing case facts |
| Portal or aggregator label | Discovery and conflict signal | Not controlling by visual prominence |
Agent output contract
Return facts, consequences and abstentions in one inspectable object
An agent-readable output needs stable fields rather than a paragraph saying the process “looks restricted.” Include procedure and notice identifiers, version, jurisdiction, regime, legal basis, buyer, lot scope, local label and code, access family with mapping rationale, current stage, supplier act, submission object, entry population, progression gates, later rounds, interaction permissions, initial-award reservation, deadline anchor, evidence anchors, conflicts, checked time, expiry triggers and state.
Keep observations separate from consequences. “The notice invites requests to participate” is an observation. “An uninvited supplier may submit a participation request now but may not yet submit a tender” is the consequence. Both need evidence. If the consequence depends on a missing instruction, leave it unresolved rather than combining a procedure stereotype with a live deadline.
The record should also say what it did not decide. It does not establish that the buyer lawfully chose the route, calculate statutory minimum periods, decide a remedy, waive a condition, register a supplier or submit a response. Those boundaries let another agent reuse the classification without inheriting hidden assumptions or authority.
Downstream automation can consume confirmed fields. Opportunity matching can filter by public entry. Bid planning can create the correct participation or tender workstream. Calendar logic can bind the right deadline object. A conflict state blocks these uses until a human or a newer public source resolves it.
| Field group | Required contents | Rule |
|---|---|---|
| Identity | Procedure, notice, version, buyer and lot | No cross-procedure joins |
| Law | Jurisdiction, regime, legal basis, local label and code | Preserve source wording |
| Operation | Access family, stage, act, object, gate and interaction | Cite each consequence |
| Time | Deadline object, instant, zone and source | Never reuse a bare date |
| Assurance | State, conflicts, checked time and expiry | No confidence without evidence |
| Authority | Read-only scope and prohibited external actions | Require explicit authorization |
What good looks like
Useful outcomes from identify procurement procedure
- The official local procedure label, code, governing regime, notice version and evidence anchor remain visible in one record.
- A separate operational access family supports cross-market retrieval without replacing the jurisdiction-specific classification.
- The current stage identifies the exact supplier object due now, such as a request to participate, initial tender, final tender or dynamic-market application.
- Public entry, shortlisting, invitation, dialogue, negotiation, demonstrations and elimination rules are represented independently.
- An initial tender is treated as potentially final whenever the controlling documents reserve award without negotiation.
- Framework and dynamic-market techniques remain distinct from the procedure used to establish them or award under them.
- Conflicting labels or stage instructions block automated pursuit recommendations until the discrepancy is resolved.
- Every bidder consequence points to the notice or document passage that supports it and carries a checked time and expiry trigger.
Operating model
How to run the work
- 01
Fix the procurement and current notice
Use the verified procedure identifier, notice identifier, version, stage and lot scope. Do not classify a planning notice, award notice or related framework as the live competition by association.
- 02
Capture jurisdiction and legal basis
Record the governing regime and buyer category before interpreting a label. The same English word can carry different procedural consequences in another law or special regime.
- 03
Extract the official procedure type
Copy the structured code and displayed label from the current notice, with a precise evidence anchor. Preserve both when a portal renders a human label from a code.
- 04
Reconstruct the disclosed stages
Read the associated documents for entry, conditions of participation, shortlisting, tender rounds, dialogue, negotiation, demonstrations, elimination and final-offer rules.
- 05
Name the supplier act due now
Return one current act and its object, channel and deadline anchor. Keep a request to participate separate from a tender even when the same portal button accepts both.
- 06
Normalize only for retrieval
Assign an open, selective, limited or direct access family when the evidence supports it, while retaining the official local classification and its more detailed stage model.
- 07
Issue a state and safe next step
Confirm the classification only when the label, stage and current instructions cohere. Otherwise preserve the conflict, stop dependent automation and identify the next public source to check.
Evaluation
Questions that change the decision
- Which procurement, notice version, jurisdiction, legal basis and lot does the classification cover?
- What official code and local procedure label does the current notice publish?
- Does the regime prescribe a sequence, or must the sequence be reconstructed from buyer-designed documents?
- Can any interested supplier submit the next object, or only an admitted or invited supplier?
- Is the next object a request to participate, a tender, an initial tender, a revised tender or a final tender?
- What evidence permits dialogue, negotiation, a demonstration, elimination or refinement of criteria?
- Could the buyer award on the initial tender without entering an expected negotiation?
- Does a correction, new invitation or stage notice supersede the procedure description currently stored?
Failure modes
Where teams lose control
An “open” status badge can be mistaken for the formal open procedure.
A document called RFP can be treated as a procedure type even though it only names the requested response.
A competitive flexible procedure can be forced into a legacy restricted or dialogue label and lose buyer-defined stages.
A selective entry stage can be skipped because the eventual full tender documents are already visible.
A mention of possible negotiation can be converted into a promise that price, minimum requirements or award criteria will change.
A team can hold back its strongest initial tender even though the buyer may award without negotiation.
A framework or dynamic market can be recorded as the procedure rather than as a purchasing technique with its own entry and award rules.
An agent can turn a public-source classification into unauthorized registration, communication, submission or legal advice.
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.
- procedure records with a current official notice, legal basis, local label, code and exact evidence anchor
- buyer-designed procedures whose disclosed stages are represented rather than inferred from the family name
- opportunities where the current supplier act, object, channel and deadline anchor are all explicit
- normalized access families that retain the original local classification and never claim legal equivalence
- negotiation and dialogue fields supported by a cited permission and bounded subject matter
- initial-tender records that expose whether award without negotiation is reserved
- procedure or stage conflicts preserved and excluded from automated pursue recommendations
- records rechecked after a correction, invitation, stage transition or change in governing documents
Questions
Common questions
Does an open opportunity use an open procedure?
Not necessarily. Open can describe current status or public visibility. Confirm the formal procedure in the current official notice and then identify the act available at the present stage.
Is an RFP a procurement procedure?
Usually it is a document or buyer label. The same label can appear inside different public procedures or a private competition. Use the governing notice and rules for classification.
Can I submit a tender during a selective first stage?
Only if the current instructions invite a tender. A selective route commonly invites a request to participate first and reserves tender submission for suppliers selected and invited later.
Does competitive flexible mean negotiation will happen?
No. The buyer designs and discloses the route. It may include one or more stages, dialogue, negotiation, demonstrations or none of those. Read the tender notice and associated documents.
May a buyer award without holding the planned negotiation?
That depends on the governing regime and disclosed documents. If the buyer reserves award on initial tenders, treat the initial tender as potentially final and cite that reservation.
Is a framework agreement a procedure type?
It is better recorded separately as a purchasing technique or vehicle. The framework can be established through one procedure, while later awards follow its call-off rules.
Can a normalized open or selective code replace the local label?
No. A normalized family improves retrieval across data sources. Keep the official local label, legal basis and detailed stage graph because they determine the bidder consequence.
Can an agent decide whether the buyer used the right procedure?
The agent can report the declared procedure and the public basis for it. A legality or remedies analysis is a separate, jurisdiction-specific task for a qualified reviewer.
Sources
Primary references
- Procurement Act 2023, including section 20 The National Archives
- Guidance on competitive tendering procedures UK Cabinet Office
- The Procurement Regulations 2024 The National Archives
- BT-105: Procedure Type Publications Office of the European Union
- eForms procurement procedure type codelist Publications Office of the European Union
- OCDS guidance on pre-qualification and pre-selection Open Contracting Partnership
- Directive 2014/24/EU, procurement procedures EUR-Lex
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
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.