Skip to content
Dashboard
Set up HiVAM around your business · Chapter 1 of 4

Set up only what your first real job needs

Start with a real operating goal, such as booking and completing a hired FTL movement or moving cartons through a branch. The first setup path should collect the resources that goal actually needs. You can add additional facilities, trucks, employees and integrations later. The course describes the workflow and required evidence; labels and access may vary with the deployed release. Use the current feature matrix to distinguish platform capabilities, APIs and planned work instead of searching for a button that does not exist.

HiVAM product guides · About 4 minutes to read, plus practice · Reviewed

Your learning goals

What you’ll learn

  • Choose a setup path for the actual business model.
  • Create the smallest complete first-job resource set.
  • Verify saved records instead of relying on checklist ticks.

Useful terms

Master
A reusable party, goods, resource or policy record.
Activation
Reaching a useful saved business outcome, not merely opening pages.

Step-by-step operating routine

  1. Confirm organisation and service model

    Check the legal and trading identity, locale, timezone and operating pattern. Choose FTL, PTL or hybrid and owned, hired or mixed capacity accurately. Identify the owner responsible for setup decisions.

    Record or confirm
    • Organisation
    • Timezone
    • Service model
    • Capacity model
    • Setup owner

  2. Add the first service resources

    For point-to-point FTL, prepare the parties, route and actual carrier or vehicle. For a branch-based PTL job, add the real station and warehouse locations used. Do not create dummy facilities to satisfy an unrelated path.

    Record or confirm
    • Origin / destination
    • Required facilities
    • Carrier / vehicle
    • Responsible team

  3. Create people and limited access

    Invite the staff needed for booking, dispatch, custody and finance. Configure role and facility access. Start with the minimum permitted work, then test a restricted account before sharing real operational data.

    Record or confirm
    • Staff role
    • Facility scope
    • Permission reviewer
    • Invitation state

  4. Add the commercial and goods facts

    Record sender, receiver, payer, goods, units, handling and accepted payment terms. Connect only integrations needed for the first workflow. Confirm an actual successful connection operation rather than just a saved secret.

    Record or confirm
    • Party roles
    • Goods / units
    • Handling
    • Payment terms
    • Required connection

  5. Complete and review a real first job

    Save the booking and follow its movement, quantities, evidence and financial handoff. Reopen records after refresh or a second session. Mark setup progress from actual saved outcomes; sample work should remain visibly separate.

    Record or confirm
    • Booking ID
    • Movement
    • Delivery evidence
    • Financial handoff
    • Review result
Worked example

Two first-job paths

A hired FTL operator begins with the contracting customer, receiver, payer and carrier. A PTL operator begins with these parties plus a real origin branch, labelled packages and a destination custody point. Both complete a first booking, but the first operator does not invent a warehouse or owned truck just to fill a universal checklist.

  • Match the setup to the service.
  • Test permissions using a limited staff account.
  • Reopen saved source records to verify persistence.

Exceptions and mistakes to avoid

  • Do not enter real secrets in training worksheets.
  • A trial may temporarily expand capability access without expanding a user’s role.
  • The same setup task must not create duplicate masters after a retry.
Put it into practice

First-job setup checklist

List only real dependencies, then reopen the saved records. Keep future setup improvements on a separate optional list.

Illustrative row—replace it with your own private operating information.
Required recordWhy this job needs itOwnerSaved referenceVerified
Destination branchReceives PTL cartonsBranch leadActual branch referenceReopened successfully
Download CSV worksheet

Includes the illustrative row and blank rows. This is a planning worksheet, not a HiVAM import format. Keep your completed copy private; do not add credentials.

Check your understanding

Try answering first, then open the explanation. Use the worksheet and source records to practise the task.

Does a market-truck operator need an owned asset?

No. Use the actual hired carrier and supported market-vehicle workflow.

How should setup completion be verified?

By reopening saved records and completing a representative workflow, rather than counting page visits.

Connect the workflow

Put it to work with HiVAM

Use these connections to explore the relevant product workflows. Confirm access in your deployed release; API capabilities require an integration or an available interface.

Platform capability · Starter and above

Guided setup around your business

Follow guided activation around the operating model and saved resources.

Platform capability · Starter and above

Saved views, access scopes and audit evidence

Check the staff role and facility scope before using real customer data.

Compare all capabilities and availability

Keep your learning moving.

0 chapters marked complete. Reading progress stays in this browser; it is not a qualification or your company’s setup progress.

Try the workflow with your team.

Bring a representative job and an exception to a HiVAM demonstration. Review saved records, permissions and handoffs alongside the interface.