What this guide decides.
This page decidesWhich observations and records support routine maintenance and when a condition should be referred to the responsible specialist.
This page does not decideA universal interval, warranty decision, structural acceptance, security release, powered-gate safety approval or repair instruction for an unknown system.
Create the baseline at receiving and handover.
Record bundle and component identities, visible transport damage, coating condition, shortages, drawings, finish documents and accepted deviations. After installation, keep dated line-by-line photographs and the approved component/gate schedule so later changes can be compared with a known basis.
Inspect by location and function.
Observe leaning or displaced posts, loose or missing pales, rail movement, damaged connectors and fasteners, sharp or exposed edges, coating breakdown, vegetation contact, erosion, changed ground gaps and unauthorized attachments. Use run and gate IDs rather than a single perimeter-wide note.
Give gates their own condition record.
Check movement, alignment, hinges or rollers, stops, latches, locks, hold-open devices, clearances and adjoining fence transitions. Powered equipment, controls and safety devices require the competent maintenance and risk-management process for that exact gate system.
Separate cleaning, touch-up and structural repair.
Routine cleaning or an approved coating repair is not the same as straightening a pale, changing a post, welding a gate or altering a foundation. Before structural work, identify the original material, finish, connection, design responsibility and any security or warranty consequence.
Use stop-and-escalate triggers.
Restrict access and refer the condition when there is instability, a hazardous projecting edge, a gate that cannot be safely controlled, damaged foundations, progressive movement, an unexplained breach, widespread coating failure or uncertainty about the approved configuration.
Keep the observation and action separate.
Use this matrix to expose the next decision. It is not a performance rating, installation instruction or project approval.
Project-input schedule.
Carry these fields into the enquiry. Return unknowns as open items with a named owner instead of filling them with typical values.
What a usable supplier response should return.
A useful response identifies the exact proposed component and drawing basis, uses the buyer's run and opening IDs, and separates confirmed values from assumptions. It should list inclusions, options, exclusions, deviations and the information still needed from the survey, project designer, installer, gate specialist or local authority.
Where a standard, certificate, test or inspection record is requested, the response should identify its edition, scope, issuing body and relationship to the exact offered configuration. Generic marketing language must not close an engineering, security, safety or compliance decision.
Questions to close before quotation or release.
- What changed from the approved baseline?
- Is the condition local or repeated?
- Is there instability, sharp exposure or unsafe gate movement?
- Does the proposed repair change material, geometry or finish?
- Who owns structural, gate-safety or security review?
- What evidence closes the action?
Technical reference boundary.
These sources define terms, responsibilities and decision scope. They do not certify a XIEHENG product or approve a project.
Keep adjacent intent with its owner.
For a rated 358 system, preserve the exact approved configuration and use the dedicated lifecycle route.
Review 358 inspection and repair →