Technical review
Confirm terminology, units, operating conditions, stated assumptions, application limits and whether the conclusion follows from the cited evidence.
Operational review control
Technical content review and source-control checklist
A repeatable pre-publication gate for classifying claims, matching them to the correct source, protecting manufacturer attribution and keeping quotation-stage facts out of evergreen content.
Before the draft
Classify the decision and the claim
Start with the buyer decision the page must support. Then classify every material statement as a regulatory or standards statement, stable technical concept, manufacturer-specific specification, GSE interpretation, public relationship research or current commercial fact.
The classification controls the evidence. A manufacturer data sheet can support a manufacturer specification, but it cannot prove regulatory compliance, GSE authorization, current inventory or guaranteed suitability for a site-specific application.
Six-field claim register
| Field | Review question | Required output |
|---|---|---|
| Claim owner | Who is responsible for the statement? | Regulator, standards body, manufacturer, GSE analysis or current quotation |
| Source | What evidence supports the exact wording? | Canonical URL, document title, revision and access date |
| Boundary | What does the source not prove? | Visible limitation beside the decision claim |
| Freshness | Can the fact change? | Source-review date and review trigger |
| Commercial status | Does the statement imply price, inventory, channel or warranty? | Move changing facts to the written quotation |
| Role attribution | Is the manufacturer, distributor and responsible approving party clear? | Named roles without unsupported ownership or independence claims |
Commercial review
Remove unsupported authorization, inventory, price, lead-time, shipping, warranty, service and seller-of-record implications. Route them to a current quotation.
Publication review
Verify one clear H1, descriptive metadata, useful internal links, accessible tables, correction path, review date and accurate structured data.
Release evidence
Publish the audit trail with the asset
Record the reviewer, review date, source URLs, version, material assumptions and next review trigger. For datasets, publish the schema, field definitions, version and downloadable formats. For interactive tools, state which values are user-entered and which outputs are estimates.
A correction is not a reputational failure. Concealing a known error is. Material changes should update the visible page, machine-readable companion files and linked decision paths.
Current written scope
Turn this research into a controlled technical request.
Send the application, model, specification or drawing. GSE will preserve the technical lane, identify missing scope and verify current commercial details without treating website copy as an offer.
- Unique request reference
- Completeness score
- Technical-lane routing
- No fabricated channel or inventory claims