Authority before repetition
A frequently repeated statement is not automatically reliable. Permit and infrastructure claims should trace to the responsible agency or asset owner whenever available.
Evidence and claim controls
Heavy Haul Now matches each material statement to evidence appropriate for that claim. Public agencies support permit and infrastructure rules; exact manufacturer records support machine specifications; facility owners support access procedures; and company, customer or case-study claims require approved first-party proof. Unsupported metrics, licensing statements, insurance promises, customer relationships, prices and project outcomes are withheld. Sources are qualified by scope, reviewed for change and corrected across connected pages when necessary.
Policy purpose
This policy governs public facts, regulatory statements, equipment specifications, company claims, customer proof, case studies, prices and planning scenarios. A source is accepted only for the scope it can reasonably support.
A frequently repeated statement is not automatically reliable. Permit and infrastructure claims should trace to the responsible agency or asset owner whenever available.
An exact machine configuration, jurisdiction, corridor or facility source is preferred over a broad industry summary when the page makes a specific claim.
Information that changes by model, route, authority, date or shipment is qualified. Planning language must not imply universal capacity, approval, availability, timing or price.
Customer, project, licensing, insurance, performance and experience claims are not published merely because they would strengthen conversion.
Source hierarchy
| Information | Preferred source | Acceptable use | Not sufficient alone |
|---|---|---|---|
| Permit rules and travel restrictions | Controlling DOT, permit office, bridge, toll or local authority | Current public rule and application guidance | Another broker’s summary or an undated article |
| Machine dimensions and weights | Official manufacturer record for the exact model/configuration | Screening and model-specific comparison | Marketplace listing or unrelated model-family average |
| Trailer characteristics | Manufacturer documentation and configuration-specific technical material | Geometry, loading and application analysis | Generic capacity claim without axle or route context |
| Ports, terminals and facilities | Official owner, operator or public authority | Appointments, access scope and facility role | Map listing or directory description |
| Roads, bridges and construction | Transportation agency or infrastructure owner | Named asset, ownership and published restriction context | Consumer navigation result |
| Company licensing or authority | Official regulator record and legal company identity | Verified status with date and scope | Logo, badge or unsupported marketing statement |
| Insurance or carrier vetting | Current documentation and written procedure | Qualified explanation of review method | Unqualified coverage promise |
| Customer review or case study | Approved first-party record and publication permission | Attributed or explicitly anonymized evidence | Invented quotation, stock image or unsupported outcome |
Commercial proof
The website does not assign substitute values when company proof is unavailable. Unsupported performance percentages, shipment counts, customer names, operating history, coverage amounts, licensing badges or response-time promises must be removed or withheld.
Any statement describing Heavy Haul Now as a broker, carrier, coordinator or planning platform must match the legal entity, operating authority and actual contractual role.
Coverage statements must identify whose policy is being described and remain subject to current documentation, shipment terms and applicable exclusions. Carrier-vetting procedures should describe the actual review process.
On-time rates, loads moved, response times and similar statistics require a defined period, calculation method and auditable record. Zero placeholders and guessed corrections are prohibited.
Founding dates, years in business and accumulated project experience require legal or business records that support the specific wording.
Project evidence
Confirm the cargo, relevant model or configuration, origin and destination scope, project date and the role Heavy Haul Now actually performed.
Verify the trailer or transport configuration, loading method, permit scope, route work, schedule and documented outcome.
Confirm permission for customer attribution, photographs, documents and identifying facility details. Anonymization must be disclosed when used.
Stock photographs, illustrative routes, estimated prices and hypothetical outcomes cannot be presented as completed customer work.
Citation and qualification
A source label should identify the responsible organization or document. Regulatory and infrastructure statements include a review date when practical. Links should lead to the authoritative destination rather than a search-results page.
Place the source near the table, fact group or section it supports. A general sources list does not prove every sentence on the page.
State whether a figure is cargo-only, machine operating weight, loaded combination, routine permit threshold, planning estimate or another limited measure.
Permit rules, processing times, closures, construction, weather and facility procedures must be reconfirmed close to the planned shipment date.
When credible sources conflict, do not silently select the more convenient value. Identify the conflict, narrow the configuration or leave the claim unpublished.
Automation and AI
Automation may organize records, identify missing fields, generate draft structures and test consistency. It cannot establish that a facility relationship, customer project, specification, permit rule or company claim is true.
Automated content must not invent local facts, reviews, customers, project outcomes, photographs, prices, authorities or performance metrics.
A city-by-equipment or city-by-industry combination is rejected unless the relationship has defensible operational or commercial relevance.
Research notes, editorial prompts, source requests, template tokens and publication instructions are blocked from indexable customer-facing content.
The publication gate requires review of canonical ownership, sources, claims, visible language, structured data, links and conversion functionality.
Corrections policy
A correction review identifies the affected claim, its source, every page or schema record that repeats it, and whether a redirect, sitemap update or database change is also required. Corrected content receives an updated review date when the change is material.
Provide the affected URL, exact statement, reason for concern and the most authoritative supporting source available.
The team compares sources, configuration, jurisdiction, publication date and page relationships before changing the record.
Shared data, visible text, schema, tables, internal links and related pages are checked so the same error does not survive elsewhere.
Submitting a correction does not guarantee the proposed wording will be adopted; the published result follows the evidence and claim scope.
Policy answers
Yes, when they are suitable for context and do not replace an available controlling or primary source. The source must be evaluated for authority, date, scope and direct support for the claim.
A number is withheld when its definition, period, calculation or evidence cannot be substantiated. The policy prohibits replacing a bad value with a more attractive guessed value.
They should not be presented as customer proof without documentation of the relationship and publication rights. Industry examples must be labeled as examples rather than implied clients.
No. They provide planning information and links to relevant authorities. The issued permit and controlling agency determine the authorized route, configuration, timing and conditions for a specific movement.
An anonymized case study must still have an approved underlying project record. The page should explain that identifying details were withheld and must not invent substitute customer or facility names.
Use the contact page with the URL, statement and supporting evidence. The review covers the visible page, structured data and connected records that may repeat the same claim.
Send the URL, disputed statement and supporting source. Material corrections are reviewed against the evidence and reflected in the affected page.