Prepare each shift, coordinate exceptions, and give IT a clear release and recovery routine.
Confirm the selected facility, door occupants, waiting visits, active shuttle work, holds, and physical assets. Name the dispatch owner.
At handover, review open requests, active moves, ready doors, waiting drivers, failed or blocked checkouts, and unassigned assets. Reconcile physical counts and assign an owner to every unresolved issue.
Deploy the server, browser app, desktop client, and database schema as a tested set. Use production mode, a strong unique server secret, explicit allowed origins, and separate database identities for runtime and migrations.
Public booking and phone QR flows need a reachable HTTPS origin serving the browser app and proxying /api. The marketing website is separate from this operational application.
GET /api/health.Server startup checks the schema but does not apply migrations. Validate the actual target environment before a live rollout.
Assign owners for API health, SQL failures, disk space, backup age, login failures, gate exceptions, and audit retry warnings. Test that alerts reach the responsible person.
Agree on maximum acceptable data loss and outage time. Verify off-site retrieval and perform a restore drill into a separate scratch environment. A scheduled backup job alone is not evidence of a usable backup.
Stop relying on stale board or map state for new instructions.
Capture time and timezone, reference, tractor and trailer, origin and destination, event, actor, and notes.
IT diagnoses the failure. Read authoritative records before replaying work, match existing events, and confirm physical positions to prevent duplicates.
The supervisor and transportation lead confirm that open exceptions and manual events have been reconciled.