Skip to main content
GullySystem
Other industries

Job Cards for Equipment rental companies

Keep the inspection, work, parts and status of a service job together.

Field Service

Does this function belong in your operation?

Use when service or repair work needs a record beyond an appointment.

A repair or field-service request is accepted.

A repair or service on a machine is a job card with parts, labour and hours. The workshop sees which units are due before the next hire. Cards link to the asset record.

Bring the records the workflow depends on.

  • Customer and asset details
  • Reported issue
  • Work and parts approval rules

Outputs to check

  • Service job and inspection record
  • Approved parts and labour statement
  • Completion and billing handoff

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 service job

    Capture the customer, asset and reported issue.

  2. 2. Inspect and estimate

    Record findings and proposed work before chargeable changes.

  3. 3. Obtain approval

    Retain the customer's or authorised manager's decision.

  4. 4. Perform the work

    Record labour, parts, tests and unresolved findings.

  5. 5. Close and hand over

    Issue completion evidence and send approved billing inputs to accounts.

Who uses the module, and who approves?

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

Service advisor

Opens the card, builds the estimate, records approval and tells the customer where their machine stands.

Technician

Reads the complaints and inspection notes, and sees the parts issued to their job.

Storekeeper

Issues against a card number and not to a name shouted from the bay.

Accounts assistant

Bills from the card line for line, and records what was paid.

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.

Extra repair discovered

Record the finding and obtain approval before adding chargeable work.

Part unavailable

Keep the job waiting with the required item identified.

Customer declines work

Record what was inspected, what was refused and the authorised closing outcome.

Can this work independently?

Job cards can run with entered customer and asset records. Scheduling assigns staff, stock controls parts, and invoicing creates the bill from approved work. Closing a technical job should be distinguishable from financial settlement or customer acceptance where those occur later.

Systems and records it connects with

  • Estimates and quotations: Approved estimate lines, revisions and acceptance references.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Spare-parts stock: Item-location quantities and authorised stock movements.
  • Technician scheduling: Assigned field jobs and technician availability.

Configure, test and introduce the workflow.

  • We trace a vehicle from gate to delivery. You show us today’s slips, and we return the card layout we propose.
  • Stages and who may change them are agreed. A chart on a page is yours to approve. The parts list and labour rates are loaded. Storekeepers test issuing against dummy cards.
  • Cards run alongside paper for a stretch. Differences are discussed with advisors and technicians. Cards become the only record. The workshop team gets a short practice on phones.

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.

  • Parts usage links to the job.
  • Unapproved additional work remains flagged.
  • Completion retains the service record.
Equipment rental companies

How the business operates.

A rental company earns only while its machines are on hire and working. Between one site and the next, a unit has to be collected, washed, inspected, greased and made ready again. Each idle day costs money. Nobody sees it.

Equipment register and availability

Hold each machine with its serial number, attachments, yard location and status. See what is free, reserved, on hire or in the workshop for any dates asked.

Quotations and rental contracts

Quote from rate cards by day, week or month, add operators, haulage and bonds, and turn the accepted quote into a contract that lists every unit and attachment.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and customers. Record each enquiry with its source, dates and site. Customer files hold contacts, credit terms, site addresses and earlier contracts together, so the counter sees the history before it quotes a repeat hirer.
  • Equipment register. Hold each machine with its serial number, class, attachments, location, status, purchase details and hire history. Tracked excavators, trailers and tower lights each sit in their own class. Each unit keeps one record.
  • Availability calendar. See which machines are free, reserved, on hire or on the workshop ramp for any dates. Move a booking without losing the record, and see the clash before a second hirer is promised the same scissor lift.
  • Quotations and rate cards. Build quotations from your own rate cards by day, week, month or hour, with operator, transport, diesel, insurance and deposit lines. Revisions are kept.

Operational bottlenecks to check

Availability is held in someone’s head

Two customers are promised the same telehandler for the same week. Nobody finds out until two trucks wait at a yard that holds one unit. Someone loses the job.

Condition at return is argued

A bucket tooth is missing or a mudguard is dented. Without a signed check at delivery and another at off-hire, the charge becomes a negotiation.

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. Enquiry

    Someone rings, emails or walks up to the counter wanting a machine. The request is logged with the dates, the site, the class of equipment and any attachments wanted, such as a hydraulic breaker or a trench box.

  2. 2. Availability and quotation

    The counter checks what is free for those dates and builds a quotation from the rate card, with operator, low-loader transport, fuel and deposit lines where they apply.

  3. 3. Contract and dispatch

    Once the quotation is accepted it turns into a hire contract naming every unit and attachment. A driver and a tipper, flatbed or low-loader are assigned for the delivery date.

  4. 4. On hire

    Hour meter readings, extensions, swaps and site contacts are recorded while the machine is out. The office sees which contracts end this week and which units are due a greasing visit.

  5. 5. Return and inspection

    The yard checks the machine against the delivery photographs, reads the hour meter, notes damage and diesel level, and passes it to the workshop if it needs work. It is pressure-washed first.

  6. 6. Billing and release

    The contract, its extensions and any charges feed the invoice. The deposit is settled. The machine goes back to the available list only when the workshop marks it ready.

Industry reports to connect with

  • Utilisation and idle days by machine and class
  • Earnings by machine, customer and branch
  • Contracts due back and overdue returns
  • Servicing due by hours or by date

Questions before implementation.

When should equipment rental companies consider job cards?

Use when service or repair work needs a record beyond an appointment. A repair or field-service request is accepted.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer and asset details; Reported issue; Work and parts approval rules. 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 inspection, work, parts and status of a service job together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A job card records work and does not itself certify repair quality or equipment safety.

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. Parts usage links to the job. 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