A BOQ revision delta line freeze register should be a revision register linking each BOQ line to prior and current source references, delta description, affected supplier question, owner, freeze state and release note. Its release question is whether the current BOQ line is stable enough for the stated RFQ comparison or must remain conditional pending an authorized revision decision. 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 line controller 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 revision delta line freeze register control?
A BOQ line should not be compared against mixed revisions. Record the carrier input change, affected line and authorized freeze state so every shipping-instruction issuer receives the same bounded basis without inventing cargo counts or line boundary.
The core deliverable is a instruction revision register linking each BOQ line to prior and active carrier input references, delta description, affected shipping-instruction issuer question, owner, freeze state and instruction freeze note. It should be readable as a freeze decision record rather than a marketing presentation. The comparable test is whether the active BOQ line is stable enough for the stated RFQ comparison or must remain conditional pending an authorized instruction revision freeze decision. If the commercial review group cannot answer that question from frozen files, the BOQ delta 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 line 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 freeze state such as instruction-authorized is not substantiation by itself. Store the approving role, date, applicable line 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 BOQ change controller must decide what independent or destination-specific substantiation the project-specific control requires.
Minimum fields for the BOQ revision delta line freeze register
Use a structured register with one line row per item, package, freeze decision or revision 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 line controller find the same item across files? |
| Basis | instruction-authorized carrier input, instruction revision and line boundary | Is the active basis distinguishable from a proposal? |
| freeze state | Named owner, freeze decision and date | Is every revision 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 freeze state is interpreted. Put the BOQ change 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 boq change 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 RFQ line-freeze gate.
Prior revision
Treat prior revision 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 line controller 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 revision gap; the BOQ delta register must not silently choose the convenient answer.
Current revision
For current revision, 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 BOQ change controller's action; those are different roles. The boq change 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.
Delta description
Record delta description at the smallest level where the outcome can change independently. Project-wide totals hide unit, batch, package and zone differences, so the line row 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 delta register useful when the line boundary splits and allows RFQ line-freeze gate to be tested for only the affected portion.
Affected package
The owner of affected package 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 boq change controller keeps the former value as history so a line controller can see what changed and whether downstream handling of the BOQ line was updated.
Clarification owner
Use clarification owner 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. RFQ freeze requires revision-line-freeze evidence, not memory.
Freeze state
Before accepting freeze state, test it against one awkward example from the actual line 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 boq change controller should be able to export the BOQ delta register to another line controller and receive the same conclusion about the BOQ line and RFQ line-freeze gate.
Step-by-step workflow for BOQ revision delta line freeze register
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 source set
freeze the source set. Begin with the carrier-operative PO, BOQ, drawing, sample or shipment line boundary that governs this freeze decision. Mark its instruction revision and exclude superseded material from the working view. The boq change 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: Compare line and drawing references
compare line and drawing references. Visit the physical or digital carrier input rather than copying the previous freeze 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 boq change controller distinguishes what was seen, what was declared and what was authorized so revision-line-freeze evidence can support a bounded next action.
Step 3: Describe only evidenced deltas
describe only evidenced deltas. 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 boq change controller routes the revision gap to the role named by the project-specific control and prevents affected work from crossing RFQ line-freeze gate while the freeze decision is open.
Step 4: Link affected rfq questions
link affected RFQ questions. 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 line boundary unusable. The boq change controller records which related records need an update and which unaffected units may continue, creating a frozen boundary rather than a blanket transport instruction hold.
Step 5: Assign owners
assign owners. 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 boq change 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 delta register shows the follow-up substantiation required before final RFQ line-freeze gate.
Step 6: Record the authorized freeze
record the authorized freeze. Propagate the freeze decision into every operational file that still controls the BOQ line. That may include shipping-instruction issuer instruction, inspection line boundary, package map, cargo list or site receiving plan. Retain superseded revisions as history and prevent them from appearing active. The boq change 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 line changes unit
When a line changes unit, freeze the last undisputed shipment identity and separate the affected BOQ line from the remainder. The boq change 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 revision-line-freeze evidence can pass RFQ line-freeze gate; the unresolved portion receives its own owner and next check.
Case 2: A drawing changes a finish
If a drawing changes a finish, 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 boq change 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: A supplier quotes an older revision
Where a supplier quotes an older revision, compare the active 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 boq change controller may request clarification, containment or a new check, but cannot invent a criterion. The final disposition must identify both authority and revision-line-freeze evidence.
Case 4: An allowance is removed
For an allowance is removed, 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 boq change 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 late addendum arrives
With a late addendum arrives, treat the shipping-instruction issuer proposal as an input rather than an instruction-authorized resolution. Preserve the original requirement, the proposed action and the BOQ change controller's authorized response as separate submission lines. The boq change controller verifies implementation on the stated line boundary and records remaining exposure. A concession or schedule choice does not automatically prove technical conformity or satisfy RFQ line-freeze gate.
Related files and revision governance
For BOQ revision delta line freeze register, 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 revision delta line freeze register with a instruction revision, date, preparer and accountable approver. A change notice names the affected line rows 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 line boundary: none becomes a universal compliance statement merely because it is submission-connected to the procurement file.
Practical review exercise
Test the BOQ delta register with one real BOQ line and one deliberately difficult revision gap. Start at BOQ line identity, then trace prior revision, affected package and release note without verbal help from the preparer. Ask a second line controller to perform 'compare line and drawing references' and 'record the authorized freeze' from the submission-connected carrier inputs. Next, simulate the case a line changes unit while keeping the original order and substantiation history visible. The line controller should be able to identify the bounded freeze decision, the unresolved portion, the next owner and the exact revision-line-freeze evidence required before RFQ line-freeze gate. If two line controllers 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 revision delta line freeze register
Complete the checklist against the BOQ revision delta line freeze register 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 revision 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 line controllers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for active releases.
- The final record names preparer, approver, issue date and instruction revision.
Request a BOQ revision-delta review
To evaluate this control within a real sourcing package, use the project references and upload the BOQ, active drawings, schedules, sample register and any existing BOQ revision delta line freeze register. 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 line 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
The carrier inputs support the general control concepts identified above. Standards and public guidance must be read in their own line boundary and active edition. A reference here is not a declaration that a particular product, shipment, shipping-instruction issuer or HOMESEE service complies with it.