Scope creep rarely shows up as a formal amendment. It shows up as “while you’re up there,” a text on the drive out, or a new deliverable mentioned after you already priced the flight. Drone job change orders exist so you can adjust the job without pretending the original quote still covers everything—and without throwing that quote away and starting from zero.
This is a Pilot Ledger Sales post: teach-first, nationwide U.S. commercial ops. Soft CTA only to Pilot Ledger. Quoting, job notes, and invoices work better when they live in one system. No SkyView waitlist pitch here.
Why “just add it” quietly destroys margins
Commercial drone work has fixed costs you cannot invent later: travel, weather windows, airspace homework, battery cycles, and processing time. When a client expands scope mid-job and you absorb it as goodwill, you are not being flexible—you are rewriting the economics of the job after the price was locked.
Common creep patterns:
- Extra acres, roofs, or structures after the quote locked a smaller footprint
- “Can you grab thermal too?” when the quote was visual-only
- A second flight day implied as “part of the same job”
- New file formats, higher resolution, or a client portal share that was never in the proposal
- Same-day “also document the staging yard” after wheels-up on the primary site
None of those are rude requests. They are new work. New work needs a written change order (CO) before you fly more, process more, or promise a new due date.
The change-order ladder (use it in order)
Treat every mid-job expansion the same way. Do not invent a special process for your nicest clients.
- Notice the creep — Name what changed relative to the accepted quote (area, sensors, deliverables, timeline, access constraints).
- Pause incremental flying — Do not keep collecting “just a little more” data until the CO is clear. Extra batteries spent cannot be unspent.
- Write the CO — Short, specific, tied to the original quote ID or job ID.
- Price the delta — Flat add, hourly add, per-acre / per-structure add, or processing surcharge—whatever matches how you sell. Show the difference, not a brand-new full rewrite unless the job truly flipped.
- Get client approval in writing — Email, portal accept, or signed PDF. Texts that say “sure” are weak; attach them to the job if that is all you have, and still send a confirming CO summary.
- Fly / capture the new work — With photo or flight-log evidence that the new scope happened.
- Invoice as line items — Original quote lines stay; CO lines appear separately so accounting and the client can see the story.
That ladder is the whole habit. Everything below is detail for each rung.
When scope creeps: name it out loud
Clients often do not realize they are changing the deal. Your job is to say, calmly: “That’s outside the accepted quote. I can add it as a change order—here is what it would cost and when I can deliver.”
Write three sentences in the job notes the same day:
- Original scope (one line)
- Requested add (one line)
- Impact (time, sensors, processing, or schedule)
If you cannot state the impact, you are not ready to price it. Do not fly the add while you “figure it out later.” Later is when resentment and unpaid evenings live.
Written CO before more flying
A usable CO is boring on purpose:
- Job / quote reference
- Date of request and who asked
- Description of added (or removed) work
- Deliverables added or changed
- Pricing delta and how it will appear on the invoice
- Revised schedule or “same window if weather holds”
- Approval line (name, date, method)
You do not need a lawyer’s novel. You need something you can hand to the client and to your future self when the invoice is questioned in sixty days.
If the add is safety-critical or access-constrained (new corridor, night work, escort required), say so in the CO. Those constraints change cost and calendar even when the “extra” looks small on a map.
Pricing the delta without rewriting the whole quote
Rewriting the entire proposal every time scope shifts trains clients to treat your quotes as drafts forever. Prefer a delta:
- Keep the original accepted total as baseline
- Add CO-001, CO-002… with clear descriptions
- Only re-quote from scratch when the job’s purpose changed (different site, different product family, or a cancel-and-replace)
Price drivers worth naming on the CO:
- Additional flight time or a second mobilization
- Extra sensor payload or dual-pass collection
- Processing / delivery format changes
- Rush turnaround
- Standby caused by client-controlled access delays (if your terms allow)
Nationwide shops: keep the structure of COs consistent across states even when tax, travel, or permit costs vary. The ladder stays the same; the line-item labels can reflect local reality.
Client approval is a gate, not a courtesy
Do not treat verbal “go ahead” on the pad as approval for a material add. If the client is standing next to you and wants more flown now:
- Send the CO summary from your phone (or dictate it into the job record and email it)
- Get an explicit “approved” reply before the extra pattern
- If they refuse to pause, you can still decline the free add—better an awkward minute than an unpaid afternoon
Approval should live next to the quote and the job notes. Scattered approvals in three inboxes are how CO history disappears.
Photo / evidence of the new work
When you invoice a CO, you should be able to show that the new work happened:
- Still frames or a short clip tied to the added area or asset
- Flight log excerpt or mission name that matches the CO description
- Delivery folder or share link labeled with the CO ID
- Timestamped notes if weather or access forced a partial
Evidence is not theater for distrustful clients. It is how professional shops close the loop: request → approval → capture → deliver → bill.
Invoice line items: keep the story readable
On the invoice:
- Leave original quote lines intact
- Add separate lines for each approved CO (description + amount)
- Apply deposit / progress payments against the running job total per your terms
- Reference CO IDs in the line description so AP can match paperwork
If your books only show one lumped “drone services” total, the client’s AP team will ask why the number moved—and you will re-explain the job from memory. Line items end that loop.
Soft systems note (not a hard sell)
Change orders fail most often when the quote lives in a PDF, the “yes” lives in email, the flight notes live in a chat thread, and the invoice lives in a separate tool. Pilots then rebuild the narrative by hand. Keeping the quote, job notes, CO text, and invoice lines in one place—for example in Pilot Ledger—does not replace judgment. It keeps the ladder visible so the next person on your team can follow it.
A short week-one checklist
- Add a one-page CO template (even a saved email outline)
- Train yourself to pause before “while you’re up there”
- Require written approval above a dollar or time threshold you choose
- Attach evidence to the job when the CO is flown
- Invoice COs as their own lines within seven days of delivery when possible
Drone job change orders are not bureaucracy for its own sake. They are how you stay fair to the client and solvent as a business when the job evolves—without rewriting the whole quote every time someone finds one more thing to capture.