A compliance matrix straight from the tender documents

The requirements are scattered, and the time never covers them all

The requirements in a tender package are rarely in one place: the commercial ones sit in the administrative provisions, the technical ones in the specification, the quantities in the bill of quantities, and the decisive ones often in an appendix. During the tender period nobody has time to read everything equally carefully, and it is precisely the deprioritized appendix that tends to hold the line that costs. In one public procurement, every single bidder missed an item worth roughly 40,000 kronor; all were disqualified and the procurement had to be redone. We have written about that case before. The problem is rarely competence. It is volume against time.

The whole package in, one row per requirement out

Yesper reads the whole package regardless of format: PDF, Word, Excel, email, images and drawings, including scanned pages and handwritten notes via OCR. From that it:

• Extracts every requirement and separates mandatory from desirable, with a reference to the exact document, revision, page and line. That goes for the technical requirement, like weld class EN ISO 5817 level B or a prescribed compaction grade per AMA Anläggning, as much as for the commercial one: a required reference project of a certain size, a penalty clause tied to an interim deadline, or a requirement for an appointed safety coordinator.
• Cross-reads the documents against each other, technical specification against bill of quantities against drawings, and marks where they disagree: when the specification calls for an 80-centimetre sub-base while the type section shows 60, or when pressure testing of water mains is prescribed but has no item in the bill of quantities.
• Reads the commercial terms in the administrative provisions and checks them against AB 04 and ABT 06: penalties, warranty periods, insurance levels and liability caps, flagging deviations from the standard contract.
• Puts incoming subcontractor bids side by side and compares price, scope and reservations against the requirements, so the late subcontractor bid stops being a guess.
• Flags ambiguities, contradictions and unanswered requirements instead of guessing.

The result is a matrix with one row per requirement: the requirement, your answer, status (met, partly or not met) and source. You keep working directly in it, with the sources one click away and full version history, and export it in your own visual profile to Excel or Word. The material is fetched where it already lives: SharePoint, Teams, OneDrive or Dalux.

And Yesper does not make the decision. Under uncertainty the rule is to flag, and the final check stays with the estimator.

When it earns its place

• Large or complex packages where a full manual read-through does not fit in the time.
• Public procurements with hard mandatory requirements, where one missed requirement disqualifies the whole bid.
• When subcontractor bids land late and have to be checked against the requirements with minimal time left.
• When several disciplines' documents must agree and contradictions between specification, quantities and drawings need catching.
• When the commercial terms need review against AB 04 or ABT 06 before the bid binds you.
• Before go/no-go and before submission, as the safe step before anyone signs.

400 pages, 180 requirements, twelve unaddressed

Take a civil-works package of just over 400 pages. You gather the administrative provisions, technical specification, bill of quantities and drawings in the project and start the matrix. A few minutes later you have 180 identified requirements, twelve of them marked unaddressed. One is a weld-class requirement hidden in a technical appendix. Another is a contradiction: the specification requires dewatering throughout the excavation stage, but no item for it exists in the bill of quantities. A third is a penalty clause on an interim deadline that deviates from ABT 06. When the last subcontractor bids come in, Yesper puts them side by side against the requirements and flags a reservation one of them has made. You complete the answers, click through to the source to double-check, and export the matrix in your own template. The item that would otherwise have become a silent disqualification now sits as a visible row.

The careless read-through is what loses the bid

The compliance matrix rarely wins a bid on its own. But the careless read-through is often what loses it: immediately, in a disqualification, or later, as a change-order dispute over a line nobody read. The forty-five-minute meeting does not get shorter. It gets better, because for the first time it rests on someone having read the whole package.