How to onboard a new gas station manager in 30 days.

Why a structured 30-day onboarding works

New manager onboarding at most independent stations is informal , the new hire shadows a current employee for a week, then runs the floor alone. It works at very small operations where the manager's scope is narrow. It breaks at any station with EOD, lottery, fuel margin, vendor invoices, and multi-shift coordination because the scope is too broad to learn by osmosis.

The structured 30-day plan stages learning by money risk. The manager learns the highest-risk daily task (cash and EOD) first, then layers on lottery and fuel (higher dollar exposure but slower attribution decay), then inventory and vendors, then exception handling. Each week ends with a checkpoint that verifies competence before adding scope.

Week 1: cash and the daily close

The highest-risk daily activity. The manager has to run a clean EOD before anything else gets added to their scope.

Day 1: shadow the owner's close

Owner runs EOD with the manager watching every step. Explain starting drawer, cash sales, drops, refunds, expected cash, counted cash, variance, tolerance band, reason code, owner-alert flow. The manager takes notes; doesn't touch the form.

Days 2–4: manager runs EOD with owner present

Manager opens the form. Owner watches but doesn't touch. Variance discussion happens at the form, not in the back office afterward. Mistakes are corrected in real time.

Days 5–7: manager closes solo; owner reviews same evening

Manager runs EOD without supervision. Owner pulls the audit row that night and runs the variance / reason code review before the next shift starts. Any pattern of error gets a same-day conversation.

Week 1 checkpoint

Day 7: did the manager close all three of their solo shifts within tolerance with no missing reason codes? Yes → move to Week 2. No → repeat the relevant Week 1 days. Don't layer Week 2 on top of a shaky Week 1.

Week 2: lottery and fuel

Slower-decay attribution than cash but higher dollar exposure when something goes wrong.

Days 8–10: lottery

Pack activation, sales scanning, settlement, daily reconciliation against the state-commission report. The manager runs the lottery closeout for 3 consecutive days with the owner reviewing the next morning. Missing-serial flags get walked through together.

Days 11–14: fuel margin and BOL

Realized vs. target margin per grade, dispenser totalizer read, ATG inventory check (or tank stick if no ATG), BOL reconciliation on a delivery day. By day 14 the manager has seen a wholesale-cost update and a delivery reconciliation.

Week 2 checkpoint

Day 14: did the manager settle the lottery pack with zero missing serials? Did the BOL reconciliation come in within tolerance? If both yes → Week 3. If either no → diagnose which (process gap or attention gap); repeat the relevant days.

Week 3: inventory and vendor invoices

Days 15–17: vendor invoices

Invoice OCR (or manual entry if no OCR), receiving discipline, short-ship documentation, cost-change flagging, manager approval before QuickBooks post. The manager processes 8–12 invoices in Week 3 with the owner reviewing the same evening.

Days 18–21: inventory and cycle counts

Mobile cycle counts on high-velocity SKUs (tobacco priority), SKU-level variance review, vendor cost-change cross-reference. Each day's 30–50 SKU counts get completed without backlog.

Week 3 checkpoint

Day 21: vendor invoice queue cleared each day this week? Cycle counts current with no backlog? Both yes → Week 4.

Week 4: KPIs and exception handling

Days 22–25: morning brief routine

The manager runs the morning brief solo. EOD variance, lottery exceptions, fuel margin, cash deposit reconciliation, cycle-count alerts, vendor invoice queue, open notes. Owner gets a same-day text on any flag the manager triaged.

Days 26–30: exception triage independently

Cross-signal flags surface from Loss Radar (if wired) or from the manual review. The manager decides the action: training, process fix, investigation, dismiss. Owner reviews the triage decisions, not the events themselves.

Week 4 / day-30 checkpoint

Day 30: did the manager run the full week solo without any owner intervention required? Did exception triage decisions match what the owner would have made (within 80%)? Yes → manager is operational; transition to standard weekly review. No → diagnose which workflow needs additional support; extend onboarding by 2 weeks targeted on that workflow.

Success criteria, what a clean hire looks like at day 30

• EOD variance under warning band on 90%+ of shifts.
• Lottery packs settled with zero missing serials.
• Vendor invoices queue cleared each day; cost-change flags actioned, not absorbed.
• Cycle counts current; high-velocity SKUs touched at least every 14 days.
• Exception triage decisions match owner's judgment on 80%+ of flagged events.
• Morning brief routine runs without owner involvement.
• Shift handoff procedure followed on every transition.
• No emergency calls to the owner outside business hours unless materially exceptional.

Common manager-onboarding mistakes

• Layering scope before the prior week is clean.If Week 1 EOD still has issues, don't move to lottery. Repeat the week; don't compound errors.
• Skipping the day-14 honest conversation.Most failed managers fail by day 14; extending to day 30 rarely changes the outcome.
• Documenting only successes. The patterns of failure in weeks 1–2 predict where ongoing support is needed. Capture both.
• Onboarding by tribal knowledge alone.Without a written plan, what the manager learns depends on who's on shift that day. Predictability breaks.
• No structured checkpoints. Without a measurable Week 1 / Week 2 / Week 3 / Week 4 gate, scope expands by clock time, not by competence.