FencingWise

Military-Site Fencing: Prepare a Traceable Supply Submission

A specialist security tender needs a product submission that can be traced to the released specification. For a fence factory or supply partner, that means identified drawings, materials, finish routes and evidence for the exact offered assembly. We recommend giving each departure its own decision record rather than using military-grade wording as a substitute for documented acceptance.

Work from the released procurement package

Obtain the specification reference, revision, authorised questions process and required submission format. Confirm which information the supplier is permitted to receive and retain. Do not request operational details simply because they might make a quotation more descriptive.

Divide the submission into product data, supporting evidence, commercial scope and departures. This makes it easier for the project reviewer to identify what is offered without searching through a mixed brochure bundle.

Green close-spaced mesh security fence along a site boundary
A fence submission should identify its actual panel, post and finish configuration.

Provide traceability for the supplied items

Record Purpose in the submission
Product and assembly drawing Identifies the proposed construction
Material and finish schedule States the basis of manufacture and inspection
Relevant test or certificate Supports the specific required characteristic
Lot and packing references Connect delivered items to the accepted order
Installation and maintenance information Defines handling and continued use requirements

Only claim a test result within its scope. Where a listed security product is required, verify the product and permitted configuration through the relevant issuing body, such as LPCB's directory. A supplier's participation in another project is not transferable technical approval.

Wide metal mesh vehicle gate within a perimeter fence
Gate leaves, posts and adjacent fence should carry consistent references across drawings and schedules.

Reconcile identifiers before issuing the offer

For an illustrative order, assume drawing revision C contains 80 panels, 82 support assemblies and two gate assemblies. The commercial schedule and packing plan should use those same three item groups and references. If the gate posts are already included in the gate assemblies, adding four gate posts to the support total would duplicate them.

The example is an accounting check, not a proposed site layout. Review quantities from the actual approved drawings and keep sensitive locations out of general-purpose packing labels where the project requires controlled identification.

Declare substitutions in a short deviation table

Show a proposed change beside the original requirement, including the affected component, evidence and manufacturing or installation consequence. A different fixing, finish route or gate frame should remain visible even if the overall boundary dimensions stay the same. Ask the authorised reviewer to accept the specific revision before it becomes the basis of material procurement or fabrication.

The acceptance authority decides whether an alternative is permissible. Record that decision and its revision. Silence after sending an attachment is not a dependable record of acceptance.

Agree document handling and close-out

Agree the supplier’s authorised document channel and permitted identification scheme before exchanging production information. The factory needs the relevant dimensions, component requirements and released revisions, while controlled operational details stay within the project’s handling rules. Packing labels, inspection references and close-out records should use the approved identifiers consistently without turning restricted project information into public marketing content.

At delivery, reconcile markings and quantities with the approved schedule. At completion, the project team should have the accepted drawings, required inspection records, authorised deviations and maintenance references. This provides a usable technical trail without publishing sensitive operational detail.

The technical deviation schedule gives a practical format, and NPSA and legacy CPNI references explains why a guidance reference is different from a product approval.