If you cannot answer “has this job’s deposit cleared?” without opening three tabs and a bank app, you do not have a deposit system. You have a hope. Drone job deposits are supposed to protect flight day. They only work when the money, the quote, and the calendar share one status—from the moment the client accepts to the morning you load batteries.
This is a Pilot Ledger Sales post. Opinionated on purpose. Not SkyView. Not a marketplace pitch. Soft CTA only: run quotes and deposits in one place at Pilot Ledger.
Deposits are not “nice to have”
Commercial drone work eats calendar. Drive time, weather windows, airspace checks, and a crew that cannot magically appear for a free maybe. An accepted quote without money is a soft booking. Soft bookings get canceled at 9 p.m. the night before. Soft bookings also get “we went with someone cheaper” after you blocked Thursday.
A deposit is the client putting skin in the game. Tracking that deposit is you putting skin in your own ops. If the deposit lives in a Venmo screenshot and the job lives in a spreadsheet, you will lose the thread. Guaranteed.
Quote acceptance is the start line—not “we’ll invoice later”
Stop treating “sounds good” in email as the same thing as acceptance. For deposit tracking, acceptance means:
- Scope locked enough to price (deliverable list, site, date window)
- Quote ID or version recorded
- Client named on the job (company + contact)
- Deposit amount and due rule written (percent, flat, or milestone)
- Next status: deposit pending—not “scheduled”
If your process jumps from “they said yes” straight to “on the calendar,” you trained clients to treat your calendar like a free hold. Change the rule: no deposit, no hard hold. Weather holds and soft penciled windows are fine. Flight-day commitments are not free.
What “tracked” actually means
Drone job deposits tracking is not a folder of PDFs. It is a status machine on the job:
- Quoted — proposal sent, awaiting decision
- Accepted / deposit due — client agreed; money not confirmed
- Deposit received — cleared in your books (not “they said they sent it”)
- Scheduled — flight window on the calendar with PIC / aircraft if relevant
- Flown / delivered / final invoice — deposit applied, balance due, paid
If a status can be true in Slack and false in QuickBooks, you do not have tracking. You have theater. Pick one source of truth. Update it when money moves—not when you remember on Sunday.
The failure modes pilots pretend are “just how clients are”
The floating Venmo. Client sends money with no job ID. You guess which quote it was. Wrong guess = awkward refund and a burned Thursday.
The “we’ll pay on site.” On site is when you have already driven two hours. That is not a deposit. That is a tip jar with a Part 107 certificate.
The partial that looks full. Client pays half the deposit and assumes the slot is locked. Your board must show remaining due, not a green check that lies.
The refund fog. Weather scrub, client cancel, no-show—each needs a written rule before flight day. If refund policy lives only in your head, you will invent policy under stress and resent the client for it.
The double book. Two accepted quotes, one aircraft, one deposit missing. Without deposit status on the board, you schedule optimism.
Make the deposit rule boring and visible
Write it once. Put it on the quote. Repeat it on acceptance:
- Deposit amount (or percent of quote)
- When it is due (on acceptance, within 48 hours, X days before flight)
- What happens if it is late (slot released, date moves to next open window)
- What is refundable vs. credit-only for weather vs. client cancel
- How the deposit applies to the final invoice
Boring beats clever. Clever deposit schemes that change per client are how you create exceptions you cannot administer at 6 a.m. when fog rolls in.
Nationwide shops: same rule language across states. Local payment norms vary; your ops status should not. ACH, card, or check—all fine. The board cares about cleared and linked to job ID, not which app made the ping.
From deposit received to flight day
Once the deposit is marked received:
- Confirm the flight window in writing (date range or hard slot—say which)
- Attach access notes, site contacts, and airspace / NOTAM homework to the same job
- Block the aircraft / PIC so the deposit is not protecting an empty promise
- Set a reminder for balance due and for “confirm weather call” the day before
If deposit received does not trigger calendar + prep packet, you collected money and still run ops like a hobby. The deposit’s job is to fund commitment. Your job is to convert commitment into a flyable plan.
What Pilot Ledger is for here
Pilot Ledger is job and money ops for commercial pilots—not a processing waitlist pitch. Use it when you want drone job deposits tied to the same record as the quote and the flight day: status you can read without a scavenger hunt, reminders that fire before the no-show, and a soft path from acceptance to wheels-up.
Start at Pilot Ledger or jump to pricing if you already know you need the stack. Soft ask. Harder ask: stop letting unpaid “yes” messages own your week.
Practical notes (blunt checklist)
- Never schedule a hard flight day on an uncleared deposit unless you enjoy unpaid drive time.
- Put the job ID in every payment memo you control; ask clients to include it.
- Log who marked the deposit received and when—future-you will thank present-you during a dispute.
- Review no-shows monthly; raise deposit % or move due-date earlier for chronic late-payers.
- Keep refund language identical on quote and invoice so you are not renegotiating ethics at the truck.
Deposits are simple. Tracking is the discipline. If your board cannot show quote → deposit → flight day in one glance, fix the board before you blame the market.