Samples
Sample SOPs and Briefs for Fuel Marketers
Five sanitized documents that show the form of what True North Data Strategies hands back to an operator: four standard operating procedures and one weekly market brief. No client information, no client data, no client system. Every PDF is a direct download, no email required.
Five sanitized samples
Each page explains what the document does, what is in it, and why it is built the way it is, in the document's own words. The PDF is one click from either the card or the page.
- Standard operating procedureTNDS-SAMPLE-SOP-2016 pages
Fuel Delivery Dispatch SOP
A sanitized order-to-delivery dispatch procedure for fuel marketers: twelve steps, four stop points, roles instead of names, and an evidence column for every step.
- Standard operating procedureTNDS-SAMPLE-SOP-5015 pages
Fuel Pricing SOP: Daily Rack to Posted Price
A sanitized daily pricing procedure for fuel marketers: one entry point for every rack price, a no-move check, a floor price by product and channel, and a change log for every posted price.
- Standard operating procedureTNDS-SAMPLE-SOP-6017 pages
Cargo Tank Testing SOP: Test and Inspection Records
A sanitized records procedure for cargo tank tests and inspections: one due-date clock per test type, an out-of-service flag that dispatch can see, and citations to 49 CFR Part 180 verified against the eCFR.
- Standard operating procedureTNDS-SAMPLE-SOP-6028 pages
Driver Qualification File SOP
A sanitized procedure for building and maintaining driver qualification files: complete before the first dispatch, an annual cycle with an owner and a date, Part 382 records kept separately, and citations to 49 CFR Part 391 verified against the eCFR.
- Market briefTNDS-SAMPLE-MKT-0015 pages
Fuel Market Conditions Brief
A sanitized weekly brief for the person who buys product and sets posted prices: what moved, the rack board, basis and spreads, replacement cost against posted price, and what the last issue got wrong. Every figure in it is invented for demonstration.
What the four procedures have in common
Roles, not names
The procedure names roles and the roster names people. When someone leaves, the roster changes and the procedure does not.
Stop points, not reminders
A stop point halts the procedure. It is not a reminder and it is not a preference. Work does not continue past it until the condition clears.
An evidence column
Every step names how an outsider can tell it happened. A step with no evidence is a hope.
Brackets where the engagement fills in the facts
Owners, thresholds, system names, and retention periods appear in brackets because those are set during the engagement, walked with the crew who do the work, and sealed only after they confirm the steps match reality.
The market conditions brief is different in kind. It is a weekly deliverable, not a procedure, and every figure in the sample is invented for demonstration.
What a stop point looks like
Order received
Required checks
Did the checks pass?
If the checks fail
STOP and hold
Assign an exception owner
Record the fix and recheck
If the checks pass
Release to dispatch
Capture delivery evidence
Reconcile and close
Example only. Every operation sets its own checks.
Want one built for your operation?
These samples show the form. In an engagement, the bracketed owners, thresholds, systems, and retention periods are filled from the operation as it actually runs. It starts with an Operations Assessment.