Editorial Policy

LaneMath publishes practical, field-oriented explanations for trucking carriers. Pages favor clear definitions, written-term checks, cautious example math, and conservative wording where payment, broker risk, accessorial approval, or compliance context is involved.

Editorial scope

LaneMath is written as educational dispatch support. A page may explain how to compare two offers, what to ask a broker, or which records are useful for detention or billing. It should not tell a carrier what rate to accept, which broker to use, how to interpret a contract, or how to satisfy a legal or regulatory obligation.

Review process

Before publication, content is checked for unsupported market claims, overconfident payment language, missing disclaimers, thin explanations, broken links, and repeated template wording. Pages that involve broker identity, payment, accessorials, or compliance context are written with extra caution and are tied to either official public references or a clearly labeled editorial methodology source.

Review also checks whether the page can be used by a carrier in a real workflow: before a broker call, before signing a confirmation, during a delay, or while preparing a billing packet. Pages that cannot answer a practical question should be revised rather than expanded with filler.

The review is deliberately conservative. A page may say which documents a carrier should compare, which questions are useful before booking, and which records commonly support a billing file. It should not say what a broker must pay, what a court would decide, whether a carrier is compliant, or whether a specific load is profitable for every business.

Experience review

Pages that describe carrier workflow are checked against field experience from dry van dispatch, small-carrier paperwork, and regional lane planning. The reviewer looks for practical gaps: a missing revised confirmation, a detention clock that is not defined, a lumper receipt that is not tied to the load file, or a load comparison that ignores deadhead and reload position.

That experience review is not treated as a substitute for outside authority. When a page needs public regulatory, registration, diesel-price, or industry-cost context, LaneMath uses official or industry sources listed on the Sources page. When a page is a practical workflow rather than a public-data claim, the source note says so plainly.

Lane guide method

Lane pages use rounded city-center mileage ranges as an orientation point, then ask the reader to route the actual truck position, shipper, receiver, and next usable freight area. Interstate names and named toll facilities are reviewed separately because a plausible mileage number can still be attached to the wrong road. Where a page discusses a public toll system, the references identify the responsible toll authority.

Lane pages do not use private load board rates or claim that one direction is currently stronger. Facility, weather, parking, and reload notes are framed as questions to verify for the load at hand. They are not predictions about what will be available when the truck arrives.

Software-assisted drafting and quality checks

LaneMath uses structured data and automated checks to manage page relationships, find repeated wording, test links, measure rendered page depth, and flag missing sources. Software-assisted drafting may also be used to organize an outline or identify coverage gaps. Automation is not treated as a factual source and a page is not approved merely because it reaches a word count or passes a template check.

Route names, quantitative claims, public-record instructions, and payment-sensitive wording require editorial review against the source or load-document context stated on the page. When a number cannot be supported as a current public fact, it is presented as a clearly labeled hypothetical example or removed.

Editorial quality rules

• No freight quotes, pricing feeds, broker recommendations, or promises about what a lane should pay.
• No copied paid load board data or private freight marketplace data.
• Examples must be labeled as hypothetical or educational.
• Official sources are used only for public background, not as freight rate sources.
• Payment, broker-risk, accessorial, and compliance topics must avoid guarantees and must point readers back to written terms, official records, or professional review when appropriate.

Updates and corrections

Each page carries an updated date. When public source pages, terminology, or editorial methodology changes, affected pages should be reviewed before the updated date is changed. If a page makes a practical statement that has become too broad, too current-sounding, or too close to advice, the wording should be narrowed rather than padded with more sources.

Correction requests can be sent to [email protected]. A useful correction includes the page URL, the sentence in question, and the public source or load-document context that should be reviewed.

Substantive updates are expected to change the page, not just the date. Examples include adding a source note, narrowing a claim, clarifying a calculation limit, correcting a term, improving a checklist step, or adding a real carrier-document context that helps the reader use the page responsibly.

Site-wide editorial work is summarized in the Content Updates log. Formatting-only changes, dependency updates, and visual cleanup do not justify changing a content date by themselves.