Skip to main content
GullySystem
Automotive

Job Cards for Wheel alignment centres

Keep the steering complaint, accepted check, machine evidence and actual alignment outcome on the same vehicle visit.

Field Service

Does this function belong in your operation?

Use for fixed-site alignment centres that need to distinguish check-only visits, completed adjustments and referrals for other work. A tyre sale or general repair order is a separate scope.

The centre accepts a vehicle for an alignment assessment or separately authorised work within its declared capability.

Keep the customer complaint, measurement context and actual outcome on one visit record. Initial and subsequent sheets need the vehicle, machine and technical reference that produced them. Distinguish a check-only outcome, an accepted adjustment and a referral for other work. A returning vehicle opens a linked visit; it does not replace the earlier evidence or establish that the previous job caused the complaint.

Bring the records the workflow depends on.

  • Vehicle identifier, model details and customer-reported symptom
  • Commissioning customer, referring garage, payer and buying-authority record
  • Accepted assessment scope and chargeable additions
  • Technician-selected specification reference and machine identity
  • Initial findings and readings with their source visit

Outputs to check

  • Visit record with initial and subsequent measurement references
  • Accepted-work and declined-work history
  • Check-only, adjusted or referred outcome with unresolved findings
  • Actual-work billing handoff and repeat-visit links

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 visit

    Record the complaint and customer authority before assigning work. Link a referring garage without assuming it will pay or authorise additions.

  2. 2. Record the assessment context

    The technician checks vehicle details and records the specification source, machine and initial observations. Keep earlier reports as history rather than relabelling them as today’s findings.

  3. 3. Resolve work decisions

    Separate the technician’s decision about proceeding from customer consent to paid work. A driver or supervisor’s role alone does not establish buying authority; retain any explicit customer delegation.

  4. 4. Retain actual work and readings

    Record the work performed and attach its subsequent measurements. Where assessment stops at a worn component or unavailable reference, retain the limited outcome and referral instead of a completed-adjustment status.

  5. 5. Review and hand back

    The responsible technician records the outcome and unresolved findings. Send only accepted chargeable work to billing and record vehicle handback separately from payment.

Who uses the module, and who approves?

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

Service adviser

Owns the complaint, commissioning party and accepted scope; explains the recorded recommendation without changing technical findings.

Alignment technician

Retains the measurement context and determines the technical outcome. A change of technician needs the previous evidence preserved.

Bay coordinator

Records allocation and actual physical occupation without using a billing status to free the bay.

Accounts reviewer

Checks actual work and the applicable charge decision before creating the bill.

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.

No matching technical reference

Hold the proposed work for qualified review. Do not copy another model’s record or present an incomplete measurement as verified.

Worn component changes the scope

Record the finding and the technician’s decision. External repair and a later alignment visit require their own acceptance and evidence.

The same complaint returns

Create a linked visit with a new symptom and measurement record. Keep responsibility, remedial work and charging decisions open for review rather than assigning fault automatically.

Measurement sheet is missing

Identify which stage lacks evidence. Do not manufacture an initial value from the final sheet or close the record as fully documented.

Can this work independently?

The card can operate with entered vehicle and customer records and attached machine reports. Direct machine transfer requires verified compatibility. Estimates manage scope revisions; resource booking records allocation; invoicing creates financial documents. None of these functions chooses technical values or proves equipment readiness.

Systems and records it connects with

  • Estimate revisions: accepted check and addition references.
  • Bay booking: planned and actual machine occupation.
  • Machine evidence: manually attached reports or a verified supported transfer.
  • Invoice management: chargeable work and the responsible payer.

Configure, test and introduce the workflow.

  • Compare a check-only visit, accepted adjustment and outside-referral job against actual records.
  • Test a missing sheet, changed vehicle reference and technician handover before marking the record complete.
  • Trial a repeat complaint and fleet driver without buying authority; confirm that the original evidence and consent remain intact.

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.

  • A check-only visit closes without an invented adjustment entry.
  • The initial and final sheets link to the correct vehicle and visit.
  • Declined additions remain visible beside accepted work.
  • Technical outcome, physical handback and financial settlement remain separate.
