Skip to content

Use case

Tender Evaluation

Check every bid against the same published criteria. Each criterion gets the passage in the bid that answers it, cited to its page, so evaluators score from evidence rather than from memory.

Who runs it

Who this review is for

Procurement and evaluation teams who assess supplier bids against published requirements and award criteria, and have to show how each response was read.

Requirements

Requirements you can run

You write each requirement in your own words. These are examples of the kind a reviewer runs.

  • “Show the bidder’s evidence of comparable contracts delivered in the last five years.”
  • “Show the bidder’s ISO 27001 certificate or equivalent information-security accreditation.”
  • “Show how the bidder will meet the four-hour response time.”
  • “Show the bidder’s proposed account management structure and named roles.”

Documents it typically reads

  • Bid responses
  • Method statements
  • Case studies and references
  • Certificates
  • Pricing schedules (XLSX)
  • Clarification responses

How it runs

From upload to decision

  1. Step 1

    Upload each bid into its own workspace or programme

    Keeping bids apart keeps every citation attributable to one bidder.

  2. Step 2

    Run the same requirements for every bidder

    One programme per bidder, with the same criteria in the same words, so findings line up across bids.

  3. Step 3

    Run it

    Each criterion gets the passage that answers it, with the file and page cited, or a plain statement that the bid does not address it.

  4. Step 4

    A named reviewer decides

    Each finding is confirmed, rejected or marked for follow-up by a person. The decision is attributed and logged, and the run exports as DOCX, XLSX, CSV or JSON with every finding, its sources and the decision.

Key to findings

…certificate valid until 2 March 2028…
Evidence located
A passage DataStruct could support against the requirement, shown with its file, page and section, or its sheet and rows.
…annual review completed…
Cited, not confirmed
A source the answer relied on that DataStruct could not confirm as support. Listed first, so the reviewer opens it first.
…the policy requires an annual test…
Related material
Returned by the search and not used as evidence. Kept apart so it never reads as proof.
[ no supporting passage ]
No supporting evidence located
Nothing in the set supports the requirement. The finding says so and names what is missing.
Confirmed · reviewer

Only a named person can confirm, reject or mark a finding for follow-up. The decision is attributed and logged. Green is theirs alone: no system state is ever shown in green.

The boundary

What it does not do

  • It does not score or rank bids. Evaluators score; DataStruct shows where each answer is.
  • It sees only what a bidder submitted. It cannot verify references or claims outside the documents.
  • It can miss a relevant passage, so evaluators should still read the bid.

Questions

Common questions

Can it compare bidders side by side?

Each bidder’s run exports as XLSX or CSV with the same requirements in the same order, so the exports can be laid side by side.

Is the evaluation decision recorded?

Each finding carries the evaluator’s decision (Confirm, Reject or Needs follow-up), attributed and logged. Scores are kept in your own scoring process.

Try tender evaluation on your own documents

Book a demo and bring a sample of the documents this review runs on.