Methodology

From official notice to a focused opportunity.

TenderScope applies a documented, bounded process to official TED data. The process improves discovery; it does not replace the original notice or promise perfect coverage.

01

Acquisition from TED

TenderScope retrieves notices server-side from the official TED Search API. Synchronizations use a bounded publication-date range, page size and maximum page count, then record progress so later runs can resume. Page requests never call TED directly.

The raw response envelope is validated before notices are processed. A malformed response fails safely; individual notices that cannot be normalized are skipped and recorded as compact quality issues.

02

Normalization

Multilingual fields are selected in a stable language order while the source wording is preserved—TenderScope does not claim to translate it. Country codes are normalized for filtering, source identifiers remain attached, and a stable content hash detects meaningful updates.

Keyword search operates on normalized titles, buyers, summaries, countries, categories and CPV fields. Missing descriptions, buyers or places are displayed as not published rather than inferred.

03

Classification

Official CPV codes provide the classification base. TenderScope maps a verified subset to practical categories for web development, software development, software maintenance, database systems and IT consulting. Notices without a supported mapping are skipped rather than forced into an inaccurate category.

Category labels are a discovery aid. The official CPV classification and notice remain authoritative.

Review current category coverage
04

Dates, lots and values

Publication dates are normalized as calendar dates. A deadline with a verified source time is displayed with that time; otherwise it is treated as an all-day date. For multiple lots, TenderScope shows the earliest known deadline and labels it accordingly.

A notice-level estimated value is preferred. A lot-level value is used only when a single lot can be identified reliably. Multiple lot values are not summed unless the official notice supplies a procedure total. Missing amounts and currencies remain undisclosed.

05

Quality controls

A visible record must have a stable TED publication number, supported CPV mapping, title and safe official TED URL. Content hashes distinguish inserted, updated and unchanged records. Skipped records and bounded-run warnings are grouped for review without storing full raw payloads or unnecessary personal contact data.

Every opportunity links back to its official notice for verification. Synchronization status may be unavailable when stored data cannot be reached; internal errors and connection details are not exposed.

06

Known limitations

Coverage is limited to the configured TED query, supported CPV mapping, bounded synchronization window and fields returned by TED. Source data may be delayed, revised, multilingual, incomplete or structured across several lots. TenderScope may therefore omit a relevant opportunity or show a field as unavailable.

Read the service disclaimer