Part 105 · Drop zone operations
Manifest & scheduling
Schedule the day's loads and the staff working them on one calendar, so the manifest is a shared record the whole drop zone reads from rather than a whiteboard one person owns. Conflicts surface before they post. It replaces running the day off a board that gets wiped every evening and reconstructed from memory the next morning.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
The drop zone manifestor or operations lead who runs the day's loads and the staff working them, and needs the manifest to be a shared record the whole DZ reads from rather than a board one person owns.
What it replaces
The whiteboard manifest one person owns, wipes every evening, and reconstructs from memory the next morning.
What manifest & scheduling gives you
- Schedule the day's loads and the staff working them
- One calendar the whole drop zone reads from
- Conflicts surface before they post
A shared manifest, not a whiteboard one person owns
As planned, the drop zone would schedule the day's loads and the staff working each one on a single shared calendar, so the manifest is a record the whole DZ reads from rather than a board one person owns and re-creates every morning. The intent is that the day's plan carries forward as a record instead of being rebuilt from memory each morning off a wiped board.
- Schedule the day's loads and the staff working them
- One calendar the whole drop zone reads from
- Carry the day's plan forward without rebuilding a wiped board
Conflicts surface before they post — not on the loading line
Built as a scheduling record, the calendar would catch a conflict — such as a double-booked instructor — before it posts, so it's surfaced ahead of the loading line rather than discovered at the aircraft. This is a scheduling-and-staff record for the loads, not a visual load-builder, a tandem/video slot-booking flow, or a booking-to-payment product, and it keeps no jumper telemetry — the manifest is an operator-kept log.
- Conflicts surface before they post
- A double-booked instructor caught ahead of the loading line
- A scheduling record, not a load-builder or booking-to-payment product
How an operator uses this
The drop zone schedules the day's loads and the staff working them on one shared calendar, so the manifest is a record the whole DZ reads from rather than a whiteboard one person owns and re-creates every morning. Scheduling conflicts surface before they post, so a double-booked instructor is caught ahead of the loading line. It's a scheduling record for loads and staff — not a visual load-builder, tandem/video slot-booking, or booking-to-payment product.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Manifest & scheduling, step by step
Schedule the day's loads and the staff working each one on a shared calendar.
Read the manifest as one record the whole drop zone works from.
Catch scheduling conflicts before they post, not on the loading line.
Carry the day's plan forward without rebuilding a wiped whiteboard each morning.
Questions
Manifest & scheduling — frequently asked
Is this a visual load builder or a tandem-booking system?
No. It's a scheduling record for the day's loads and the staff working them — a shared calendar that catches conflicts. It is not a visual load-builder, a tandem/video slot-booking flow, or a booking-to-payment revenue loop.
Why a shared manifest instead of a whiteboard?
The whole drop zone reads from one record rather than a board one person owns and rebuilds from memory each morning, and scheduling conflicts surface before they post instead of being discovered at the aircraft.
Every Part 105 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee manifest & scheduling on your operation.
It's part of the Part 105 workspace. Request a demo or join the waitlist.