Verification Notes
EC-IFAS content mixes two types of knowledge: (1) stable operational practices (how to structure a routine) and (2) context-dependent details (policy, pay, carrier procedures). This page explains how we handle each.
Official documentation, carrier SOPs (when shareable), and published standards.
Repeatable routines that work across many environments (pre-trip, timestamps, update formats).
Anecdotes and notes—useful, but not universal. We label them as Field Notes.
How we write “operational truth”
When we present a checklist or script, we treat it as an operational tool. It should be: clear, time-stamped, and compatible with real dispatch workflows.
This structure is verifiable because it doesn’t rely on speculation. It relies on observable facts.
Handling uncertainty
- If a detail depends on a carrier contract, we say so.
- If a policy varies by jurisdiction, we frame it as “verify locally.”
- If we cannot confirm a claim, we do not present it as fact.
Requesting a correction
Send the URL and the claim you believe is incorrect. Provide a supporting reference if possible.
Email: [email protected]