Turn work-order information into a practical team review

WorkOrderPro product guide · Updated 12 September 2026.

What useful field service performance information provides

Field service performance information helps a manager understand work, identify exceptions and choose a practical improvement. A useful review connects the reported number with the jobs behind it. The manager should be able to explain what was counted, which period was used and why the result matters to the service operation.

WorkOrderPro includes work-order reporting, completed-work leaderboard calculations and an insight-review workflow. These provide different views of activity and outcomes. A count of completed jobs, a value associated with completed work and an insight requiring review should not be treated as interchangeable measures of technician quality.

Start with an operating question. You might want to understand why completed work is waiting for invoicing, why some jobs remain on hold or whether a preparation change helped comparable visits. Choose a measure that can inform that question and inspect representative underlying records. The goal is to make a better decision, rather than to produce a longer dashboard or rank every employee by one number.

Define completed work before comparing totals

A work order can move through several stages before and after physical attendance. A completed-work measure needs a clear status definition. WorkOrderPro's completed-work leaderboard uses jobs in completed or invoiced status. This recognises that moving a finished job into invoicing should not make it disappear from the underlying completed-work population.

Other screens can show individual status counts for operational queue management. A count labelled completed may therefore describe jobs currently in that status, while a broader completed-work comparison includes invoiced jobs as well. Read the meaning of the particular view before comparing two numbers or assuming that a difference is an error.

Use a small sample during evaluation. Complete a job, inspect the relevant view, then move it into the next supported commercial stage and inspect the result again. This makes the distinction tangible for the team. A metric should remain understandable as the job progresses, with the manager able to explain whether the view represents a current queue or a period outcome.

Use the period associated with the outcome

Time-period selection changes the question a report answers. Jobs created this month are a different group from jobs completed this month. A long-running job can belong to both groups in different periods. When comparing performance, establish whether the view uses creation, completion, invoice or payment timing.

The completed-work leaderboard uses the recorded actual completion time, with a historical delivered-time fallback in its calculation. This gives its period comparison an outcome-based reference. Do not assume that every dashboard tile or report uses the same date field. Inspect the definition of each view you intend to use in a recurring management discussion.

Avoid comparing a partial current period with a full previous period as though the two cover equivalent time. A quiet first few days of a month do not, by themselves, demonstrate a decline against the entire previous month. Use comparable windows or explain the partial coverage clearly. Better period discipline often improves interpretation more than adding another chart.

Understand technician attribution

The completed-work leaderboard groups relevant jobs by the assigned technician. This is different from attributing work to the person who originally created the record. An administrator can enter a request for a technician to perform, so creator-based counts would answer a different question about the office process.

Assignment-based reporting still needs context for crew work. A supporting technician can contribute substantially even when a job's primary assignment identifies another person. Review crew participation and time records before interpreting a primary-assignee total as a complete account of everyone's effort.

Keep assignments accurate as work changes. When a replacement person performs the visit, the work record should reflect the operational arrangement through the supported process. A report can only use the saved attribution it has. Reviewing who actually attended and who owns the recorded work helps the office interpret both individual and team results more fairly.

Separate completed value from collected cash

A value associated with completed work describes the amount attached to those jobs under the relevant calculation. It is not automatically cash received, profit or the technician's personal financial contribution. Materials, discounts, tax treatment, collection timing and other commercial factors can affect how the amount should be interpreted.

WorkOrderPro's completed-work leaderboard can sum job totals for the selected population and period. Use that figure as the defined work-value measure, then consult the appropriate invoice, payment and cost information for other questions. Avoid using a convenient revenue label to imply that all those financial stages have occurred.

For management discussion, state the measure in plain language. “Value of the completed jobs in this view” is easier to assess than an unexplained number called performance. When the team understands what the amount includes, it can ask a useful next question about work mix, charging or office closeout without assuming the figure proves profitability.

Compare like work where possible

A technician completing many short routine visits and another handling a smaller number of complex investigations can produce different counts while both serve the business well. Job mix matters. Before treating a leaderboard position as a judgement, inspect the kinds of assignments, access conditions and supporting responsibilities behind the result.

Look at comparable work over a useful period. Separate first assessments from planned repeat service where that distinction changes the effort involved. Consider whether the technician worked alone, assisted a colleague or waited for a customer decision. A raw total cannot explain these differences without the underlying job context.

Use operational queues to identify the next action

Current status counts can help the office recognise where work needs attention. Requested jobs need a reviewed next step, scheduled work needs readiness, and completed work may need commercial closeout. These are different queues with different owners. A single total of open work can conceal where the process is slowing down.

Choose a queue and inspect a few records. Is the next action clear? Does somebody own it? Is the status consistent with the notes? A job can be visible on a dashboard while still lacking a usable handover. The practical improvement may be a better access question or a clearer approval follow-up, rather than asking technicians to move statuses faster.

Review queues at a cadence that fits the operation. Dispatch may need a daily view, while a manager may review recurring patterns over a longer period. Keep the purpose of each review clear so staff do not spend time reproducing the same numbers for several meetings without making a decision from them.

Treat an insight as a review prompt

WorkOrderPro's insight workflow supports filtering by type, severity, status and technician, with active insights shown by default. An insight can be acknowledged and later resolved. These actions provide a way to organise attention, but they do not establish that the underlying interpretation is automatically correct or that a problem has been fixed merely because its status changed.

