Boat Transport Ops — Where We Stand (Feb 26, 2026)
We're keeping you updated on the rebuild of Boat Transport Ops — the multi-tenant operations platform for boat transport companies. Here's the current status and what's next.
The big picture
Boat Transport Ops is a full rebuild of the system we ran for over 10 years. The new system is built so multiple transport companies can run on one platform, each with its own data, users, and rates, while sharing the same workflows for trips, BOLs, quotes, and invoices. Everything is built with a solid database, multi-tenant design, and company-specific rate tables already in place.
What's done so far
Database and multi-tenancy — Full schema for trips, fleet, companies, users, BOLs, billing, quotes, invoices, incidents, work orders, and more. Every company is isolated by company; Company admins see all and control all for there company, each company sees only its own data.
Quote → Billing → BOL → Invoice — Tables and links are in place. Drivers can create BOLs in the field with or without a Boat quote; the office can link them later.
Company rate tables — Nine rate tables plus permit costs per company; new companies get a full copy to customize.
Boat Transport Ops — Modern, directory-based project; more consistent CRUD and a larger, more capable codebase than the old system.
Trip structure — Stops (trip_drops), BOL and Boat Condition limits per stop, one Load Dimensions and one Load Drop Off per trip. Add-button and validation logic follow these rules.
Company settings and notifications — Company timezone (so times and the footer clock use company time). Office email addresses (trailer repair, truck service, documents, etc.) come from Company Settings and sync to the right tables. Auto Mailer aligned with current setup.
Calendar — Holiday table supports oversize restrictions (none / state / full) and date ranges; calendar uses this for display and planning. All Holidays are updated to 2050. Guest can view the upcoming holidays.
Weekly reports — Weekly fuel and payout now come from trip-level data (trip_fuel, trip_payout) via views keyed to the weekly report; the old weekly_fuel and weekly_payout tables are removed.
Truck assignments (foundation) — The truck_assignments table and screens are in place. The design is documented: one place for office to assign drivers to trucks, with history and "one current driver per truck." A schema migration is ready for full history, DB-level "one current per truck," and links from truck_lube, truck_pm, truck_expiration_dates, and trip_sheet to assignments. Sync logic (when you assign or unassign a driver, update users, truck_profile, and related tables) is planned but not yet implemented in the app.
What we're working on now
Invoices and billing (Phases 1–5) — Company-scoped invoices and permissions, "create invoice from quote" and "view quote" on invoices, matching quote and invoice layout, rate tables in the UI, "Calculate from trip" and "Recalculate," and polish (e.g. quote PDF, convert quote to invoice).
Truck assignments (implementation) — Event logic so that when office assigns or unassigns a driver in truck_assignments, the system updates the driver's primary truck, the truck's assigned driver, and contact info for PM/lube/expiration alerts. Plus: succession (one current driver per truck), block reassignment if the outgoing driver has open trips, no hard-delete of assignments (unassign only), and later: trip sheet defaulting to the driver's assigned truck and optional pool-truck choice per trip.
Audit and fixes — Multi-tenancy checks, SQL safety, session use, and cleaning up remaining legacy behavior (e.g. weekly_activity_report, save-status company check) so everything is consistent and secure.
Plans going forward
Core platform — Finish Phases 1–5 and the audit so the quote–invoice flow and company lock are solid and ready for daily use.
Truck assignments — Implement sync, succession, active-trip lock, and trip-sheet truck default (and pool truck when we add that).
Company signup and billing — Account app for signup and subscription (Stripe first, then PayPal), so new companies can join and pay in a self-serve way.
Launch — We're not naming a single "launch date" because the remaining work is mostly configuration, event code, and UI in the IDE. We're in the last major stretch and are aiming to have the core flow and company lock in good shape in the next several weeks to a couple of months, with polish and testing after that. We'll post again when we're close to opening signups or a soft launch.
Summary
Done: Database, multi-tenancy, rate tables, Trip structure (stops, BOL/condition limits), company timezone and office emails, calendar oversize holidays, weekly reports from trip data, truck_assignments table and UI (sync and rules still to be implemented).
In progress: Invoice/billing Phases 1–5, truck assignment sync and rules, and audit/fixes.
Goal: A reliable, multi-tenant platform where your company—and others—can run trips, BOLs, quotes, and invoices in one place.
Thanks for your patience. We're building this so it's worth the wait.
