Record job time and give labour review a clear starting point

WorkOrderPro product guide · Updated 12 September 2026.

What job time tracking should tell the office

Technician time tracking connects a person, a work order and a recorded working interval. Its first purpose is to make the time spent on a particular job understandable. An appointment tells you when attendance was planned. A clock entry tells you when someone recorded the start and end of their work. An invoice tells you what the customer is charged. Those records answer different questions, even when they refer to the same visit.

WorkOrderPro records clock entries against assigned technicians and work orders. The current service checks assignment before starting an entry, prevents a technician from opening another entry while one is active, and records the closing timestamp when the technician clocks out. Completed entries provide duration information. This creates a useful starting point for labour review without asking the office to reconstruct every visit from messages at the end of the week.

The strongest operating habit is straightforward: use the correct job, start the record at the agreed working boundary, close it when that interval ends, and review exceptions promptly. The quality of the habit matters as much as the presence of a timer. A running clock on the wrong job is still the wrong record.

Establish what your business means by job time

Before introducing a timer, decide when the recorded interval should start. One company may begin when the technician starts work at the site. Another may need to distinguish preparation, travel and attendance in its wider process. Write the definition in language that a new employee can follow. Avoid a rule that depends on knowing what the owner usually meant on a previous job.

Explain the ending boundary with equal care. Finishing the physical task, packing equipment, completing the customer handover and leaving the property can happen at different times. Your chosen convention should match the question you want the records to answer. If you want to understand total attendance effort, recording only tool use leaves useful work invisible. If the customer agreement covers a specific charging basis, do not quietly substitute a different definition.

Use a short example during onboarding. A technician arrives, waits for access, completes the repair, discusses the result and leaves. Ask where the record starts and stops under your policy. Resolve disagreements before interpreting the first report. The aim is consistency across people and visits, rather than a false appearance of precision.

Start with the assigned work order

The current clock-in service checks whether the user is the primary assigned technician or belongs to the job's assigned crew. That connection helps keep a time entry attached to real operational responsibility. If somebody cannot start a record because they are not assigned, the office should inspect the assignment. A shared login or a timer against a different job would hide the underlying scheduling problem.

Before attendance, confirm the customer, site, job reference and attending people. Similar addresses or repeat customer names make a reference particularly useful. On a busy day, the technician should be able to recognise the current job without opening several unrelated records. The dispatch board and the field brief should describe the same allocation.

For a replacement technician, update the actual working arrangement through the authorised office process. Do not leave the original employee looking responsible for an interval worked by someone else. Clear assignments make later review easier, especially when a second person joins partway through a visit or a supervisor assists with diagnosis.

Use one open entry per technician

WorkOrderPro's time service rejects a new clock-in if the technician already has an open entry. This makes an unfinished previous interval visible instead of silently allowing overlapping job timers. When that happens, inspect the earlier work order and establish what actually occurred. Starting another record through a different account would turn a visible exception into a more difficult reporting problem.

The practical discipline is to close the first interval before moving into the next tracked job. Include that action in the technician's departure routine alongside work notes and the next instruction. If the working day is interrupted, confirm which record remains open. A timer that continues through an unrelated visit can substantially distort the interpretation of both jobs.

An open entry is also a useful review prompt. It may reflect work still happening, a missed action or a technical issue. Do not assume which explanation applies from elapsed time alone. Contact the responsible person through the usual operating channel, establish the facts and use the appropriate correction process. Keep the explanation understandable to the person reviewing labour later.

Understand the recorded timestamps

The current clock-in and clock-out service records server time when the action is accepted. This page does not promise that a disconnected device captures an exact offline clock action for later submission. During your trial, demonstrate the time workflow on the devices and connections your technicians actually use. A successful screen tap and a saved server record should be checked as separate observations.

If the connection is unavailable, follow a clear fallback procedure for noting the actual event and informing the office. Do not repeatedly tap an uncertain action without inspecting the result when service returns. An unresolved timer should remain an operational exception until the saved record is understood. This protects the usefulness of your records without asking technicians to guess what the software accepted.

South African field teams often work across sites with uneven reception. A useful acceptance exercise therefore includes leaving a good connection, attempting the relevant action and inspecting the recovered state. Describe the observed behaviour in your internal instructions. General mobile access does not establish that every time action has the same offline behaviour as notes or photographs.

Separate elapsed time, crew effort and invoice quantity

A two-person visit lasting two hours represents two hours of elapsed attendance and potentially four person-hours of recorded effort. A customer may nevertheless have agreed a fixed repair price. These quantities should not be used interchangeably. Job time helps explain labour consumption, while the invoice must reflect the accepted commercial arrangement and any properly agreed change.

WorkOrderPro sums completed time-entry durations for the job-time total. Read that figure in the context of the crew and the entry boundaries. If one person arrived later, their interval should differ from the lead technician's. If a specialist attended briefly, that contribution should be understood separately from the length of the overall appointment.

Make multi-technician visits readable

Assign each participating technician through the relevant job allocation. Each person then records their own interval. This is more informative than asking the lead technician to run one clock as a proxy for the entire crew. A shared interval conceals late arrival, early departure and short periods of specialist support, all of which can matter when planning similar work.

For example, a lead technician may assess a fault before a second person arrives with a required component. The final job record should make the distinction clear: diagnosis happened first, the additional person contributed later, and both may have helped with the final check. Time records become more useful when the work notes explain the sequence rather than merely listing an undifferentiated total.

At review, look for incomplete entries belonging to any crew member. A job can appear finished while one person's timer remains open. Give the office a named reviewer for these exceptions so responsibility does not disappear between dispatch and accounts. The purpose is a coherent account of the visit, not ranking technicians by the shortest recorded duration.

