Why 'Live' Spreadsheets Lie: Lock In Your Numbers When a Mission Closes

The bug that costs you a tax season

You quoted a job in March when gas was $2.89/gal. You flew it, got paid, moved on. In October you open your books and your March job suddenly shows a different fuel cost, a different margin, maybe a different profit per hour — because the cell that calculates fuel cost is linked to "current gas price" and current gas price is now $3.74.

Nothing about that March mission changed. Your books just lied to you.

This is the single most common bookkeeping bug I see in solo drone businesses. The cause is always the same: formulas that reach out to live values instead of capturing the value that was true the day the work happened.

What needs to be frozen the moment a mission completes

Treat the "Complete" action like closing the books on that job. These numbers should be written down, not recomputed:

• Fuel price per gallon — the price on the day you drove, not today's
• Mileage rate — the IRS rate in effect for that tax year (it changes annually)
• Hourly rates — your fly rate, travel rate, and processor fee % as they existed when you priced the job
• Platform cut — FlyGuys / Zeitview fees as they were that day; platforms change terms
• Actual hours on site and actual miles — not the estimates from the quote
• Gross revenue, processor fees, net deposited — the dollars that actually hit your account
• Vehicle MPG — your then-current vehicle (if you changed vehicles mid-year)

If any of those are still pointers to "current settings" six months later, your historical reports are fiction.

Why "live numbers" feel right but aren't

Spreadsheets reward DRY thinking — one cell for gas price, every job references it. That's elegant for the next quote. It's catastrophic for the last one.

The accounting principle here is older than spreadsheets: a transaction is recorded at the value in effect when it occurred. Banks don't restate last year's interest because rates moved. Stripe doesn't restate last year's fees because their pricing changed. Your drone business shouldn't either.

What this breaks if you don't fix it

• Quarterly estimates — you over- or under-pay because last quarter's "profit" keeps drifting
• Per-job profitability analysis — you can't tell which platforms were actually worth it
• Repeat-client pricing — you raise rates based on a margin that was never real
• Tax filings — mileage deduction uses the wrong year's rate; expenses don't tie to receipts
• Audit defense — you can't reconstruct what the numbers were on the date of the job

The simple fix

Two rules:

1. Write, don't reference. When a mission completes, store the actual dollar values on the job record. Not a formula. Not a link to a settings sheet. The number.
2. Settings changes are forward-only. When you bump your hourly rate or your gas price updates, that affects new pricings and new completions — never historical ones.

In a spreadsheet, that means a "Completed Jobs" tab where every column is a value, not a formula. In a tool that's built for this (Rotor Rate does it automatically), completion snapshots everything: price breakdown, fuel cost at that day's gas price, mileage rate for that tax year, actual time and miles you logged.

A 3-minute audit you can do today

Open your tracker and pick a job from 60+ days ago. For each of these, ask: "is this a number, or is it a formula reaching somewhere else?"

• Fuel cost on that job
• Drive time × travel rate
• Platform fee
• Net deposit

If any one of them recalculates when you change a global setting, you've got the bug. Fix that job manually now, then fix the template so future completions write values instead of formulas.

Your future self filing taxes will thank you.

Run a mission with frozen numbers from day one