Contract Lifecycle
How contracts are created, what they contain, and how their status changes from award to completion.
Overview
Contracts on MXBS are generated automatically the moment you confirm your bid selections. You do not write contracts manually — the system assembles them from the bid data, operator profile terms, and your trip details. Each contract represents an agreement between you and one bus operator for a specific vehicle allocation on your trip.
Auto-Generated Contracts
Contracts are built from the bid you accepted and the operator's profile terms. If any of this source data changes after the contract is generated, the contract must be formally edited — the system does not update it retroactively.
Contract Statuses
| Status | Meaning |
|---|---|
| PENDING_SIGNATURE | Auto-generated after award, waiting for signatures from both parties |
| ACTIVE | Both parties have signed — the trip is confirmed |
| COMPLETED | The trip has executed and the contract is archived |
| CANCELLED | Either party cancelled the contract — immutable, cannot be reinstated |
| SUPERSEDED | This version was replaced by a newer version after an edit |
What a Contract Contains
Every contract includes the following information:
Trip details:
- Trip name, travel dates, pickup and drop-off locations
- Number and type of vehicles awarded to this operator
Pricing:
- Price per coach
- Total contract value (price × vehicle count)
- Tax amount and applicable tax rate
- Itemized cost breakdown from the original bid
Operator terms (from the operator's profile):
- Cancellation policy (e.g., refund schedule based on days before departure)
- Payment terms (deposit amount, balance due date)
- Custom terms and conditions the operator has configured
Signature tracking:
- Who signed and when (you, then the operator)
- Current version number (v1 for the original, v2 after the first edit, and so on)
Who Signs First
Trip Owners always sign first. After you sign, the operator is notified to review and countersign. You cannot see the operator sign — but once they do, the contract status automatically changes from PENDING_SIGNATURE to ACTIVE and you receive a notification.
See Signing a Contract for the step-by-step signing flow.
Version History and Superseded Contracts
If a contract is edited after it becomes ACTIVE, the original contract is marked as SUPERSEDED and a new version is created (v1 → v2). Both versions remain accessible from the contract detail page via the Version History tab. This provides a complete audit trail of any changes made after initial execution.
The most recent non-superseded version is always the operative contract.
Viewing Contracts
Navigate to Contracts in the left sidebar. Use the status filter to narrow the list:
- Filter by PENDING_SIGNATURE to see contracts awaiting signatures
- Filter by ACTIVE to see fully executed contracts for upcoming trips
- Filter by COMPLETED or CANCELLED to access historical records
Click any contract row to open the full detail view, including all terms, the cost breakdown, signature history, and version history.