Handle waiting and interruptions consistently

A technician can lose working time while waiting for a keyholder, an isolated area, a component or a customer decision. These interruptions deserve an explanation even when your current workflow does not provide a separate timer category for each cause. A short factual note can prevent the office from assuming that every minute represented active repair work.

Do not invent a break button or an automated travel classification in your internal training unless you have demonstrated it in the current interface. The time model's ability to hold break or billable data is not, by itself, proof of a complete employee-facing workflow. Start with the controls the team can actually use and define how exceptions reach the reviewer.

When assessing a long visit, ask what constrained progress. A waiting period caused by missing access may suggest a better booking question. Repeated delays while obtaining components may suggest improved preparation. Time tracking is most constructive when it directs attention to fixable causes. A raw duration cannot establish whether a technician worked effectively or whether the customer should be charged for every interval.

Review labour before preparing the invoice

Bring the completed time record together with the accepted quote, work notes, materials and any agreed variation. This is the point to explain a difference between planned and actual effort. If the customer approved a fixed amount, a longer visit does not automatically authorise a larger charge. If the arrangement is time based, the reviewer still needs the correct rate and charging convention.

The current feature should be evaluated as a source of job-time information. Do not assume that clocking out creates an invoice line or chooses a rate automatically. Demonstrate the actual invoice preparation path and identify which decisions remain with the office. That separation helps avoid presenting internal labour consumption as an unexplained customer charge.

Use readable descriptions when preparing customer documents. A customer usually needs to understand what was done and the agreed basis for the amount. An internal timer identifier will not explain the repair. The quote builder guide covers scope and approval, while job photos explains how visual records can support the work narrative.

Keep job tracking separate from payroll assumptions

A record of time on a work order is not automatically a complete attendance or payroll record. A working day can include training, meetings, preparation, travel and other activity outside a tracked customer job. Treat job hours as the measure they are designed to provide. Your employment and payroll processes need their own reviewed rules and appropriate professional advice where required.

Avoid copying a job total into payroll without understanding what was included and omitted. The technician may have worked on several jobs, completed untracked tasks or experienced an unresolved clock exception. Equally, a timer left open after the visit can overstate the recorded interval. Neither situation is solved by assuming that every minute in a job record represents the same payroll category.

For operational reporting, explain the coverage of the measure beside the result. A weekly total of completed job intervals can be useful for planning, provided the reader knows it excludes other work. Clear definitions build confidence in reports and reduce disputes about what a number was supposed to represent.

Build a short daily exception review

Review time exceptions while the people involved still remember the visit. Waiting until month end makes a missed clock-out harder to reconstruct. A practical daily check looks for open entries, unexpected durations and jobs whose assignment changed. It should take place alongside the normal review of unfinished work rather than becoming an unrelated administrative exercise.

Keep the review factual. The goal is to improve the job record and the next day's process. If the same problem keeps appearing, change the instruction, screen understanding or handover that causes it. Repeated reminders without a clear working boundary tend to produce the same exception again.

Run a realistic time-tracking trial

Use a small set of representative jobs: a short single-person visit, a longer crew visit and an interruption requiring office attention. Assign the people, start and stop the entries, and inspect the saved durations from the office view. Ask a colleague who did not attend to explain the labour record using the work order and notes.

Include a deliberate unfinished timer and an attempted second clock-in. The team should understand the rejection and know how to investigate it. Also test the connection conditions that matter for your operating area. These exercises are more informative than repeatedly timing a perfect demonstration job on a reliable office connection.

Agree the decision criteria before the trial. Can technicians identify the correct job? Can the office find incomplete entries? Can a reviewer separate crew effort from customer charges? Record where the workflow succeeds and where it needs a clear operating step. A small, well-understood trial gives a stronger purchasing basis than an impressive total of unreviewed time entries.

Use duration evidence to improve planning

Once entries are consistent, compare similar work with care. Separate a routine visit from a first diagnosis, a repeat attendance or a job with difficult access. A single overall average can obscure those differences. Read the underlying work notes before deciding that the schedule needs a longer appointment or that a quoted allowance is unrealistic.

Choose one practical improvement at a time. You might add an access question to booking, prepare a commonly required component or allow more handover time for a particular type of customer. Then inspect later comparable jobs to see whether the explanation and scheduling become more reliable. Do not treat a small sample as proof of a guaranteed financial return.

Useful time tracking should help the team discuss work with less guesswork. It becomes more valuable when the customer, assignment, interval and outcome agree. Start a WorkOrderPro trial with that complete workflow, and review current pricing for active administrators, dispatchers and field users. Disabled accounts are excluded from the active-user count. Choose the subscription around the people who need to operate the process, not only those holding tools.

Give new technicians a repeatable first-day routine

During the first supervised visit, ask the new technician to identify the customer and work order before touching the timer. Have them explain the start boundary in their own words. After the work interval, let them close the entry and locate the saved result. This makes the training observable: the supervisor can see whether the person understands the record rather than relying on a general statement that the app is easy to use.

Repeat the exercise with a different job so recognition does not depend on remembering one demonstration screen. Include the handover to the office reviewer. A technician who knows where the record goes and why the interval matters is better placed to flag an error promptly. Explain who to contact when an assignment is missing, an old timer remains open or a connection problem leaves the saved state uncertain.

Keep the written instruction short enough to consult during an actual working day. Include the start rule, end rule, correct-job check and exception contact. Store more detailed commercial and reporting guidance with the office process. This division gives each person the instruction needed for their responsibility while preserving a shared definition of job time across the business.