Write down the operating model and must-have outcomes
Describe whether you run FTL, PTL or both; use owned, hired or mixed vehicles; operate branches and depots; store inventory; and manage customer credit or freight collection. Include the people responsible for dispatch, receiving, delivery, finance and administration. The same system can be a strong fit for one business and a poor fit for another.
Define a short list of outcomes for the first release: accepting a booking, dispatching a real movement, explaining outstanding goods, completing POD review and reconciling an invoice or settlement. Distinguish these requirements from conveniences and future ideas. An important API-only feature can be acceptable if the integration work, owner and cost are explicit.
Use a test pack with ordinary work and exceptions
Prepare anonymized examples that represent your operation. Include a happy path, a split or partial quantity, a delivery refusal or shortage, a hired truck advance and a corrected commercial document. Ask the vendor to process them from the beginning, then inspect the final records and export.
A demo with prepared totals can conceal broken handoffs. Reopen the booking, package history, movement, delivery evidence and commercial documents. Verify that the quantities and balances reconcile after the exception and after a repeated submission. Do not put unnecessary personal or confidential information into a public demonstration environment.
| Test | Question to answer | Evidence to request |
|---|---|---|
| Partial movement | Where is the quantity that did not leave? | Package or quantity history by location and departure |
| POD rejected | What is delivered but still ineligible for billing? | Review state, reason and source document link |
| Duplicate action | Does a retry produce another movement or charge? | Before/after balance and retained event history |
| Restricted user | Can a user see another branch or unauthorized salary data? | A live login with the intended role and facility scope |
| Integration failure | How does staff know work stopped? | Failure state, retry history and responsible next action |
Plan migration and the first real job together
Start with the minimum clean masters needed for the first workflow: relevant parties, locations, vehicles or hire arrangements, drivers and commercial policies. Import small batches, inspect validation errors and reconcile the saved records before importing the remainder. Retain identities when duplicate masters are merged so historical work does not lose its references.
Decide how opening balances, active consignments, pending PODs, advances and outstanding invoices will be brought across. Record a cutover date and who approves the reconciliation. Guided setup should use saved records, resume across devices and avoid requiring unused modules merely to complete a checklist.
- Assign an owner for each master and opening balance.
- Keep an export of the source data.
- Reconcile record counts and financial totals, not just an import success message.
- Give the actual staff a small end-to-end task before expanding the rollout.
Inspect role, branch and plan access together
A feature’s presence in a plan does not give every employee permission to use it. Test the combination of subscription entitlement, trial grant, role and facility scope. Restricted information should remain restricted in search, exports, direct record links and AI answers, as well as in the visible navigation.
Ask what happens when a trial expires, the company downgrades or an API key is revoked. Existing records, export rights, retention and recovery dates should be stated clearly. Staff should receive an actionable explanation when access changes, rather than discovering an unexpected loss while completing critical work.
Compare the complete commercial arrangement
For tracking, separate the software subscription from purchased hardware, rental or bundled devices, installation and refundable deposits. If you use both existing and HiVAM trackers, calculate the mixed arrangement rather than applying one headline rate to every truck. Check the billing cycle, GST, annual treatment, activation dates and tracker replacements.
Also confirm integration charges, support arrangements, implementation work and which APIs or workflows the proposed plan includes. The public calculator is an estimate for the selected configuration; the agreement and actual activated usage govern billing. A free-trial feature grant is different from a hardware trial or deposit.
Test AI answers with questions you can independently verify
Ask questions for which you know the answer: a pending invoice total, an undelivered quantity or a specific POD exception. Inspect the source links, filters, date window and the records contributing to the result. An assistant should say when it lacks information rather than inventing a confident number.
Repeat the question as a restricted staff member. Then inspect any proposed action: its target, effect and required review. Verify that permissions and the current record state are rechecked when it executes. Predictive claims need their own validation; rules and simulations should retain their actual labels.
Agree what “ready” means before a rollout
Record the verified scope, unresolved issues, training plan, reconciliation checks and support contacts. A production readiness decision needs evidence from the intended deployment, integrations and operating volume. A feature being present in source code or a public page does not establish that the whole workflow is ready for your company.
HiVAM’s published matrix identifies capabilities, plan mapping and API or planned surfaces. Use it to prepare questions, then confirm the deployed release against the workflows you need. Planned items should have an explicit separate agreement if they are material to the purchase; avoid treating a roadmap description as a working capability.
A practical first-week acceptance task
Choose one representative booking. Create only its required masters, save the booking, allocate its actual resources, record movement and delivery, inspect the evidence and reconcile the resulting commercial record. Ask the dispatcher and finance user to explain what they see independently.
- The saved record can be reopened after signing out.
- Each team reaches the same source record without re-entering the booking.
- The restricted user sees only permitted information.
- A retry and an exception preserve the correct quantity and balance.
- Exported evidence matches the on-screen filters and totals.
Bring your workflow to the conversation.
Review the capabilities you need with a real FTL, PTL or hybrid job.