A VGM source and acknowledgment record should be a VGM source-and-acknowledgment record linking the final packed-container identity to the approved weighing method, contributing weight sources, tare source, responsible shipper, submission timestamp, recipient acknowledgment and later correction trail. Its release question is whether the verified gross mass information for the final packed container has a controlled source and has reached the required carrier and terminal handoff without treating an estimate as verified data. 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 vgm checker are the same confirmed HOMESEE representative; this is not an independent technical document review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement use decision this record controls
- Minimum transmittal cells and substantiation
- A step-by-step workflow
- A document-use decision matrix
- Category and edge-case handling
- Governance and change control
- Buyer checklist
- HOMESEE RFQ document review
- information requirements
What procurement decision does a VGM source and acknowledgment record control?
A packing-list total is not automatically a verified gross mass. The shipment file must identify the final container, transmittal-authorized method, information requirement records, responsible shipper, submission and acknowledgment while leaving legal method approval to the competent authority and logistics professionals.
The core deliverable is a VGM source-and-acknowledgment record linking the final packed-container document identity to the transmittal-authorized weighing method, contributing weight information requirements, tare information requirement, responsible shipper, submission timestamp, recipient acknowledgment and later correction trail. It should be readable as a use decision record rather than a marketing presentation. The vgm-usable test is whether the verified gross mass information for the final packed container has a vgm-controlled information requirement and has reached the required carrier and terminal handoff without treating an estimate as verified data. If the vgm review group cannot answer that question from vgm-controlled files, the VGM source record 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, post-award information plan specifications, qualified designers, relevant authorities and product-specific substantiation. HOMESEE should be evaluated only against the packed-container boundary and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-controlled item or use decision ID even when supplier document producer references change. Supplier document producer 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 vgm state such as transmittal-authorized is not substantiation by itself. Store the approving role, date, applicable packed-container boundary, information requirement document and transmittal revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, output count or authorization. A supplier document producer declaration can identify a claim, but the VGM handoff controller must decide what independent or destination-specific substantiation the project-specific control requires.
Minimum fields for the VGM source and acknowledgment record
Use a structured register with one weight source per item, package, use decision or VGM gap at the level where the outcome can change independently. The table below is a transmittal cell model, not a HOMESEE post-award information plan record.
| Control transmittal cell | Required treatment | document-use decision test |
|---|---|---|
| document identity | Stable ID plus native references | Can a vgm checker find the same item across files? |
| Basis | transmittal-authorized information requirement, transmittal revision and packed-container boundary | Is the vgm-active basis distinguishable from a proposal? |
| vgm state | Named owner, use decision and date | Is every VGM gap visible and actionable? |
| substantiation | delivery-connected file and limitation | Does the substantiation support only the claim being made? |
| Downstream action | Affected order, inspection, package or receiving record | Was the use decision propagated? |
Container and booking identity
Record container and booking identity at the smallest level where the outcome can change independently. Project-wide totals hide unit, batch, package and zone differences, so the weight source must show the applicable packed container, output count or range. Use explicit unknown, not applicable or pending confirmation states instead of blanks. That discipline keeps the VGM source record useful when the packed-container boundary splits and allows VGM handoff gate to be tested for only the affected portion.
Final cargo revision
The owner of final cargo revision is the role able to correct its information requirement, 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 document line until its relationship to the document-operative transmittal revision is transmittal-entered. The vgm handoff controller keeps the former value as history so a vgm checker can see what changed and whether downstream handling of the packed container was updated.
Approved vgm method reference
Use approved VGM method reference to connect the commercial line with the physical packed container. 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 document identity away. handoff closure requires weight-source and acknowledgment evidence, not memory.
Package and securing-material weight source
Before accepting package and securing-material weight source, test it against one awkward example from the actual packed-container boundary. Ask whether a partial output 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 delivery-connected record. The vgm handoff controller should be able to export the VGM source record to another vgm checker and receive the same conclusion about the packed container and VGM handoff gate.
Container tare source
At document-use decision, container tare source needs a final timestamp and accountable use decision. The document line identifies what was checked, what was not checked and which information requirement remained provisional. It must not imply price, MOQ, lead time, certification, capacity or destination compliance. Those claims require their own post-award information plan substantiation. The vgm handoff controller signs only the bounded use decision supported by weight-source and acknowledgment evidence and leaves unresolved packed-container boundary outside VGM handoff gate.
Responsible shipper and signer
responsible shipper and signer establishes document identity before any vgm state is interpreted. Put the VGM handoff controller reference beside the information requirement reference, transmittal revision and observation date. If the value came from a supplier document producer message, retain the message as a dated input rather than converting it into a post-award information plan fact. The vgm handoff controller checks that the transmittal cell describes only the packed container inside the stated boundary and records the next person who must verify it before VGM handoff gate.
Submission and acknowledgment event
Treat submission and acknowledgment event as a use decision input, not a decorative column. Name the file, transmittal revision, issuer and effective date that support it, then state what remains unknown. The document line should let a second vgm checker reconstruct why this packed container is included, excluded, held or released without calling the preparer. Where two information requirements disagree, preserve both values and open a visible VGM gap; the VGM source record must not silently choose the convenient answer.
Step-by-step workflow for VGM source and acknowledgment record
Run the workflow as delivery-connected gates. A later gate does not repair an undocumented earlier use 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 packed-container population
freeze the packed-container population. Visit the physical or digital information requirement rather than copying the previous vgm state. Reconcile identities, units, output counts and package boundaries, and capture the observation date. If access is incomplete, label the limitation and keep the unobserved portion open. The vgm handoff controller distinguishes what was seen, what was declared and what was authorized so weight-source and acknowledgment evidence can support a bounded next action.
Step 2: Confirm the permitted weighing route
confirm the permitted weighing route. Compare the new input with the transmittal-authorized reference set. Differences are logged at packed container level with both values, their information requirements and likely downstream files. Do not resolve a mismatch by overwriting the older value or averaging conflicting output counts. The vgm handoff controller routes the VGM gap to the role named by the project-specific control and prevents affected work from crossing VGM handoff gate while the use decision is open.
Step 3: Reconcile contributing source records
reconcile contributing source records. Test dependencies before acting. Check whether this packed container shares a batch, accessory, interface, package, document total or installation sequence with another line. A seemingly local change can make an adjacent packed-container boundary unusable. The vgm handoff controller records which related records need an update and which unaffected units may continue, creating a vgm-controlled boundary rather than a blanket post-award information plan hold.
Step 4: Identify the responsible shipper
identify the responsible shipper. Apply the agreed post-award information plan rule and cite it. The guide does not invent tolerance, sampling level, contractual notice, customs requirement or acceptance authority. The vgm handoff controller states the proposed outcome, obtains the authorized use decision and records any reservation. Where the information requirement supports only a provisional conclusion, the VGM source record shows the follow-up substantiation required before final VGM handoff gate.
Step 5: Submit before the applicable cut-off
submit before the applicable cut-off. Propagate the use decision into every operational file that still controls the packed container. That may include supplier document producer instruction, inspection packed-container boundary, package map, cargo list or site receiving plan. Retain superseded revisions as history and prevent them from appearing vgm-active. The vgm handoff controller verifies the same document identity and output count after the update rather than assuming transmission proves implementation.
Step 6: Retain acknowledgment
retain acknowledgment. Close with a backward-and-forward trace. Starting from the physical packed container, locate its buyer line and vgm-active substantiation; then start from the VGM handoff controller line and locate the object or remaining balance. Any broken link becomes an VGM gap with an owner. The vgm handoff controller records the document-use decision time, use decision packed-container boundary and limitation so another vgm checker can repeat the test after handover.
Edge cases that need an explicit rule
Case 1: Repacking changes the weight source
Where repacking changes the weight source, compare the vgm-active condition with the transmittal-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 vgm handoff controller may request clarification, containment or a new check, but cannot invent a criterion. The final disposition must identify both authority and weight-source and acknowledgment evidence.
Case 2: The container is swapped after weighing
For the container is swapped after weighing, map the downstream consequence before choosing a remedy. Inspection, packing, document, loading and site-receiving files may each hold the old document identity or output count. The vgm handoff controller lists the affected records and prevents silent reuse of superseded information. The use decision is closed only after the physical packed container and every document-operative operational reference agree.
Case 3: Tare data is copied from the wrong unit
With tare data is copied from the wrong unit, treat the supplier document producer proposal as an input rather than an transmittal-authorized resolution. Preserve the original requirement, the proposed action and the VGM handoff controller's authorized response as separate document lines. The vgm handoff controller verifies implementation on the stated packed-container boundary and records remaining exposure. A concession or schedule choice does not automatically prove technical conformity or satisfy VGM handoff gate.
Case 4: The carrier receives a value without acknowledgment
When the carrier receives a value without acknowledgment, freeze the last undisputed document identity and separate the affected packed container from the remainder. The vgm handoff controller records what changed, who observed it and which post-award information plan information requirement will decide the outcome. Existing photos or totals stay as history. Only the bounded portion with weight-source and acknowledgment evidence can pass VGM handoff gate; the unresolved portion receives its own owner and next check.
Case 5: A correction overwrites the first submission
If a correction overwrites the first submission, do not force the register to show a clean total. Split the line by unit, batch, package, zone or transmittal revision until each outcome can be stated honestly. The vgm handoff controller reconciles the sum back to the original order and labels every provisional balance. This keeps a partial use decision from being misread as acceptance or document-use decision of all related packed containers.
Related files and revision governance
For VGM source and acknowledgment record, keep the operating file connected to the cross-category finish schedule, mixed-material AQL plan and export packaging specification. Plan sampling in the container-loading evidence plan, state protection in the supplier document requirements, and link final placement to the HOMESEE sourcing services. Before an order, reconcile the project inquiry form. Commercial context remains in project references, project-specific files go through the BOQ normalization guide, and published material submittal register guide is a reference rather than a guaranteed outcome.
Issue the VGM source and acknowledgment record with a transmittal revision, date, preparer and accountable approver. A change notice names the affected weight sources and downstream files; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the document-operative register. Standards, photographs, declarations and sampling reports retain their own packed-container boundary: none becomes a universal compliance statement merely because it is delivery-connected to the procurement file.
Practical review exercise
Test the VGM source record with one real packed container and one deliberately difficult VGM gap. Start at container and booking identity, then trace final cargo revision, container tare source and correction and superseded record without verbal help from the preparer. Ask a second vgm checker to perform 'confirm the permitted weighing route' and 'retain acknowledgment' from the delivery-connected information requirements. Next, simulate the case repacking changes the weight source while keeping the original order and substantiation history visible. The vgm checker should be able to identify the bounded use decision, the unresolved portion, the next owner and the exact weight-source and acknowledgment evidence required before VGM handoff gate. If two vgm checkers reach different conclusions, improve the information requirement reference or transmittal cell definition rather than adding an undocumented assumption. This exercise validates traceability and use decision clarity; it does not validate price, lead time, certification, factory capacity or destination compliance.
Buyer checklist for VGM source and acknowledgment record
Complete the checklist against the VGM source and acknowledgment record source set, not from memory:
- A stable buyer-controlled ID exists for every affected packed container or use decision.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- supplier document producer references are mapped without replacing buyer identities.
- Proposed, submitted, transmittal-authorized, rejected and superseded states are distinct.
- Every VGM gap has an owner, due action and authorized use decision route.
- Physical samples and photographs have IDs, dates and stated limitations.
- output counts and units reconcile at the level needed for the document-use decision use decision.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified vgm checkers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for vgm-active releases.
- The final record names preparer, approver, issue date and transmittal revision.
Request a VGM evidence-chain review
To evaluate this control within a real sourcing package, use the BOQ normalization guide and upload the BOQ, vgm-active drawings, schedules, sample register and any existing VGM source and acknowledgment record. Include the destination, required-on-site context and the use decision dates your post-award information plan has actually transmittal-authorized. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined packed-container 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
- IMO verification of the gross mass of a packed container
- IMO/ILO/UNECE Code of Practice for Packing Cargo Transport Units
- ISO 9001 quality management systems overview
The information requirements support the general control concepts identified above. Standards and public guidance must be read in their own packed-container boundary and vgm-active edition. A reference here is not a declaration that a particular product, shipment, supplier document producer or HOMESEE service complies with it.