Wheel alignment centres

How the business operates.

A driver brings a steering-pull complaint; the desk has a booking, but the bay needs the vehicle identity and the earlier readings. Alignment-centre software should connect the accepted check, machine record, technician findings and customer decision. A measurement is not permission to adjust or replace anything. This scope covers fixed-site centres handling vehicles within their declared equipment and staff capability. Balancing, tyre supply, suspension repair and specialist electronic calibration remain separately scoped work. The workflows below are requirements examples to adapt with the centre, not evidence of an installed system.

Reception and referral intake

Record the complaint in the customer’s words, vehicle details, referring garage and paying account. A referral does not tell the desk who can authorise extra work. Keep the person bringing the vehicle distinct from the person accepting the bill.

Alignment bay

Attach the relevant initial measurement and the vehicle specification reference selected by the qualified technician. Preserve the machine identity and the observed condition that limits work. The technician decides whether assessment, adjustment or referral is appropriate.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Vehicle identity, complaint and referring-party record
  • Accepted check or adjustment estimate and revision history
  • Machine and specification-reference record for the visit
  • Initial and subsequent readings with visit identity and technician

Operational bottlenecks to check

A coloured result becomes a repair order

The desk needs a clear boundary between a machine result, a technical recommendation and accepted paid work. A result alone does not explain every steering complaint.

A repeat visit loses its earlier evidence

Link the new visit to the earlier job while retaining its own date, complaint and readings. A changed condition or new tyre work must not be mistaken for the same measurement event.

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. Accept the visit

    Confirm the vehicle type and the requested check against the centre’s declared capability. Record who commissions the work and the account to charge before treating a garage referral as an accepted job.

  2. 2. Establish the measurement context

    The technician records the vehicle reference and relevant observations. Keep a quick-check result distinct from a completed alignment record. Missing or conflicting identity details require review before evidence is attached to the job.

  3. 3. Present the findings and scope

    Retain the proposed work and its price revision. A worn component or unavailable technical reference can lead to a limited assessment or outside referral. Customer consent does not replace the technician’s decision about proceeding.

  4. 4. Record what was actually done

    Link work entries and subsequent readings to the same visit. A check-only visit stays check-only. If additional work is accepted, record its revision and who authorised it; do not overwrite the original complaint.

  5. 5. Review, explain and reconcile

    The responsible technician records the outcome and unresolved findings. Hand the relevant evidence to the permitted customer contact. Send actual chargeable lines to accounts and release bay capacity only when physical use has ended.

Industry reports to connect with

  • Checks completed without adjustment, with stated outcomes
  • Jobs awaiting customer decisions or outside repair
  • Initial and subsequent readings missing a matching visit reference
  • Bay occupation and equipment-block exceptions

Questions before implementation.

When should wheel alignment centres consider job cards?

Use for fixed-site alignment centres that need to distinguish check-only visits, completed adjustments and referrals for other work. A tyre sale or general repair order is a separate scope. The centre accepts a vehicle for an alignment assessment or separately authorised work within its declared capability.

What should we bring to the requirements discussion?

Bring anonymised examples of Vehicle identifier, model details and customer-reported symptom; Commissioning customer, referring garage, payer and buying-authority record; Accepted assessment scope and chargeable additions; Technician-selected specification reference and machine identity; Initial findings and readings with their source visit. 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. Keep the steering complaint, accepted check, machine evidence and actual alignment outcome on the same vehicle visit. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

This module does not diagnose faults, operate alignment equipment, authorise repairs, certify roadworthiness or establish that a steering complaint has been resolved.

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. A check-only visit closes without an invented adjustment entry. 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