Reusable bundles. A requirement template is a set of document-type rules (and optional broker file links) that can auto-apply from carrier profile flags. Sent packet snapshots are never rewritten.

Requirement templates

Define once, reuse for hazmat, reefer, flatbed, first-time carriers, or manual assignment. Each item is still a typed requirement — not a raw file.

Packet preview (simulated carrier profile)

Toggle equipment and onboarding flags to see which templates would match for a new packet. Production would read the carrier profile.

Your templates

Active templates participate in automatic matching. Standalone requirements still apply when no template matches (or merge — see preview).

Manual-only templates are not auto-matched; brokers or carriers pick them explicitly in a full flow.