How to find tenders near a delivery location

Operating boundary

Turn “nearby” into a service rule that operations can defend

A useful radius begins with the work, not the map. A parts delivery, a four-hour repair call, a weekly inspection and a twelve-month construction site impose different limits from the same depot. Name the operating anchor with its full address, source and coordinate confidence. Then describe the on-site share, visit frequency, response clock, working hours, crew pattern, equipment movement and return requirement. If a second branch or approved partner can serve the work, give it a separate anchor and owner. Do not move the origin silently to make an opportunity fit.

Choose the measure that matches the promise. Kilometres may suit a delivery tariff. Road time may govern routine maintenance. Emergency work may depend on dispatch time at night, vehicle readiness and the customer’s definition of arrival. Record whether the limit covers one direction or a return shift, whether overnight stays are allowed, and which ferries, tolls, borders or seasonal roads need review. The service envelope should yield pass, fail or review from the same facts when another person applies it.

Source reading

Read the lot and documents before turning an address into a pin

Procurement data contains addresses with different meanings. The buyer address identifies an organization. A place of performance describes where works, supplies or services are expected. A delivery address may appear only in a pricing schedule, site appendix or call-off document. A meeting venue and a mandatory visit location are yet another category. Save each value with its field, section, lot, notice version and source passage. Never copy the first visible address into a generic location column.

eForms models place of performance as a repeatable group because a part or lot may run in several locations. It can contain street, city, postcode, country subdivision, country and additional information. It can also express wider patterns such as country-wide, EEA-wide or anywhere. TED exposes separate location fields for procedure, part and lot. Prefer the most specific current value and keep every material site. When a document narrows or expands the notice, preserve both and flag the conflict for review rather than choosing the convenient one.

Geographic model

Use regions to retrieve candidates, not to measure the journey

NUTS is the EU classification of territorial units for statistics. Its three regional levels move from larger to smaller units, and TED lets users browse places of performance by country or NUTS level. This makes NUTS useful for a first retrieval layer. It does not describe a road network, travel time or service boundary. A depot near a regional border may reach a site in the next NUTS unit faster than one at the far edge of its own. Include all units touched by the service envelope and a documented recovery ring around them.

Write the classification edition beside every stored code. NUTS 2024 has applied since 1 January 2024, while NUTS 2027 takes effect on 1 January 2027. Codes and boundaries can change. Historical notices must be interpreted with the edition relevant to their publication or source data, then mapped explicitly if the search system uses a newer edition. Add city, postcode and free-text branches for places that structured regional fields miss. Keep country-wide, EEA-wide, anywhere and unspecified results in named lanes because none can be evaluated as a single point.

• Start with the smallest structured region that still covers the operating envelope.
• Add neighboring units reached within the same operating threshold.
• Record the NUTS edition rather than storing an unexplained code.
• Run city, postcode and site-name recovery searches separately.
• Keep broad and unspecified location values available for document review.
• Use route evidence, not regional membership, for the final distance judgement.

Search plan

Make every location search reproducible and independently testable

Create one row for each portal and search arm. Save the exact field alias, operator, value, notice stage, category condition, publication window, active-status rule, latest-version setting, execution time and result count. TED’s expert-search examples include place-of-performance queries by a NUTS code, by country and by broad values. The Search API documentation also provides location-query examples. Portal behavior changes, so retain the raw query and the response metadata needed to run it again.

Do not hide every location route inside one large Boolean expression. Separate core region, neighboring region, country, city or postcode, document phrase, broad location and missing-location recovery. Dedupe later by stable procedure, notice and lot identifiers while preserving the query arm that found the record. This structure shows which lane adds useful candidates and which creates noise. Run current opportunities against the live official source on the date of use; an article or cached result cannot establish what is open now.

Triage states

Preserve mixed and unknown locations instead of forcing yes or no

