Part 107 made commercial drone operations possible at national scale. It gives operators a known framework for small UAS work, remote pilot certification, visual line of sight rules, preflight duties, and waiver paths.
The proposed Part 108 framework points to a different trust model. BVLOS operations can involve new personnel roles, accepted aircraft systems, approved operating areas, strategic deconfliction, conformance monitoring, cybersecurity, and formal records.
The practical shift
For many Part 107 operations, compliance still lives close to the remote pilot in command. That model works for many visual line of sight missions. It does not scale cleanly to high-frequency BVLOS fleets with shared aircraft, rotating crews, and external evidence demands.
As operations scale, trust must move into the system. The organization needs to know before launch that the right configuration, people, procedure, area, and evidence are in place.
Why this matters before the final rule
Part 108 is still rulemaking, and final details can change. The direction is clear enough to prepare. Operators that wait for a final rule can lose months assembling aircraft status, training history, flight logs, risk records, and maintenance evidence.
The better preparation is to make records come from normal work. Dispatch creates the release record. Maintenance updates aircraft state. Training updates crew currency. Findings update readiness. Evidence packs read from those source records.
Sources
Build the record while you keep flying.
Ledger runs deterministic checks before release and keeps proposed Part 108 readiness evidence in shadow mode while you operate under today's authority. See BVLOS compliance software, Part 108 recordkeeping software, or the Part 107 BVLOS waiver to Part 108 transition brief.