Job Cards for HVAC contractors
Keep the inspection, work, parts and status of a service job together.
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 job card records the unit, the fault found, gas added by weight and parts fitted. The customer signs on the technician’s phone. The card feeds the unit’s history and the invoice.
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.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
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.
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.
How the business operates.
The installation is one payment. The AMC is years of them, plus gas top-ups and a compressor that fails in its seventh summer. That second half is where records fall apart.
The records that hold the operation together.
- Customer sites and units. Keep each customer’s sites and the units at them. Every unit carries its model, capacity, serial number, installation date and service history, and outdoor and indoor units are paired, so a visit never starts from a guess.
- Enquiries and quotations. Log installation and service enquiries. Prepare quotations for units, piping, drain lines, electrical points and labour, and keep every revision. The accepted version becomes the job without retyping a single line.
- Installation jobs. Plan installation jobs by team and date, record units fitted and materials used, such as copper pipe, flare nuts, insulation and brackets. Close each job with a handover.
- Breakdown call desk. Log complaints from phone, WhatsApp and the website. Allocate each to a technician and follow it to closure, and repeat faults on the same unit are flagged, so a third visit gets a senior technician’s eye.
Operational bottlenecks to check
The last gas top-up is unknown
A customer reports poor cooling, and nobody can say when gas was last added, so it is charged again. The customer pays twice.
Preventive visits slip in summer
Breakdown calls take every technician, and quarterly visits slip a month without notice. The customer notices first.
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. Enquiry and quotation
An enquiry for a new installation or a service contract is logged against the customer. A quotation lists the units, piping, stands, drain lines, electrical points and labour, with tonnage and brand named for each room.
2. Installation
An accepted quotation becomes an installation job with a team and a date. Units installed are recorded against the site with serial numbers, and brazing checks, vacuum and leak test readings go on the handover sheet for the customer.
3. Contract and breakdown calls
Contract visits are scheduled for each unit. A breakdown call is logged, allocated to a technician and tracked to closure, so no complaint sits unassigned overnight, and the coordinator’s calendar shows both kinds of visit side by side.
4. Visit and job sheet
The technician records the fault, the readings, the work done, refrigerant gas added and parts fitted. The customer signs the job sheet on the phone before the technician leaves the site.
5. Billing
A tax invoice is raised for chargeable work. Otherwise the visit is marked as covered by a contract or a warranty, and the parts used are still charged to the right account for the contract review.
6. Renewal and follow-up
Contracts nearing their end and units due for service are listed, so customers can be contacted before the summer rush. Renewals are quoted from the same unit list, with the repairs of the year noted beside each unit.
Industry reports to connect with
- Visits completed by technician and by type, with the breakdown calls closed on first visit
- Contract visits due and visits missed, by unit and by site
- Contracts ending soon and renewals done
- Spare parts and refrigerant gas used by job, technician and vehicle
Questions before implementation.
When should hvac contractors 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.
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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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