Implementation and migration
Agree what a successful operator launch requires.
Moving an operation involves customer records, container inventory, open work, billing rules and the people who use them. TossDock Pro implementation is scoped for each qualified large-scale operator. A useful launch plan names the work, its owner and the evidence needed to accept it.
Define the first deployment
Identify the yards, service area, teams and workflows included in the proposed launch. Separate required day-one work from later expansion. Confirm the commercial scope, support arrangements and dependencies in writing. The complete Pro partnership is the OS offering; deployment sequencing helps the team manage the rollout without creating a Basic software tier.
Reconcile the records before importing
Inventory your current systems and exports. Agree identifiers and ownership for customers, containers, trucks and open jobs, and identify duplicate or incomplete records. Compare representative records with the source before accepting a migration. Open invoices and balances need a specific reconciliation plan with the people responsible for the books.
- Record which source wins when two exports disagree.
- Set a cutoff and a process for changes made during migration.
- Confirm which history is included and what remains available elsewhere.
Rehearse real work with the right people
Ask dispatchers, drivers and the office to run representative workflows using agreed test records. Include reassignment, delayed service, lost connectivity, rejected saves and billing questions. Configure individual access and verify which role can perform each action. Training is more useful when the participant can complete the work and explain an exception.
Accept the connections and the operating plan
Configured providers need their own checks: identity, payment processing, accounting, messaging and any field hardware in scope. Record the evidence, reviewer and unresolved limitations for each required item. Choose a cutover, recovery and escalation plan the operator can support. A sales stage or completed checklist alone does not award a zone or activate a production service.
Prepare the conversation
A practical launch acceptance checklist
Each required item should have an owner, a status, supporting evidence and an acceptance decision. “Not applicable” needs a reason.
- Operating scope, written commercial terms and zone decision reviewed.
- Imported records reconciled against the agreed sources.
- Individual roles and access checked with the intended users.
- Dispatch, field and office workflows rehearsed, including exceptions.
- Required providers and hardware validated for the agreed environment.
- Training, cutover, recovery, support and unresolved limitations accepted.
Use this in an evaluation
Review exercise: an essential connection is unavailable
Before choosing a launch date, take one required connection out of the rehearsal. Walk through what the dispatcher or office sees, which work can continue and when the team escalates. Use that result to decide whether the limitation is acceptable or blocks launch.
- Identify the affected workflow and accountable owner.
- Demonstrate the approved fallback and reconciliation process.
- Record the evidence and the person authorized to accept the outcome.
Common questions
How long does implementation take?
Timing depends on data readiness, the workflows in scope, required providers, hardware work and the operator’s availability for review. A schedule is agreed after discovery; the public site does not promise a fixed launch time.
What is included in the implementation price?
The proposal defines the annual platform relationship, one-time deployment work and separately scoped hardware or connectivity. Migration depth, training, integrations and support responsibilities should be explicit before approval.
Does an accepted OS deployment automatically activate TossIt?
No. TossIt remains a separate consumer Beta with its own local capacity, provider and operating requirements. Participation is limited to the qualified TossDock Pro operator for the awarded zone and requires the appropriate activation checks.