Skip to main content
GullySystem
Logistics

Job Cards for Moving companies

Retain the accepted moving work, actual goods handovers and unresolved exceptions on one operational record.

Field Service

Does this function belong in your operation?

Use when an accepted move or loading assignment needs a shared record of scope, actual work, goods handovers and unresolved exceptions.

The operator accepts a specific moving or labour-only assignment for execution.

Use the job card as the operational move record, with accepted scope, actual collection and delivery handovers. Preserve declared versus observed goods, customer-packed contents and incomplete checks. A changed destination or extra item needs an authorised instruction and capacity review. Record exceptions alongside acknowledgements so a signed delivery note cannot silently erase a missing item or unresolved condition concern.

Bring the records the workflow depends on.

  • Accepted estimate and included work at each address
  • Goods references, declared contents and condition observations
  • Assigned team, authorised collection and receiving contacts
  • Scope changes, handover evidence and uncompleted work

Outputs to check

  • Move work and custody-event history
  • Collection and delivery reconciliation with recorded exceptions
  • Approved billing inputs and unresolved customer follow-up

Follow the job cards workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Open the accepted move

    Link the current scope and locations, identifying actual responsibility for packing, transport and unloading. Keep a labour-only assignment limited to its accepted work.

  2. 2. Check the starting record

    Compare actual presented goods and access with the survey or declaration. Mark customer-packed contents as declared where not checked; do not infer contents from a sealed carton label.

  3. 3. Record authorised changes

    Retain extra-item or destination instructions and review capacity. The customer authorises commercial scope, while the supervisor or qualified operator decides whether the work can proceed.

  4. 4. Maintain actual handovers

    Record what was collected, transferred and delivered, with the responsible people and permitted evidence. If storage is separately accepted, identify the actual custodian and receipt before treating goods as stored.

  5. 5. Reconcile outcome and follow-up

    Record the authorised receiver’s acknowledgement, exceptions and remaining work. Send supported billing inputs to accounts while preserving missing-item, condition or service concerns for separate review.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Move coordinator

Maintains the current instructions and obtains required customer decisions when the actual work differs from the accepted scope.

Crew supervisor

Records actual goods and work handovers, keeping unobserved conditions and customer declarations distinct from checked facts.

Receiving representative

Acknowledges the recorded delivery within verified authority, with any exceptions preserved alongside the handover evidence.

Resolution owner

Reviews incomplete work and customer concerns separately from operational closure and any financial adjustment decision.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Sealed carton contents are disputed

Preserve the declared contents and what was actually observed at handover; do not manufacture a verified item list.

Destination cannot receive the goods

Hold the original delivery as incomplete and obtain an authorised revised destination or separately confirmed custody arrangement.

Item is missing or condition differs

Record the specific exception and evidence for review without deciding liability or compensation through a job status.

Person present lacks receiving authority

Verify an authorised instruction before completing the handover; physical presence alone does not establish acceptance rights.

Can this work independently?

The job can run from entered customer, scope and goods references. Estimates provide accepted terms and resource allocation supplies acknowledged assignments. Evidence access must match customer privacy needs. Storage, claims and financial settlement require separately confirmed processes and decision owners.

Systems and records it connects with

  • Estimates: Accepted scope and authorised variations.
  • Resource allocation: Responsible team and acknowledged resources.
  • Invoice management: Actual supported work and payer references.
  • Customer resolution: Missing-item and condition concerns with preserved evidence.

Configure, test and introduce the workflow.

  • Trace a real move from survey to collection and delivery, retaining differences instead of reconstructing a clean outcome.
  • Agree how to record sealed cartons, condition observations and receiving authority with restricted evidence access.
  • Test a changed destination, missing item and labour-only completion; confirm that exceptions remain open when work or billing closes.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Actual handovers identify responsible parties and recorded exceptions.
  • Declared contents and observed condition are distinguishable.
  • Extra work retains customer authority and operational review.
  • Operational completion does not dismiss a claim or establish payment.
Moving companies

How the business operates.

A moving company accepts a defined transfer of household or office goods, then coordinates the people, transport and handovers needed for that move. The job begins with a surveyed or declared load and access conditions, not a room count alone. Full-service moves and labour-only loading assignments have different responsibilities. This scope covers ordinary moves within the operator’s accepted service area and capability; specialist handling, international work and interim storage need separate confirmation. It overlaps packers-and-movers, with emphasis here on scope changes, crew commitments and custody evidence rather than assuming every move includes packing, storage or a company-owned truck.

Survey and estimating

Record items to move, items excluded, origin and destination access, and the requested service components. Distinguish customer declarations from observed information and hold unassessed specialist items for review.

Move coordination

Confirm dates, customer contacts and crew needs against the accepted scope. Keep proposed external crews or transport separate from an acknowledged assignment, including changes caused by a delayed property handover.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Survey or customer-declared item list with exclusions and unassessed areas
  • Origin and destination contacts, access constraints and agreed service components
  • Versioned estimate, customer acceptance and payer authority
  • Crew and transport assignments with external acceptance where applicable

Operational bottlenecks to check

The actual load differs from the survey

Extra furniture or an undisclosed collection address changes the work and capacity needed. Preserve the original estimate and seek a reviewed change before recording a new commitment.

The crew is free but the move cannot proceed

A missing lift slot, blocked loading access or unavailable receiver can invalidate the plan. Resource availability alone does not establish customer or property readiness.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Capture the proposed move

    Record addresses, requested dates and the person authorising the work. Ask whether packing, transport and unloading are included or whether the request is for labour only.

  2. 2. Establish the scope

    Review the load and access information through the agreed survey method. Keep unseen goods and missing destination details explicit instead of assuming the estimate covers them.

  3. 3. Accept the current estimate

    Retain the customer’s accepted revision and actual billing arrangement. Confirm required booking conditions separately from a provisional calendar entry or unverified payment message.

  4. 4. Allocate and brief the team

    Match the accepted work to available people and resources, with actual partner acknowledgement. Share the current scope and relevant access information while limiting unrelated personal data.

  5. 5. Record collection and handovers

    Compare actual goods and conditions with the agreed record. Capture changes and custody transfers, including an authorised interim destination if the original delivery cannot proceed.

  6. 6. Reconcile delivery and account

    Record delivered items, uncompleted work and the receiving person’s authority. Pass supported charges to accounts and keep unresolved damage or missing-item follow-up open after operational completion.

Industry reports to connect with

  • Accepted moves with unconfirmed resources or missing access details
  • Survey-to-actual load changes and their approval status
  • Crew assignments, overruns and displaced commitments
  • Collection and delivery exceptions by move and responsible owner

Questions before implementation.

When should moving companies consider job cards?

Use when an accepted move or loading assignment needs a shared record of scope, actual work, goods handovers and unresolved exceptions. The operator accepts a specific moving or labour-only assignment for execution.

What should we bring to the requirements discussion?

Bring anonymised examples of Accepted estimate and included work at each address; Goods references, declared contents and condition observations; Assigned team, authorised collection and receiving contacts; Scope changes, handover evidence and uncompleted work. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Retain the accepted moving work, actual goods handovers and unresolved exceptions on one operational record. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The job card does not supply handling procedures, prove unseen contents, certify goods condition or determine insurance and liability.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Actual handovers identify responsible parties and recorded exceptions. Use this check when reviewing the first working version.

Talk to us

Discuss job cards for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements