A RFQ addendum acknowledgment register should be an addendum register linking each issued change to affected BOQ lines, drawings, recipients, receipt evidence, bidder acknowledgment, quotation impact and the controlling RFQ revision. Its release question is whether every invited bidder is pricing the same controlled bid package and whether any response must remain on hold until an addendum is acknowledged. 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 addendum 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 RFQ addendum acknowledgment register control?
When an RFQ changes, emailing a revised file is not enough. Buyers need a addendum-controlled record of what changed, who received it and which quotation instruction revision incorporates it, without treating silence as acceptance.
The core deliverable is an addendum register linking each issued change to affected BOQ lines, drawings, recipients, receipt substantiation, bidder acknowledgment, quotation impact and the controlling RFQ revision. It should be readable as a freeze decision record rather than a marketing presentation. The addendum-usable test is whether every invited bidder is pricing the same addendum-controlled bid package and whether any response must remain on hold until an addendum is acknowledged. If the addendum review group cannot answer that question from addendum-controlled files, the addendum 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 bid-revision 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 addendum state such as instruction-authorized is not substantiation by itself. Store the approving role, date, applicable bid-revision 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 bid-package controller must decide what independent or destination-specific substantiation the project-specific control requires.
Minimum fields for the RFQ addendum acknowledgment register
Use a structured register with one addendum line per item, package, freeze decision or acknowledgment 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 addendum checker find the same item across files? |
| Basis | instruction-authorized carrier input, instruction revision and bid-revision boundary | Is the addendum-active basis distinguishable from a proposal? |
| addendum state | Named owner, freeze decision and date | Is every acknowledgment 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? |
Addendum identity and issue time
addendum identity and issue time establishes shipment identity before any addendum state is interpreted. Put the bid-package 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 bid-package controller checks that the instruction cell describes only the RFQ revision inside the stated boundary and records the next person who must verify it before bid-revision gate.
Affected rfq and boq revision
Treat affected RFQ and BOQ 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 addendum checker reconstruct why this RFQ revision is included, excluded, held or released without calling the preparer. Where two carrier inputs disagree, preserve both values and open a visible acknowledgment gap; the addendum register must not silently choose the convenient answer.
Changed drawing or specification
For changed drawing or specification, 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 bid-package controller's action; those are different roles. The bid-package controller links the applicable carrier input, notes its limitation and prevents the instruction cell from being reused for a broader RFQ revision population than the substantiation actually covers.
Recipient and delivery channel
Record recipient and delivery channel at the smallest level where the outcome can change independently. Project-wide totals hide unit, batch, package and zone differences, so the addendum line must show the applicable RFQ revision, cargo count or range. Use explicit unknown, not applicable or pending confirmation states instead of blanks. That discipline keeps the addendum register useful when the bid-revision boundary splits and allows bid-revision gate to be tested for only the affected portion.
Receipt evidence
The owner of receipt evidence 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 bid-package controller keeps the former value as history so a addendum checker can see what changed and whether downstream handling of the RFQ revision was updated.
Bidder acknowledgment
Use bidder acknowledgment to connect the commercial line with the physical RFQ revision. 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. bid closure requires issue-receipt-acknowledgment evidence, not memory.
Quotation impact response
Before accepting quotation impact response, test it against one awkward example from the actual bid-revision 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 bid-package controller should be able to export the addendum register to another addendum checker and receive the same conclusion about the RFQ revision and bid-revision gate.
Step-by-step workflow for RFQ addendum acknowledgment 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 original bidder list
freeze the original bidder list. Begin with the carrier-operative PO, BOQ, drawing, sample or shipment bid-revision boundary that governs this freeze decision. Mark its instruction revision and exclude superseded material from the working view. The bid-package controller identifies the exact RFQ revision 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: Number and describe the addendum
number and describe the addendum. Visit the physical or digital carrier input rather than copying the previous addendum 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 bid-package controller distinguishes what was seen, what was declared and what was authorized so issue-receipt-acknowledgment evidence can support a bounded next action.
Step 3: Map affected commercial and technical files
map affected commercial and technical files. Compare the new input with the instruction-authorized reference set. Differences are logged at RFQ revision 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 bid-package controller routes the acknowledgment gap to the role named by the project-specific control and prevents affected work from crossing bid-revision gate while the freeze decision is open.
Step 4: Issue one controlled package
issue one controlled package. Test dependencies before acting. Check whether this RFQ revision shares a batch, accessory, interface, package, document total or installation sequence with another line. A seemingly local change can make an adjacent bid-revision boundary unusable. The bid-package controller records which related records need an update and which unaffected units may continue, creating a addendum-controlled boundary rather than a blanket transport instruction hold.
Step 5: Capture receipt and acknowledgment separately
capture receipt and acknowledgment separately. 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 bid-package controller states the proposed outcome, obtains the authorized freeze decision and records any reservation. Where the carrier input supports only a provisional conclusion, the addendum register shows the follow-up substantiation required before final bid-revision gate.
Step 6: Reconcile bidder responses
reconcile bidder responses. Propagate the freeze decision into every operational file that still controls the RFQ revision. That may include shipping-instruction issuer instruction, inspection bid-revision boundary, package map, cargo list or site receiving plan. Retain superseded revisions as history and prevent them from appearing addendum-active. The bid-package 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 bidder misses one attachment
When a bidder misses one attachment, freeze the last undisputed shipment identity and separate the affected RFQ revision from the remainder. The bid-package 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 issue-receipt-acknowledgment evidence can pass bid-revision gate; the unresolved portion receives its own owner and next check.
Case 2: A late drawing changes quantity
If a late drawing changes quantity, 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 bid-package 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 RFQ revisions.
Case 3: One bidder responds before the addendum
Where one bidder responds before the addendum, compare the addendum-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 bid-package controller may request clarification, containment or a new check, but cannot invent a criterion. The final disposition must identify both authority and issue-receipt-acknowledgment evidence.
Case 4: An addendum replaces a prior clarification
For an addendum replaces a prior clarification, 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 bid-package controller lists the affected records and prevents silent reuse of superseded information. The freeze decision is closed only after the physical RFQ revision and every carrier-operative operational reference agree.
Case 5: The due date changes for only approved reasons
With the due date changes for only approved reasons, treat the shipping-instruction issuer proposal as an input rather than an instruction-authorized resolution. Preserve the original requirement, the proposed action and the bid-package controller's authorized response as separate submission lines. The bid-package controller verifies implementation on the stated bid-revision boundary and records remaining exposure. A concession or schedule choice does not automatically prove technical conformity or satisfy bid-revision gate.
Related files and revision governance
For RFQ addendum acknowledgment 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 RFQ addendum acknowledgment register with a instruction revision, date, preparer and accountable approver. A change notice names the affected addendum lines 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 bid-revision boundary: none becomes a universal compliance statement merely because it is submission-connected to the procurement file.
Practical review exercise
Test the addendum register with one real RFQ revision and one deliberately difficult acknowledgment gap. Start at addendum identity and issue time, then trace affected RFQ and BOQ revision, receipt evidence and controlling bid-package status without verbal help from the preparer. Ask a second addendum checker to perform 'number and describe the addendum' and 'reconcile bidder responses' from the submission-connected carrier inputs. Next, simulate the case a bidder misses one attachment while keeping the original order and substantiation history visible. The addendum checker should be able to identify the bounded freeze decision, the unresolved portion, the next owner and the exact issue-receipt-acknowledgment evidence required before bid-revision gate. If two addendum 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 RFQ addendum acknowledgment register
Complete the checklist against the RFQ addendum acknowledgment register source set, not from memory:
- A stable buyer-controlled ID exists for every affected RFQ revision 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 acknowledgment 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 addendum checkers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for addendum-active releases.
- The final record names preparer, approver, issue date and instruction revision.
Request an RFQ addendum control review
To evaluate this control within a real sourcing package, use the project references and upload the BOQ, addendum-active drawings, schedules, sample register and any existing RFQ addendum acknowledgment 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 bid-revision 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 systems overview
- ISO 19650-1 information management concepts and principles
- UN/CEFACT trade and transport standards
The carrier inputs support the general control concepts identified above. Standards and public guidance must be read in their own bid-revision boundary and addendum-active edition. A reference here is not a declaration that a particular product, shipment, shipping-instruction issuer or HOMESEE service complies with it.