Procurement guide · specification and submittal

358 Fence Specification & Submittal Guide

Write a performance and interface brief first; approve the exact product schedule, evidence and deviations before release for supply.

What this guide decides.

This page decidesWhether the enquiry and submittal contain a controlled, comparable and approvable supply basis.

This page does not decideAutomatic technical approval, engineering design responsibility or acceptance of unrecorded substitutions.

Representative detailed view of a 358 panel, post, fixings and topping bracket
Representative connection view. Product schedules and approved drawings must identify the exact supplied components.

Separate requirement from proposal.

The employer or designer should state the site objective, required evidence, geometry, interfaces and acceptance process. The supplier should identify the offered product, supported configuration, documents, exclusions and deviations.

Schedule every component.

Include panels, posts, connections, fasteners, gates, hinges, locks, toppings, transition and corner items, base or embedded items, finish, touch-up materials, spares and packing. Link each to a drawing and revision.

Create an evidence crosswalk.

For every security, coating, material or dimensional requirement, identify the submitted certificate, report, drawing or inspection record and the exact clause or configuration it supports. Mark partial matches and deviations openly.

Control changes through approval.

Use a deviation register with requirement, offered condition, reason, impact, evidence, disposition, reviewer and date. Supply release should reference the final approved document set and quantities.

Make tender comparison auditable.

Require every bidder to return the same schedule with a direct response, document reference, option, exclusion or deviation against each line. Separate product compliance from commercial qualifications and from project design items still owned by others. When bids use different terminology, normalize the exact components and responsibilities before comparing price. The final recommendation should show why the selected offer is technically reviewable and commercially complete rather than simply recording the lowest total.

Build the submittal around review decisions.

A large file package is not necessarily a controlled submittal. Each document should answer a requirement, interface or approval question.

Submittal packageProduct schedule
What it must identifyExact panel, post, connection, fastener, gate, lock, topping, finish, spare and controlled option.
Review outcomeAccepted, commented or rejected component basis with no unnamed substitutions.
Submittal packageLayout and details
What it must identifyRuns, levels, corners, openings, transitions, foundations/interfaces, quantities, revisions and drawing relationships.
Review outcomeCoordinated geometry with project-specific areas separated from typical details.
Submittal packageEvidence crosswalk
What it must identifyRequirement, source document, exact product/configuration, supported clause, limit and deviation.
Review outcomeTraceable evidence disposition without transferring claims between unlike systems.
Submittal packageResponsibility matrix
What it must identifySecurity, structural, civil, electrical, gate, coating, installation, inspection and commissioning ownership.
Review outcomeNo unassigned interface and no silent transfer of project design to a component supplier.
Submittal packageRelease and handover record
What it must identifyApproved revisions, comments closed, quantities, packing, hold points, inspections and as-built deliverables.
Review outcomeA supply release that can be audited against what was manufactured and delivered.

Move from enquiry to approved supply basis.

Keep commercial comparison, technical review and fabrication release as distinct control points.

  1. 01

    Issue a common enquiry schedule

    State the operational basis, fence-line information, openings, interfaces, evidence needs, supply boundary, delivery conditions and required response format.

  2. 02

    Receive an explicit supplier proposal

    Require an exact product schedule, drawings, documents, assumptions, options, exclusions and deviation register rather than accepting catalogue language as the offer.

  3. 03

    Review by responsibility

    Route security evidence, structural and civil interfaces, gates, electrical systems, coatings, operations and commercial scope to the named reviewers.

  4. 04

    Close comments and deviations

    Record each response and disposition against controlled revisions. An updated drawing should not make the earlier unresolved decision disappear.

  5. 05

    Release a frozen document set

    Reference approved drawings, schedules, evidence, quantities, finish, packing and open hold points in the manufacturing or supply release.

  6. 06

    Complete the handover record

    Collect inspections, delivery identification, as-built changes, maintenance information and outstanding actions against the same component and drawing references.

Project-input schedule.

Carry these fields into the enquiry, drawing review and approval record. Mark unknowns as open items instead of guessing.

BasisThreat/operational requirement, site, standards, classifications and responsibility matrix.
GeometryRuns, heights, levels, corners, gates, thresholds, slopes, walls and bottom gaps.
ProductsPanels, posts, fixings, gates, locks, toppings, finish, spares and controlled options.
DocumentsDrawings, schedules, calculations by owner, certificates, reports, inspections and packing.
ApprovalComments, deviations, revisions, named reviewers, release status and as-built handover.

Submittal completeness questions.

  • Can every supplied component be traced to a named schedule and drawing revision?
  • Does each evidence document map to the exact offered configuration and requirement?
  • Are assumptions, options, exclusions and deviations visible in one register?
  • Who reviews security, structural, civil, electrical, access and coating interfaces?
  • Which comments must close before fabrication, packing or shipment?
  • What documents and records are required for inspection and lifecycle handover?

When this specialist guide is not the right page.

Use the general welded-mesh specification guide when no security classification, controlled configuration or security-system evidence is required.

Open the general welded-mesh specification guide →

Approve the system, not the label.

Send the threat or operating requirement, fence-line drawing, gate schedule, site interfaces, requested evidence, supply boundary and destination. We will identify confirmed product options and open technical items.

Prepare a 358 enquiry