A useful job card tells the next person what was requested, where the work belongs, who is responsible and what happened during the visit. It can begin as a printed sheet or a digital record. The important part is that the instruction, field notes and office handover stay connected. Start with a clear customer and site, describe the reported problem, assign the work, record the outcome and identify the next action.
This guide explains how to build that record for a trade or service business. It includes a practical field list, a worked example and a review process you can use with the free PDF and Excel job card templates. The example is illustrative and does not describe an actual customer. A job card supports operational documentation; it does not automatically establish the quality of a repair, guarantee payment or replace other documents your work may require.
Decide what the job card needs to communicate
Before choosing a form, identify the people who will use it. The dispatcher needs enough information to prepare the visit. The technician needs the current instruction and access details. The office needs an understandable account of the work, materials and unresolved questions. The customer may need a copy of the agreed scope or visit outcome. These needs overlap, but the same information is not necessarily suitable for every audience.
A practical test is to give an unfamiliar staff member a completed example. Ask them to explain the original request, the work performed and the next action. If they need to telephone the technician to interpret an abbreviation or identify the site, improve that part of the record. A form with many fields can still be unclear, while a concise form with specific descriptions can support a reliable handover.
Choose consistent terminology. If your office calls the record a work order and technicians call it a job card, explain that both refer to the same job. Keep one identifiable number across related notes, photos and documents. Avoid creating a second unrelated reference each time the work changes hands, because that makes later retrieval and reconciliation harder.
Capture the customer and the actual job site
Record the customer or account holder separately from the place where the work will happen. A landlord, property manager or business customer may have several sites. The billing contact may also be different from the person who can provide access. Confirm the site address and relevant contact details when preparing the job, rather than assuming that the address on the customer account is the destination.
Access instructions should help the technician arrive prepared. Useful examples include the correct entrance, an appointment window, a building contact and any customer procedure that must be followed. Handle access codes and other sensitive information through the appropriate restricted process for your business. Do not place unnecessary personal information on a copy that will be distributed widely.
When a customer changes the location, update the job instruction and make the change visible to the assigned person. A note in an unrelated message thread can be missed. During a paper-based process, mark the revised copy clearly and ensure the older instruction is no longer being used. With software, confirm that the technician can see the current site information before travelling.
Write the reported problem before the diagnosis
Start with what the customer reported. “The kitchen sink is draining slowly” is a report. “The outside pipe needs replacement” may be a diagnosis that has not yet been established. Keeping those statements separate helps the technician understand the problem without treating an assumption as an authorised repair instruction.
Include the details that make the report specific: where the issue occurs, when it was noticed, whether it is intermittent and what the customer has already observed. Record relevant limitations too. If the customer cannot identify the equipment model, say that the model still needs to be checked. An empty field can be mistaken for an oversight, while an explicit unknown tells the technician what to confirm.
After assessment, add the technician's findings in a separate note. Preserve the original report so the office can understand how the work developed. If the findings change the proposed scope or price, identify the approval needed before proceeding. A technical recommendation in a note is not the same as customer approval of additional work.
Use a field list that fits the handover
The following fields form a practical starting point. Adapt them to the operation, and distinguish required information from information that becomes available later. For example, the request may be complete enough to schedule even though the exact materials will only be known after assessment.
| Part of the record | Information to capture | Why the next person needs it |
|---|---|---|
| Reference | Unique job number and request date | Connect the instruction, evidence and documents |
| Customer | Account holder and relevant contact | Identify who requested the service |
| Site | Actual service address and site contact | Prepare the correct visit |
| Request | Reported problem and known context | Understand the customer's need |
| Assignment | Responsible technician and appointment | Establish ownership and timing |
| Scope | Agreed tasks, exclusions and approvals | Distinguish authorised work from recommendations |
| Visit | Arrival, work notes and relevant time records | Explain what happened on site |
| Services and materials | Description, quantity and pricing basis | Support review of billable work |
| Evidence | Relevant photos, notes and acknowledgements | Add context to the completion record |
| Outcome | Completed work, limitations and next action | Support invoicing, return visits or follow-up |
For paper, leave enough writing space for descriptions instead of shrinking every field into a narrow box. For a digital form, use structured fields where they support consistent decisions and free text where the situation needs explanation. A dropdown can make status consistent, but it should not prevent the technician from explaining why the job is waiting.
Record services, parts and time clearly
Describe the work in a way the office and customer can understand. A catalogue entry can make frequently used services consistent, but it should still match the actual scope. Check whether a standard price includes a callout, a defined amount of labour or particular materials. If the scope differs, record that difference explicitly rather than relying on an informal convention known only to one employee.
For materials, record the description and quantity used or supplied. Where a part reference matters for a return visit, preserve that identifier. Separate materials used from materials recommended for future work. A replacement discussed with the customer but not installed should not appear as completed work simply because it was entered into a draft line.
Time records and charges also need clear interpretation. The elapsed time between arrival and departure may include waiting, assessment or access delays. Your commercial agreement determines how the work is charged. Do not assume that every minute recorded by a timer becomes an invoice line automatically. Review the relevant labour or service lines and any customer-approved variation before issuing a document.
Follow a status process that reflects the work
Use status to describe a meaningful operational milestone. A newly received request may need assessment or scheduling. A draft quote needs internal preparation, and a sent quote is waiting for a customer decision. An approved scope can then move into the visit workflow. Keep these commercial and operational decisions understandable instead of treating every record as the same kind of job from the outset.
In a visit workflow, scheduled means that the job has been planned. Dispatched indicates movement towards the visit, on site indicates arrival, and in progress indicates that work has started. Completion records the outcome of the work. Invoicing and payment are separate commercial milestones. An invoice being issued does not prove that its balance has been settled.
Exceptions need a next action. If access is unavailable, record that situation and who will arrange another appointment. If a part is missing, identify what is required and who is following it up. If a job is paused, record the reason and review it deliberately. The exact timing treatment depends on the system and rule configuration; a status label alone does not establish compliance with a customer service agreement.
Work through an illustrative job card
Consider a small maintenance business responding to a slow-draining kitchen sink. The office creates reference JC-2026-0142, records the customer and the service address, and notes that the site contact is available during the agreed morning appointment. The request describes the reported symptom without assuming a cause. The assigned technician can now identify where to go and what needs assessment.
At the visit, the technician records arrival and the relevant findings. Suppose the agreed work can be completed within the original scope. The job notes describe the action performed, the service or material lines used and the outcome of the technician's checks. This is a documentation example, not an instruction for performing a repair. Any technical work must follow the competence and procedures appropriate to the task.
The completion note also records an unrelated observation that may need a later visit. That observation is clearly marked as a recommendation, not as work already performed or charged. If the customer is available, the relevant acknowledgement can be recorded with the person's name. If they are unavailable, the record states that fact and identifies the office follow-up rather than inventing a signature.
The office then reviews the agreed scope, recorded work and billable lines. Any uncertainty is resolved before invoice preparation. The job reference connects the visit record to the invoice, while the payment record shows whether the invoice has subsequently been settled. Another staff member can follow this sequence without needing to reconstruct a collection of separate messages.
Add evidence without overstating what it proves
Relevant photos can support a job record by showing the condition observed, the location of the work or a particular result. Add a short description so someone reviewing the image later understands its purpose. A photograph of a component does not necessarily identify which property it belongs to or explain whether the image was taken before or after the work.
Preserve the difference between customer-supplied images and technician evidence. A request photo may help prepare the visit, but it does not establish what the technician encountered on arrival. Similarly, a timestamp or location field adds context without proving every aspect of quality or responsibility. GPS availability and accuracy depend on the device, permissions and conditions; do not assume every photograph carries reliable location information.
A signature or acknowledgement should have a clear purpose in your procedure. Record who signed and what they were acknowledging. If there is a disagreement, document the actual issue and follow the appropriate review process. Avoid claiming that a digital signature, file hash or photograph makes a record tamper-proof or guarantees an outcome in a dispute.
Review the job before sending it to the office
A short completion review can prevent avoidable follow-up. Ask the technician to check that the correct customer and site are attached, the work description is understandable, and the services or materials match what happened. The review should also identify incomplete work and missing approvals. A completed-looking form with an unresolved variation can create more confusion than a clearly paused job.
| Review question | Example of a gap | Useful correction |
|---|---|---|
| Is this the correct site? | Customer has several properties | Confirm the actual service address |
| Is the work understandable? | Note says only “done” | Describe the task and observed outcome |
| Are quantities clear? | Material listed without quantity | Record what was actually used or supplied |
| Is additional work authorised? | Extra item appears only in notes | Link the approval or hold for review |
| Is any work outstanding? | Return visit mentioned without owner | Record the next action and responsible person |
| Is the handover complete? | Photos remain unsent on a device | Confirm required uploads before relying on them |
Make one person responsible for checking the handover. In a small team this may be the owner; in a larger operation it may be a dispatcher or office reviewer. The responsibility matters more than the job title. If a record needs clarification, keep the question connected to the original job so the answer is available to the next reviewer too.
Choose paper, PDF, Excel or software deliberately
A printed form is useful when you need a simple structure that can be completed on site. A fillable PDF provides a consistent layout that can be saved and shared. A spreadsheet can help organise line items and calculations. Each format still needs a process for naming files, protecting access, retaining the original record and ensuring that the office receives the current version.
The template resource provides actual PDF and Excel downloads with format-specific instructions. Test the file in the application your team will use and save a sample before distributing it. Do not assume that every browser or mobile viewer handles editable PDF fields in the same way. Check the saved copy and any printed output, especially where information is entered into a limited space.
Software becomes worth evaluating when assignment, shared status, evidence and the invoice handover are difficult to coordinate manually. There is no universal technician-count threshold at which paper stops working. Look at your actual process: missing records, repeated clarification calls, version confusion and delayed review. Those observations provide a more useful basis for a decision than an unsupported promise of a fixed number of minutes saved.
Test the digital process with one representative job
Start with one customer, the correct site and a service your team understands. Create the request, assign the visit and record the work through the intended mobile workflow. Have the office review the result and prepare the appropriate next action. The point is to test the handover between people, not simply to populate a dashboard with imported records.
Include an ordinary complication such as a changed appointment or an unavailable customer. Review the mobile guide and test the actions your team requires under the connectivity conditions it expects. Treat queued changes as pending until synchronisation succeeds. A note being available offline does not prove that an associated upload, approval or status change has reached the shared record.
When the process works for the sample, bring across a small, checked group of customer and service records. Establish naming conventions, confirm active team access and identify who reviews completed work. Expand gradually enough to resolve missing information before it becomes a repeated problem. Use WorkOrderPro pricing to check the selected plan and active-user cost once the workflow has been demonstrated.
Frequently asked questions
Does a job card satisfy every documentation requirement?
No. Treat it as an operational record and verify the requirements that apply to your transaction and trade. Section 26 of the Consumer Protection Act addresses transaction records, with specified information and exceptions. A generic template should not be presented as automatic compliance or a replacement for a required certificate, invoice or specialist record.
What number format should a paper job card use?
Choose a unique, consistent sequence that your office can retrieve, such as JC-2026-0142. The exact pattern matters less than avoiding duplicates and keeping the reference on related documents. If software generates the number, use that reference consistently rather than maintaining a competing manual sequence for the same job.
What should happen if the customer cannot sign?
Record that the customer was unavailable and identify the next action under your procedure. Do not sign on their behalf or imply an acknowledgement that did not occur. If another person acknowledges the visit, record their name and capacity accurately. Completion, acknowledgement and payment should remain distinct facts.
Can a photo of a paper job card be retained digitally?
A legible image can support retrieval, provided the relevant information is captured clearly and associated with the correct job. Check that pages and signatures are not cut off. Decide how the original is retained and who can access the digital copy. A photograph alone does not guarantee authenticity or replace your record-management process.
How much detail belongs in the problem description?
Include enough context for another person to prepare the visit and distinguish this request from a similar one. Identify the location of the problem, the symptom and relevant timing. Keep the customer's report separate from the technician's findings. Add specialist detail when it is known and useful, and mark unknown information honestly.
Should the job card include prices?
Include the commercial detail needed by the people using the record, with a clear distinction between proposed and approved work. Some businesses use a separate quote alongside the field record. The office should be able to trace billable lines to the agreed scope and work performed without assuming that every recommendation was accepted.
Does completing the job create an invoice automatically?
That depends on the workflow and configuration you use. Completion should trigger an office review appropriate to your operation. Confirm how invoice generation works in your chosen setup and check the resulting document. Do not assume that work completion also records payment or resolves every outstanding commercial question.
What is the best first step for an inconsistent team process?
Choose one representative job and agree on the information each person needs at the handover. Use the template or a trial record to walk through it together. Identify missing details, unclear ownership and duplicated entry, then adjust the process before importing the rest of your data. A shared example is easier to teach than a long list of abstract rules.