ResourcesCoverage

Coverage

Missing Tender Document Checklist

Distinguish a genuinely missing document from a bad reference, inaccessible link, renamed file, or non-applicable template.

03

Quick summary

Compare what the package says should exist with what was actually supplied, then keep unresolved gaps visible instead of burying them in assumptions.

01

Build an expected-versus-received inventory

  • Compare the download list with the instructions, tables of contents, drawing index, specification index, appendices, and schedules.

  • Record each expected item, where it is referenced, its revision, and whether it was received.

  • Confirm each file opens and contains every listed page or sheet.

  • Include documents and forms referenced from pricing workbooks and addenda.

02

Test the apparent gap

  • Search alternate names, abbreviations, and file extensions.

  • Check whether the item is embedded inside another PDF or hidden workbook sheet.

  • Test external links and check whether an addendum replaced, withdrew, or renamed the item.

  • Confirm the reference belongs to this project rather than a reused template.

03

Classify and resolve

  • Use a clear status: bid blocker, pricing risk, clarification required, or background.

  • Send a written question before the deadline and cite the exact source reference.

  • Do not silently substitute an older project document.

  • Record the official response, update the package inventory, and keep unresolved gaps visible.

Common pitfalls

Keep these visible during review.

  • Treating a broken hyperlink as proof the document is optional.
  • Assuming a similarly named drawing is the missing drawing.
  • Marking a blank workbook quantity as zero without confirmation.
  • Reconstructing requirements from an older tender.
  • Letting an automated “not found” result replace a manual package check.

Where MESTRE fits

Organize the review. Keep the judgment human.

MESTRE helps surface references to documents that may not be present and connects the finding back to its source for estimator confirmation.