A lot with six facilities does not have one truthful midpoint. Compare every mandatory site with the service envelope and retain the set. The result may be confirmed in range, confirmed outside, mixed, remote or broad. A mixed lot can still be viable through a partner, another base, a lot split or a permitted delivery model, but that is a new decision with its own evidence. Do not average an easy site and an impossible site into a plausible distance.

Missing geography needs two states. Provisional means the notice gives a coarse location while a named document or later stage may provide detail. Unknown means the relevant source is absent, inaccessible or contradictory. Neither state is a failed radius test. Keep the candidate in a bounded review queue, record the exact missing fact and use the official clarification route if the answer matters before the deadline. A separate eligibility-unresolved flag prevents an operationally attractive result from moving directly to bid qualification.

Routing

Attach assumptions to every distance and travel-time estimate

Resolve each endpoint before calculating. Save the source address, normalized address, geocoder, coordinates, match type and confidence. A postcode centroid, municipality centre and exact facility entrance are different endpoints. If the source identifies only a region, do not invent a point at its centre and call the result site distance. Use that region for retrieval and retain the route as unresolved until a defensible endpoint appears.

Straight-line distance is a cheap outer screen when it is labelled as such. Operational review should use an approved routing method and record mode, departure assumptions, traffic basis, road restrictions, border or ferry treatment, result and retrieval time. Test the service promise rather than a pleasant daytime journey. A four-hour response can include dispatch, loading, parking, security access and site induction. Route estimates support the decision only for the named endpoints and assumptions; they are not permanent facts.

• Keep the published address beside the normalized mapping input.
• Record exact, interpolated, postcode, locality or region match confidence.
• Label straight-line and routed distance as different measures.
• Include dispatch and access time when the contract measures response.
• Test restrictions that affect the actual vehicle, crew or equipment.
• Recalculate after a site, route, schedule or operating-base change.

Decision boundary

A short journey does not grant the right or capacity to bid

Location screening answers an operations question: can the named delivery model plausibly serve the published sites? Eligibility asks whether the economic operator may participate and meets the stated conditions. The procurement documents may require professional registration, licences, security clearance, insurance, experience, language coverage, a site visit, named resources or a response commitment. Some conditions apply at submission, others at award or during performance. Capture the exact clause, jurisdiction, lot, timing and evidence request. Do not infer a local-establishment rule from the place of performance or from the buyer’s address.

For procurements governed by Directive 2014/24/EU, Article 18 states equal treatment, non-discrimination, transparency and proportionality, while Article 58 allows requirements concerning the human and technical resources needed to perform the contract. Those principles do not decide a specific case. National law, the procedure and the actual wording still control. Agents may extract clauses and compare them with an approved evidence set. A person with procurement, legal and operations authority owns uncertain participation, local-presence and commitment decisions.

Agent handoff

Return evidence, uncertainty and the next decision together

The finished artifact has four linked records: the service envelope, location query plan, candidate-lot classification and exception log. Give each one a stable identifier and version. For a result, expose procedure, notice and lot identifiers, current source URL, extracted location text, field level, NUTS edition, all resolved sites, route evidence, state, reason, checked time and next permitted action. Keep the source passage close to the conclusion so another agent can verify it without reconstructing the search.

Agent authority should be explicit. An agent may run public searches, retrieve current notices, preserve location evidence, propose neighboring regions, calculate a labelled preliminary route and open a review item. It must stop when a controlling document is inaccessible, location sources conflict, geocoding confidence is weak, any required site breaches the envelope, eligibility wording is unclear or an exception would change staffing or commercial commitments. Publish only the operating assumptions needed to explain the filter. Crew rosters, customer addresses, private inventory positions and internal security details stay outside the public record.

• Identify the task, anchor, envelope version and responsible owner.
• Return the exact query and its execution time with each candidate set.
• Attach location passages, notice versions and lot identifiers.
• Expose unknown, mixed and eligibility-unresolved states without filling gaps.
• State the next permitted action and the person required to approve it.
• Refresh after an amendment, document release, classification change or operating change.