A BOQ unit pack count reconciliation should be a reconciliation register linking each BOQ line to its unit basis, supplier pack reference, quoted quantity, conversion note, source revision and unresolved balance. Its release question is whether the line can be compared on the stated unit basis without inventing a conversion, price, MOQ or supplier capability. Build the record before ordering or shipment, keep open points visible, and require an authorized buyer decision for every exception; the framework does not replace project specifications, contracts, or destination rules.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: September 8, 2026
Corrections: Send documented corrections through the HOMESEE contact page.
Editorial note: The author and photo checker are the same confirmed HOMESEE representative; this is not an independent technical instruction review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement freeze decision this record controls
- Minimum instruction cells and substantiation
- A step-by-step workflow
- A instruction freeze matrix
- Category and edge-case handling
- Governance and change control
- Buyer checklist
- HOMESEE RFQ instruction review
- carrier inputs
What procurement decision does a BOQ unit pack count reconciliation control?
A pack count is not automatically a BOQ cargo count. Keep the unit-reconciliation controller unit, shipping-instruction issuer pack reference and conversion carrier input separate so a comparison remains conditional when the substantiation is incomplete.
The core deliverable is a reconciliation register linking each BOQ line to its unit basis, shipping-instruction issuer pack reference, quoted cargo count, conversion note, carrier input instruction revision and unresolved balance. It should be readable as a freeze decision record rather than a marketing presentation. The retrievable test is whether the line can be compared on the stated unit basis without inventing a conversion, price, MOQ or shipping-instruction issuer capability. If the inspection review group cannot answer that question from indexed files, the BOQ unit register is not ready, even if individual participants believe they remember the answer.
This guide describes a buyer-side control method. It does not establish a legal duty, a technical tolerance, a test method or a destination compliance result. Those come from the signed contract, transport instruction specifications, qualified designers, relevant authorities and product-specific substantiation. HOMESEE should be evaluated only against the evidence boundary and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-controlled item or freeze decision ID even when shipping-instruction issuer references change. Shipping-instruction issuer model names, carton numbers and report numbers remain valuable, but they should be mapped to the stable ID rather than replacing it. That approach preserves continuity between a BOQ, a finish schedule, a sample, a drawing, an order, an inspection record and a package mark.
Keep status separate from evidence
A evidence state such as instruction-authorized is not substantiation by itself. Store the approving role, date, applicable evidence boundary, carrier input document and instruction revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, cargo count or authorization. A shipping-instruction issuer declaration can identify a claim, but the unit-reconciliation controller must decide what independent or destination-specific substantiation the project-specific control requires.
Minimum fields for the BOQ unit pack count reconciliation
Use a structured register with one photo entry per item, package, freeze decision or metadata gap at the level where the outcome can change independently. The table below is a instruction cell model, not a HOMESEE transport instruction record.
| Control instruction cell | Required treatment | instruction freeze test |
|---|---|---|
| shipment identity | Stable ID plus native references | Can a photo checker find the same item across files? |
| Basis | instruction-authorized carrier input, instruction revision and evidence boundary | Is the captured basis distinguishable from a proposal? |
| evidence state | Named owner, freeze decision and date | Is every metadata gap visible and actionable? |
| substantiation | submission-connected file and limitation | Does the substantiation support only the claim being made? |
| Downstream action | Affected order, inspection, package or receiving record | Was the freeze decision propagated? |
Boq line identity
BOQ line identity establishes shipment identity before any evidence state is interpreted. Put the unit-reconciliation controller reference beside the carrier input reference, instruction revision and observation date. If the value came from a shipping-instruction issuer message, retain the message as a dated input rather than converting it into a transport instruction fact. The unit-reconciliation controller checks that the instruction cell describes only the BOQ line inside the stated boundary and records the next person who must verify it before comparison release gate.
Buyer unit basis
Treat buyer unit basis as a freeze decision input, not a decorative column. Name the file, instruction revision, issuer and effective date that support it, then state what remains unknown. The submission line should let a second photo checker reconstruct why this BOQ line is included, excluded, held or released without calling the preparer. Where two carrier inputs disagree, preserve both values and open a visible metadata gap; the BOQ unit register must not silently choose the convenient answer.
Supplier pack reference
For supplier pack reference, distinguish observation from forecast and authorization from substantiation. A photograph may show visible condition on one date, a declaration may identify the shipping-instruction issuer's position, and an instruction-authorized transport instruction file may control the unit-reconciliation controller's action; those are different roles. The unit-reconciliation controller links the applicable carrier input, notes its limitation and prevents the instruction cell from being reused for a broader BOQ line population than the substantiation actually covers.
Quoted quantity
Record quoted quantity at the smallest level where the outcome can change independently. Project-wide totals hide unit, batch, package and zone differences, so the photo entry must show the applicable BOQ line, cargo count or range. Use explicit unknown, not applicable or pending confirmation states instead of blanks. That discipline keeps the BOQ unit register useful when the evidence boundary splits and allows comparison release gate to be tested for only the affected portion.
Conversion source
The owner of conversion source is the role able to correct its carrier input, not merely the person typing the register. Capture the requested action, due point and authorized escalation path. A later email or spreadsheet does not supersede the submission line until its relationship to the carrier-operative instruction revision is instruction-entered. The unit-reconciliation controller keeps the former value as history so a photo checker can see what changed and whether downstream handling of the BOQ line was updated.
Revision and date
Use revision and date to connect the commercial line with the physical BOQ line. The value should reconcile with the applicable drawing, sample, inspection, package or shipment reference, while respecting the different purpose of each record. When repacking, rework, substitution or split shipment changes that relationship, create a traceable event instead of editing the old shipment identity away. evidence closure requires unit-pack-source evidence, not memory.
Unresolved balance
Before accepting unresolved balance, test it against one awkward example from the actual evidence boundary. Ask whether a partial cargo count, mixed batch, inaccessible package, revised drawing or held unit would still be represented correctly. If the answer depends on verbal context, add the missing qualifier or submission-connected record. The unit-reconciliation controller should be able to export the BOQ unit register to another photo checker and receive the same conclusion about the BOQ line and comparison release gate.
Step-by-step workflow for BOQ unit pack count reconciliation
Run the workflow as submission-connected gates. A later gate does not repair an undocumented earlier freeze decision; it merely makes the missing control harder and more expensive to find. The exact approval titles and contract notices belong to the project-specific control, but the sequence below gives procurement teams a reproducible starting point.
Step 1: Freeze the active boq
freeze the active BOQ. Begin with the carrier-operative PO, BOQ, drawing, sample or shipment evidence boundary that governs this freeze decision. Mark its instruction revision and exclude superseded material from the working view. The unit-reconciliation controller identifies the exact BOQ line population, the carrier input owner and the freeze decision due point. The output is a stable baseline against which later observations can be compared; it is not a promise that conditions will remain unchanged.
Step 2: Identify supplier pack references
identify supplier pack references. Visit the physical or digital carrier input rather than copying the previous evidence state. Reconcile identities, units, cargo counts and package boundaries, and capture the observation date. If access is incomplete, label the limitation and keep the unobserved portion open. The unit-reconciliation controller distinguishes what was seen, what was declared and what was authorized so unit-pack-source evidence can support a bounded next action.
Step 3: Record unit bases
record unit bases. Compare the new input with the instruction-authorized reference set. Differences are logged at BOQ line level with both values, their carrier inputs and likely downstream files. Do not resolve a mismatch by overwriting the older value or averaging conflicting cargo counts. The unit-reconciliation controller routes the metadata gap to the role named by the project-specific control and prevents affected work from crossing comparison release gate while the freeze decision is open.
Step 4: Test conversion evidence
test conversion evidence. Test dependencies before acting. Check whether this BOQ line shares a batch, accessory, interface, package, document total or installation sequence with another line. A seemingly local change can make an adjacent evidence boundary unusable. The unit-reconciliation controller records which related records need an update and which unaffected units may continue, creating a indexed boundary rather than a blanket transport instruction hold.
Step 5: Reconcile quoted quantities
reconcile quoted quantities. Apply the agreed transport instruction rule and cite it. The guide does not invent tolerance, sampling level, contractual notice, customs requirement or acceptance authority. The unit-reconciliation controller states the proposed outcome, obtains the authorized freeze decision and records any reservation. Where the carrier input supports only a provisional conclusion, the BOQ unit register shows the follow-up substantiation required before final comparison release gate.
Step 6: Route gaps
route gaps. Propagate the freeze decision into every operational file that still controls the BOQ line. That may include shipping-instruction issuer instruction, inspection evidence boundary, package map, cargo list or site receiving plan. Retain superseded revisions as history and prevent them from appearing captured. The unit-reconciliation controller verifies the same shipment identity and cargo count after the update rather than assuming transmission proves implementation.
Edge cases that need an explicit rule
Case 1: A supplier uses a different unit
When a supplier uses a different unit, freeze the last undisputed shipment identity and separate the affected BOQ line from the remainder. The unit-reconciliation controller records what changed, who observed it and which transport instruction carrier input will decide the outcome. Existing photos or totals stay as history. Only the bounded portion with unit-pack-source evidence can pass comparison release gate; the unresolved portion receives its own owner and next check.
Case 2: A carton contains mixed items
If a carton contains mixed items, do not force the register to show a clean total. Split the line by unit, batch, package, zone or instruction revision until each outcome can be stated honestly. The unit-reconciliation controller reconciles the sum back to the original order and labels every provisional balance. This keeps a partial freeze decision from being misread as acceptance or instruction freeze of all related BOQ lines.
Case 3: The boq revision changes
Where the BOQ revision changes, compare the captured condition with the instruction-authorized reference under the viewing, measuring or access conditions defined by the project-specific control. Record the limitation if a meaningful comparison cannot be made. The unit-reconciliation controller may request clarification, containment or a new check, but cannot invent a criterion. The final disposition must identify both authority and unit-pack-source evidence.
Case 4: A conversion is assumed from memory
For a conversion is assumed from memory, map the downstream consequence before choosing a remedy. Inspection, packing, document, loading and site-receiving files may each hold the old shipment identity or cargo count. The unit-reconciliation controller lists the affected records and prevents silent reuse of superseded information. The freeze decision is closed only after the physical BOQ line and every carrier-operative operational reference agree.
Case 5: A partial pack is quoted
With a partial pack is quoted, treat the shipping-instruction issuer proposal as an input rather than an instruction-authorized resolution. Preserve the original requirement, the proposed action and the unit-reconciliation controller's authorized response as separate submission lines. The unit-reconciliation controller verifies implementation on the stated evidence boundary and records remaining exposure. A concession or schedule choice does not automatically prove technical conformity or satisfy comparison release gate.
Related files and revision governance
For BOQ unit pack count reconciliation, keep the operating file connected to the material submittal register guide, cross-category finish schedule and mixed-material AQL plan. Plan sampling in the export packaging specification, state protection in the container-loading evidence plan, and link final placement to the supplier document requirements. Before an order, reconcile the HOMESEE sourcing services. Commercial context remains in project inquiry form, project-specific files go through the project references, and published BOQ normalization guide is a reference rather than a guaranteed outcome.
Issue the BOQ unit pack count reconciliation with a instruction revision, date, preparer and accountable approver. A change notice names the affected photo entries and downstream files; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the carrier-operative register. Standards, photographs, declarations and sampling reports retain their own evidence boundary: none becomes a universal compliance statement merely because it is submission-connected to the procurement file.
Practical review exercise
Test the BOQ unit register with one real BOQ line and one deliberately difficult metadata gap. Start at BOQ line identity, then trace buyer unit basis, conversion source and comparison status without verbal help from the preparer. Ask a second photo checker to perform 'identify shipping-instruction issuer pack references' and 'route gaps' from the submission-connected carrier inputs. Next, simulate the case a supplier uses a different unit while keeping the original order and substantiation history visible. The photo checker should be able to identify the bounded freeze decision, the unresolved portion, the next owner and the exact unit-pack-source evidence required before comparison release gate. If two photo checkers reach different conclusions, improve the carrier input reference or instruction cell definition rather than adding an undocumented assumption. This exercise validates traceability and freeze decision clarity; it does not validate price, lead time, certification, factory capacity or destination compliance.
Buyer checklist for BOQ unit pack count reconciliation
Complete the checklist against the BOQ unit pack count reconciliation source set, not from memory:
- A stable buyer-controlled ID exists for every affected BOQ line or freeze decision.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- shipping-instruction issuer references are mapped without replacing buyer identities.
- Proposed, submitted, instruction-authorized, rejected and superseded states are distinct.
- Every metadata gap has an owner, due action and authorized freeze decision route.
- Physical samples and photographs have IDs, dates and stated limitations.
- cargo counts and units reconcile at the level needed for the instruction freeze freeze decision.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified photo checkers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for captured releases.
- The final record names preparer, approver, issue date and instruction revision.
Request a BOQ unit-reconciliation review
To evaluate this control within a real sourcing package, use the project references and upload the BOQ, captured drawings, schedules, sample register and any existing BOQ unit pack count reconciliation. Include the destination, required-on-site context and the freeze decision dates your transport instruction has actually instruction-authorized. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined evidence boundary and organize an RFQ discussion against those files. The response should be assessed against the project-specific control's technical, contractual and destination requirements. Sending information does not create a claim about price, MOQ, lead time, certification, production capacity or outcome.
Sources
- ISO 9001 quality management overview
- ISO 10005:2018 guidelines for quality plans
- GS1 Global Traceability Standard
The carrier inputs support the general control concepts identified above. Standards and public guidance must be read in their own evidence boundary and captured edition. A reference here is not a declaration that a particular product, shipment, shipping-instruction issuer or HOMESEE service complies with it.