Know which fence document is current, who has it, and what happens next.

Track required and received drawings, product data, reports, certificates and shipping records by identifier, revision, reviewer, response and next action.

This register tracks document movement. It does not create document requirements, validate a certificate, approve technical content, release production, determine legal retention or accept delivered products.

A file called “final.pdf” is not enough. Give every item a stable register ID, preserve each revision and response, and make the current action owner visible.

1. Set the register basis

Project / location____________________________
Register ID / revision____________________________
Prepared by / date____________________________
Project document procedureID ______ Rev ______
Current quote / POID ______ Rev ______
Register owner____________________________

Build the required-document list from the project specification, purchase order and agreed review route. A document type appearing below is an example, not a universal requirement.

2. List what is required before chasing files

Required-document matrix
Register IDDocument type / descriptionRequirement sourceIssuerReviewerRequired by / purpose
SUB-001Layout / shop drawingSpec / PO ______________________Review / record / other
SUB-002Product data sheetSpec / PO ______________________Review / record / other
SUB-003Test report / certificate, if requiredSpec / PO ______________________Review / record / other
SUB-004Packing / origin / shipping documentSpec / PO ______________________Review / record / other

Write the clause, drawing, purchase-order line or agreed schedule that creates the requirement. If no source is found, mark “confirm requirement” instead of presenting the document as mandatory.

Connect the register to your material family

Start with the same requirement revision used in the RFQ draft and supplier response comparison. Give each required file its own register row; a material family is not a document ID. The candidates below are questions to tailor to your project, not a mandatory document package.

Material-specific document references to confirm
Material pathCandidate files, if requiredProduct references to matchReview question to assign
Woven wire meshProduct sheet; agreed pattern or roll schedule; finish or test evidence requested by the specification.Knot construction, height and mesh pattern, wire component descriptions, finish, roll format and the quoted item/revision. Record batch or lot coverage where the requirement calls for it.Which project-assigned reviewer will check the requested specification and whether each report identifies the relevant material? A generic certificate is not a match by itself.
Electric-fence componentsExact-model product data and manual; component/quantity list; power accessory information and evidence requested for the project.Model and regional version, power source, output-versus-stored energy data and stated conditions, included conductors/connections/accessories, manual ID and revision.Who is assigned to review model-specific compatibility and unanswered system questions? This register does not size an energizer, prescribe installation or verify compliance.
Tubular panels and gatesPanel/gate drawing; product sheet and fittings list; requested material, weld, finish or inspection evidence; package schedule.Drawing ID/revision, height/width/rail layout, tube sections and wall thickness, specified tolerances, lug/pin details, gate interfaces and item quantities.Who is assigned to review drawing departures and connection interfaces? File receipt does not demonstrate structural suitability or approve a substitution.

Material examples draw on Virginia Cooperative Extension’s energizer guide — https://www.pubs.ext.vt.edu/content/pubs_ext_vt_edu/en/SPES/spes-689/spes-689.html and HUADE’s panel catalogue — https://www.wiremeshmfg.com/corral-panels/. The catalogue is supplier information, not independent certification; neither source creates your project’s document requirements.

Close view of a galvanized woven-wire fence roll beside installed fence fabric
Connect each drawing, data sheet, report or certificate to the exact product description and revision it covers. A similar-looking roll is not proof that the document belongs to the ordered material.

3. Track submission, review and next action

Submission and review status
Register IDFile / document IDRevision / issue dateSubmitted / transmittalReviewerResponse / dateNext action / owner / due
________________Rev ___ / ______________________________________
________________Rev ___ / ______________________________________
________________Rev ___ / ______________________________________

Useful workflow states include “not requested,” “requested,” “received,” “under review,” “returned for revision,” “accepted for record,” “superseded” and “closed.” Use the project’s actual codes and record the formal response verbatim; never translate a reviewer’s response into stronger permission.

Two-column ruleKeep the formal reviewer response separate from the workflow status. A document can have a response and still have an open comment, missing attachment or downstream action.

Name the issuer, reviewer and action owner separately

Use the people and authority defined in your project procedure. The roles below are editorial workflow examples, not prescribed contractual responsibilities. One person may fill several roles, but the recorded action and authority still need to be clear.

Document routing responsibilities to confirm
ActionNamed role to recordReference to preserveBoundary
Confirm why a file is requestedBuyer/project requirement ownerRFQ/PO/specification line and revision; intended review purposeIf unclear, record “confirm requirement”; do not invent a mandatory certificate.
Issue or revise the fileActual issuer and submitting contactDocument ID, revision/date, transmittal and submitted file locationThe contact sending the file is not automatically its issuing authority.
Review the assigned questionProject-named reviewer and review scopeExact formal response, date, comment ID and reviewed revisionThe register owner cannot strengthen the reviewer’s response into approval.
Chase and record the next actionRegister owner and specific action ownerRequested correction/file, reply reference and agreed due dateRecording receipt does not close unresolved comments.
Distribute the identified revisionNamed distribution owner and recipientsCurrent file location, revision and distribution recordUse the project’s formal release route; this page gives no permission to proceed.

