“Suitable for bridges” tells an engineer little about whether a bearing can accommodate the movements identified for a particular structure. A useful description identifies the bearing type, declared movement and load characteristics, the basis for testing, and the conditions under which those figures apply. The writer is not assessing suitability for the bridge; the task is to make the information needed for that assessment easy to find and interpret.
Start with the decision the reader must make
Product pages for transport infrastructure serve different readers. A designer may need a declared property for preliminary screening; a construction team may need handling and installation constraints. An asset manager may be looking for inspection access, replacement information, or a way to identify a product already in service. “High performance” answers none of those questions.
Before drafting, list the decisions the page can legitimately support. Can readers identify the variant, determine which evidence to request, and spot a condition that rules out immediate use? Keep those questions separate from decisions requiring project-specific calculations, approvals, or examination of site conditions.
Build a question-to-evidence map
A working table helps keep prominent claims from displacing essential details. It also exposes questions the available documentation cannot answer.
| Reader question | Useful content | Evidence to check |
|---|---|---|
| Which version is described? | Product designation, configuration, and available sizes | Current drawing and variant schedule |
| What performance is declared? | Property, value or range, unit, and test conditions | Approved technical data and test report |
| Where are its limits? | Environmental and application restrictions | Manufacturer instructions and assessment documents |
| What must happen on site? | Substrate, storage, preparation, or inspection requirements | Current installation and maintenance instructions |
The map is a drafting tool, not a promise that every answer will fit on one page. If performance depends on the configuration selected, say so beside the property and point readers to the controlled variant data. Do not combine values from different configurations into a fictitious “typical” product.
Lead with identification and intended function
Open by identifying the item and its function. For example: “A prefabricated drainage composite intended to convey water along a specified interface in a road or rail earthwork.” That says more than “an innovative drainage solution,” though the description still needs to identify the interface and explain what governs selection.
State the product family and configuration before giving performance figures. Readers should not have to guess whether a value belongs to a sheet, a complete assembly, or a system installed with particular accessories. For products with multiple grades, use the same designation in the page title, tables, drawings, and downloadable documents. A material name alone may not be enough when thickness, reinforcement, geometry, or connector type changes its behavior.
Distinguish intended application from demonstrated suitability. “Intended for drainage behind retaining structures” describes a proposed use. It does not establish capacity under a particular confining pressure, hydraulic gradient, soil condition, or service environment. Give readers the relevant evidence without presenting intended use as an approval.
Answer performance questions with conditions attached
A number without its test conditions can be more misleading than no number at all. A geosynthetic’s reported flow capacity, for example, may depend on normal stress, hydraulic gradient, contact surfaces, and the duration of compression. Include the conditions needed to interpret the result, its units, and the test method recorded in the source documentation. Do not extend the result silently to other conditions.
The same principle applies to other infrastructure products. A coating’s declared properties may depend on preparation and curing. A movement joint’s stated range may apply only to a particular assembly and installation gap. A monitoring instrument’s accuracy may be specified for a defined measurement range and operating temperature. Include the conditions that matter to the claimed property, rather than an unexplained catalogue of figures.
Keep three kinds of statement distinct:
- Declared property: a value or classification attributed to the identified product and supported by specified documentation.
- Test result: an observation under defined laboratory or field conditions; it may not represent every installation.
- Project requirement: a criterion set by the project team, which the product page should neither invent nor imply it has verified.
If a property has not been established, “designed for demanding conditions” is no substitute. Say that the relevant performance information must be obtained or assessed for the proposed application. An explicit gap is safer than an unqualified assurance.
Put compatibility and exclusions near the claim
Place limitations where readers might otherwise make an incorrect assumption. If a sealing product is described for concrete joints, clarify whether the documentation addresses wet substrates, expected movement, and the joint geometry in question. If a sensor requires a particular power supply, data interface, or calibration procedure, put those requirements alongside its operating features.
A short compatibility section can address adjacent materials, the operating environment, required accessories, and installation dependencies. Separate established compatibility from matters still needing verification. “Chemically resistant,” for example, is incomplete unless the available evidence identifies the substances or exposure conditions covered. An unknown site contaminant cannot be assumed compatible.
Installation constraints matter as much as headline specifications. Delivery form, storage restrictions, preparation, curing, inspection access, and the replacement method may determine whether an item can be used within a planned work window. Present these as requirements drawn from controlled instructions, not informal tips that might contradict them.
Make the description easy to scan without hiding qualifications
Readers often arrive with one question. Follow a short functional opening with labeled sections for variants, declared properties, application limits, installation, maintenance, and documentation, as relevant. Tables help compare variants if units are unambiguous and conditions remain visible. Use prose for dependencies that could be misunderstood in a table cell.
Do not put a broad promise at the top of the page and bury its exception in a download. A qualification can sit beside the figure: “Value applies to the configuration and test conditions shown in the technical data.” If those conditions are too extensive to reproduce, identify the exact document and revision. Readers should still see that the qualification exists.
Use headings as information labels, not slogans. “Operating temperature and measurement range” helps readers find evidence; “Built for every challenge” does not. Define specialist abbreviations on first use if procurement or maintenance staff may read the page alongside designers. Keep units consistent across the text, tables, and downloadable data.
Review claims against controlled documents
A product description is an edited account of technical records. Before publication, a technically competent reviewer should check designations, revisions, values, units, conditions, and limitations against approved source documents. An illustrative photograph or diagram should not show a different variant without saying so. If the page cites a certificate or test report, verify that it covers the exact product and property claimed.
Changes need to be traceable. A revised formulation, component geometry, test method, or installation instruction can make an otherwise polished page inaccurate. Record the document revisions used, assign responsibility for review, and revisit the page when controlled product information changes. If a property varies by batch or custom configuration, explain how readers can identify the applicable record instead of publishing one number as universal.
Before publishing, try a question a project team might ask: “Does this listed movement capacity apply to the 300 mm joint assembly shown in the drawing?” If answering requires a guess about which variant produced the figure, put the variant designation and applicable test conditions beside the value.
