What is the difference between scan, match, and fill?
Scan turns tender files into structured requirements and form layout. Match compares those requirements to product data and flags gaps. Fill writes bidder responses into the buyer’s form using matched values and evidence, leaving residuals for humans. Stages are sequential in logic; teams may iterate when new product facts appear.How the stages differ
Scan takes tender files and produces structured requirements plus a cellmap. It fails when the wrong sheets or rows are mapped. Match takes those requirements plus product facts and produces compliance outcomes and residuals. It fails on false “meets” or missing evidence. Fill takes match results plus the cellmap and drafts the buyer template. It fails when values land in the wrong cells.Order that works
- Scan until structure is trusted
- Rank, then lock a product
- Formal match (hard limits first)
- Fill and residual review
- Export / deliver
Anti-patterns
- Filling without a match — invented or inconsistent cells
- Matching without a scan — no reliable requirement inventory
- Treating rank as fill-ready — rank is not formal compliance