The August 2026 UFGS submittal guide — https://www.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2033%2000.pdf illustrates identification, review routing and project tailoring. Its government-specific roles, action codes and approval procedures are not adopted as universal fence-buying rules.

4. Preserve the revision chain

Revision and comment history
Register IDRevisionChange / comment referenceSubmitted dateResponseSuperseded byFile location
________________________________________________________
________________________________________________________
________________________________________________________

Do not delete an earlier row when a revision arrives. Mark it superseded, link the replacement and keep the original response with the exact file it reviewed. The project change log should carry any approved change that affects the required document or product basis.

Turn a missing or unmatched file into a specific follow-up

Record the gap, requested reply and next owner
Observed gapRecord separately from review responseQuestion to send yourselfNext record
Required file not submittedRequirement source; requested document; status “requested”; named owner/due datePlease provide the identified file for this requirement revision, or confirm its availability and proposed response date.Actual transmittal, received file ID/revision and reviewer routing
Model, drawing or quoted item does not matchRequested and received identifiers; exact mismatch; reviewer not yet resolvedWhich quoted model/drawing does this file cover? Provide the matching revision or identify the proposed substitution explicitly.Dated clarification and any separate substitution review
New file refers to an old revisionBoth revisions and issue dates; received filename; current-basis questionConfirm which revision the offer and response cover, identify the replacement file and explain the change reference.Preserved revision chain and linked change record, where applicable
Reply exists but attachment or comment closure is missingExact formal reply, missing attachment/comment ID and open workflow actionPlease supply the referenced attachment or response to this comment against the reviewed file revision.Reply/evidence reference plus the project reviewer’s actual disposition

Fictional recordkeeping example: RFQ revision R3 asks for model EF-A; reply OFFER-7 names EF-A but attaches manual EF-B, revision 1. Register the received file as submitted, record the model mismatch, and assign a dated request for the EF-A manual to the named contact. Keep the review response blank until the assigned reviewer responds. These identifiers are invented examples, not supplier products or technical findings.

Reusable follow-up line: Register ID ___; required document/model/drawing ___; requirement revision ___; received ID/revision ___; gap ___; requested reply/file ___; action owner ___; agreed due date ___; response reference ___.

After the formal review route identifies the current documents, carry the same item and revision references into the receiving observation record and installation handoff. Those records remain separate from technical acceptance and permission to proceed.

5. Close comments and distribute the current file

Open comment reference____________________________
Response / evidence____________________________
Action owner / due____________________________
Current revision confirmedBy ______ Date ______
Final recipientsBuyer / supplier / site / other
Closeout status / date____________________________

Before closing, confirm that the reviewer response, current revision and distributed file all carry the same register ID. Route current shipping and packing records into the delivery receiving checklist.

Questions buyers ask

What is a document submittal register?

It is an index of required and received project documents showing stable IDs, current revisions, issuers, reviewers, dates, responses, next actions and superseded files.

Which fence documents should be included?

Only documents required by the project specification, quotation, purchase order or agreed schedule. Depending on the job, that may include drawings, product data, samples, test reports, certificates, instructions, packing records or closeout information.

Does “received” mean approved?

No. “Received” records delivery to the process. Review disposition, technical acceptance and permission to proceed are separate decisions made by the authority named in the project documents.

How should revised files be named?

Use the project naming rule and include a stable document ID plus a revision or issue identifier that distinguishes each version. Avoid relying on filenames such as “new,” “latest” or “final.”

Can an old revision be deleted?

Do not use this page to decide retention. Mark the old row superseded, link the replacement and follow the project’s contract, quality and records-retention rules.

Evidence and limits

The U.S. Army Corps of Engineers RMS manual displays register fields for section, item, description, dates, review codes, primary reviewer and status, plus transmittal history. The DoD UFGS submittal procedure groups submittals such as drawings, product data, samples, reports, certificates, instructions and closeout records, while requiring project tailoring. NIST document-control guidance uses a master list to identify current revisions and separates active from obsolete or superseded documents. These are transferable control patterns, not universal fence-document requirements or approval codes.

USACE RMS Manual: Submittal Register Identifiers, dates, reviewer, status and history

Supports a register that makes item identity, action ownership and review status visible.

— https://rms.usace.army.mil/datafiles/rms_manuals/rms_manual_gm_vol3_v5.0.pdf
WBDG / DoD: UFGS 01 33 00 Submittal types and project-specific procedure

Shows common document categories and why the governing specification must define the actual submission and review rules.

— https://www.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2033%2000.pdf
NIST: Document Control and Master Lists Current revision and superseded records

Supports recording the issuing source, revision status and separation of active from obsolete documents.

— https://www.nist.gov/system/files/documents/pml/wmd/labmetrology/NationalAnnualAssessmentMemo20160328.pdf

Send the document ID and revision with every question.

Include the requirement source, issuer, current reviewer, formal response and the next action still open.

Send a document query