Before accepting an insight, inspect the description, source data and relevant work records. Ask whether the metric definition fits the service question and whether the sample is sufficient. An automatically generated explanation should be treated as a starting point for review, especially where work mix or missing information may change its meaning.

Acknowledge an item when the appropriate person has taken responsibility for investigating it. Resolve it when the review and intended action have a clear outcome under your operating process. Keep the distinction between reading a prompt, understanding its cause and improving the work. That gives the insight list a practical role beyond becoming another collection of unattended alerts.

Keep automated narratives grounded in evidence

A generated narrative can help summarise a pattern, but the wording does not add evidence that was absent from the source records. A confident sentence about a technician's performance still needs the underlying metric, period and attribution to be appropriate. Managers should review the explanation with the same care as a manually written report.

Do not assume that an insight proves causation. A lower total can coincide with leave, different assignments, a changed customer mix or incomplete data. The appropriate next step may be to inspect those conditions and speak with the technician, rather than immediately prescribing coaching or drawing a conclusion about effort.

During evaluation, ask the reviewer to explain one insight without relying on its headline. They should identify the source records and the question the result raises. If the statement cannot be checked against understandable work information, it should not be the basis for a consequential personnel decision. Useful automation supports judgement rather than replacing the need to understand the work.

Review record quality before comparing people

Reports depend on the records that feed them. Missing completion times, stale assignments or unclear outcomes can affect the interpretation of otherwise sensible calculations. Establish a small set of source-quality checks before using performance comparisons as a regular management tool.

Start with completed jobs. Confirm the recorded outcome, primary assignment and relevant dates. Then inspect whether the notes explain the work well enough to understand unusual duration or value. A manager who can follow the job story is better placed to distinguish a service problem from a data-entry problem.

Use repeated quality issues to improve the workflow. If completion is recorded long after the visit, clarify the departure routine. If assignments are rarely updated when crews change, improve the dispatch handover. Correcting the source process benefits customer service and reporting together, rather than creating a separate reporting cleanup that happens after the useful context has been forgotten.

Make coaching specific to an observed task

A useful coaching discussion concerns a behaviour or handover that the employee can recognise and improve. Instead of telling someone to raise their performance score, review a concrete example: an assessment note that left the office unable to prepare a quote, an unresolved timer or an access instruction that was missing from the brief.

Ask for the technician's explanation before choosing the action. They may identify a preparation problem, an unclear screen or a responsibility that the report does not show. Agree one practical change and the circumstances in which it should be used. This gives the next review a concrete question to assess.

Do not use a leaderboard as a complete appraisal. Counts and values can support a conversation about work, but quality, competence, collaboration and customer context require broader evidence. The most useful performance system helps managers ask better questions and support consistent work, rather than encouraging staff to optimise a visible number at the expense of the customer outcome.

Connect service timing with the actual workflow

SLA tracking provides a different lens on response and resolution. Its rules use defined timestamps and recorded hold treatment. A timing exception can help the manager identify delayed work, but the underlying sequence is needed to explain why the threshold was exceeded.

For example, assessment may have been prompt while further work waited for a customer decision. Another job may have remained unassigned too long before attendance. Both can affect overall resolution, but the appropriate improvement differs. Read the rule definition and job history before comparing the results.

Bring the timing review back to a named operational action. Who will contact the customer, arrange the next visit or resolve the dependency? A performance discussion that ends with a chart but no responsibility is unlikely to change the service process. The record should help the team act, then provide context for reviewing the result later.

Run a weekly review that ends with a decision

Choose a short agenda with a few parallel questions: what completed, what remains blocked and which recurring issue deserves attention? Use the available views to locate records, then inspect enough detail to understand the pattern. Resist adding every possible metric to the meeting simply because the system can display it.

Keep a short record of the decision in your normal management process. The next review should be able to distinguish an unresolved action from a new issue. This turns reporting into a repeatable improvement routine rather than a weekly rediscovery of the same concerns.

Evaluate reporting with known sample jobs

Create a few representative trial jobs with clear assignments and outcomes. Include a job entered by an administrator but completed by a technician, a crew visit and work spanning two reporting periods. Inspect the relevant completed-work view and explain where each job appears.

Then change a supported status or complete a job in the next period and review the effect. The purpose is to understand the calculation boundary before using it in a real management conversation. Include a current-queue view so staff can see why a status count may differ from an outcome-based total.

For the insight workflow, inspect filtering and the acknowledge or resolve actions with an appropriate sample. Confirm who is expected to review each item and what constitutes resolution in your operating process. A useful trial demonstrates both the reported information and the decisions the team can make from it.

Choose measures that support the service you want to deliver

Start with a small set of measures whose definitions the team can explain. Add another only when it answers a distinct operating question. A completed-work view, a clear exception review and a reliable closeout routine may provide more practical value than a large collection of loosely interpreted scores.

Review current pricing and confirm the reporting and insight features in the plan you intend to use. Staff billing includes active administrators, dispatchers and field users, with disabled accounts excluded. Include the people who maintain the source records and those responsible for acting on the results.

Start a trial with representative work and a real management question. Judge the outcome by whether a colleague can explain the measure, trace it to the jobs and choose a useful next action. That is a stronger foundation for team improvement than assuming a high score automatically proves good service.

For a new manager, begin with one completed job and follow it through the relevant report. Ask them to explain the period, assignment and value in their own words. This makes the interpretation observable and gives the team a simple way to identify misunderstandings before the numbers become part of a recurring performance conversation.