Electrical
Field service work order management for electrical contractors
The work order is the one record of a job from the call to the cash. Capture it in the field, authorize the scope, track the status, and invoice straight from it.
Direct answer
A work order is the single record of one job from the first call to final payment: the customer and site, the problem, the equipment, the authorized scope, the findings, the work done, parts, labor, photos, and the signature. Manage it well and nothing falls through. Manage it badly and you lose hours to missing info and unbilled work.
Key takeaways
- A work order is the single record of one job from the first call to final payment: customer, site, problem, scope, findings, work, parts, labor, photos, signature.
- The work order lifecycle is create, schedule and dispatch, perform, document, invoice, close; money does not move until document and invoice are done.
- Record reported problem and findings as separate fields; if it is not on the work order, it did not happen and cannot be billed.
- Authorize the scope and price before doing work beyond the report, and write a signed change order when scope grows mid-job.
- On commercial jobs capture the PO number up front and stop at the not-to-exceed (NTE); first-time fix rate references around 80 percent.
What a work order is, and why managing it runs the company
A work order is the one record that follows a job from the call that started it to the money that ends it. Who called, where the site is, what the problem was, what you were authorized to do, what you found when you got there, what you actually did, the parts you used, the hours you spent, the photos that prove it, and the signature that accepts it. One job, one record, start to finish.
Manage that record well and nothing falls through the cracks. The tech shows up with the history, the scope is agreed before a wrench turns, the parts and time land on the ticket while the truck is still on site, and the invoice goes out the same day. Manage it badly and the company bleeds in ways that never show up as a single line. A return trip because the first ticket did not say what was wrong. A bill the customer disputes because nobody wrote down what was approved. A box of breakers that got installed and never billed. An invoice that sat for three weeks because the paperwork was in a truck.
For a service business, the work order is the unit of work and the unit of cash. The estimate predicts the job and the invoice collects on it, but the work order is the thing in the middle that decides whether the second one matches the first. Get the record right and the rest of the operation has something solid to stand on.
What goes on a work order
A complete work order answers every question the office will ask after the truck leaves. If a field is missing, somebody has to call the tech, the customer, or guess, and all three cost time. The rule on a service job is simple: if it is not on the work order, it did not happen, and you cannot bill for it.
The record breaks into the same pieces on every job. The customer, site, and contact tell you who and where. The reported problem is what the caller said was wrong, in their words. The equipment or asset is the specific panel, unit, or circuit you worked on, ideally with a nameplate. The authorized scope is what the customer agreed to pay for. The findings are what you actually discovered, which often differs from what was reported. The work done is the fix. Parts and labor are what it cost you to do it. Photos are the proof. The signature is acceptance.
Two of those fields earn their place by preventing fights later. The reported problem and the findings are not the same thing, and writing both protects you. The customer said the lights flicker; you found a loose neutral in the panel. Recording the gap between the complaint and the cause is what turns a service call into a defensible record.
- Customer / site / contact
- Who is paying, where the work is, and who to reach on site
- Reported problem
- What the caller said was wrong, in their words, before diagnosis
- Equipment / asset
- The specific panel, unit, or circuit worked on, with nameplate where possible
- Authorized scope
- What the customer agreed to pay for, captured before the work
- Findings
- What you actually discovered on site, which often differs from the report
- Sign-off
- The customer signature that accepts the work and authorizes the bill
The work order lifecycle: call to cash
Every work order moves through the same stages, and the job stalls at whichever stage gets dropped. The lifecycle is create, schedule and dispatch, perform, document, invoice, then close. Money does not move until the last two are done, so a work order stuck at perform or document is a job you have paid for and not been paid for.
The stage that costs the most is the handoff between perform and invoice. The tech finishes, drives off, and the ticket goes quiet. Days pass before the office sees it, more days before it gets keyed into a bill, and by then nobody remembers the detail. That gap between the wrench going down and the invoice going out is where service companies lose their cash flow, and it is the single most fixable stage in the whole chain. Close each stage as it happens and the work order never sits. Let any stage wait for later and later becomes never.
| Stage | What happens | Where it stalls |
|---|---|---|
| Create | Capture the call: customer, site, problem, priority | Vague problem description forces a diagnostic re-call |
| Schedule / dispatch | Assign the right tech to the right time slot | Wrong skill or no parts means a wasted roll |
| Perform | Tech diagnoses, gets scope approved, does the work | Work done outside the authorized scope, no sign-off |
| Document | Findings, work, parts, labor, photos captured on site | Captured from memory at night, details lost |
| Invoice | Bill generated straight from the work order | Re-keying delay, ticket sits for days or weeks |
| Close | Payment collected, history filed, parts replenished | Open tickets pile up, unbilled work never caught |
Capture it in the field, not from memory at night
The most expensive habit in service work is filling out the ticket later. The tech does the job, means to write it up, and gets it down hours later in the truck or at the kitchen table. By then the part number is a guess, the start time is rounded, the second small repair is forgotten, and the photo that would have settled a dispute was never taken. Memory is not a record. It is a story that gets shorter every hour.
Capture happens on site or it does not happen accurately. The photos get taken while you are standing in front of the panel. The parts get logged as they come off the truck. The clock starts when you arrive and stops when you leave, not when you remember to think about it. The findings get written while the cover is still off and you are looking at the problem.
This is the case for a field tool the tech actually carries. FieldOS puts the work order on the phone in the tech's hand, so the photo, the part, the time, and the note land on the ticket at the moment they happen, not from memory in the parking lot. The job is documented before the tech pulls away from the curb, which is the only time the detail is still complete and correct. A ticket finished on site is a ticket you can bill tomorrow morning.
How the work order feeds the schedule
The work order is what the dispatch board schedules. Once a call is captured, dispatch puts it on the calendar and assigns a tech, and the quality of that assignment depends entirely on what the work order says. The right tech at the right time needs the work order to carry the skill required, the parts likely needed, the access window, and the priority.
A thin work order produces a bad dispatch. Send a tech with the wrong skill and you burn a truck roll and lose the first-time fix. Send one without the part the problem clearly calls for and you have scheduled a second visit before the first one starts. The richer the create stage, the better the dispatch, which is why the call taker who writes a real problem description saves the company a return trip they will never see on a report.
Tracking status so no job is lost
Every work order has a status, and tracking it is how you make sure no job is lost. Open, scheduled, in progress, on hold for parts, complete, invoiced. At any moment you should be able to look at the board and see exactly where each job sits and what it is waiting on. The status is the difference between running the work and the work running you.
The status that hides money is on hold for parts. A job that needs a special-order breaker goes quiet, the part comes in, and nobody remembers the customer is still waiting because the work order fell off everyone's radar. A clear on-hold status with the part on order keeps that job alive. The status that hides the most money is complete but not invoiced. The work is done, the customer is happy, and the ticket sits in a complete pile that nobody bills.
Untracked status is how good companies leak revenue without knowing it. The work got done. The customer would have paid. The ticket just never made it to a bill because nothing was watching the gap between complete and invoiced. A status you can see at a glance is the cheapest insurance a service department has against its own forgetfulness.
Recording parts on the work order
Record every part on the work order as it goes in, because an unbilled part is money you spent and never got back, and an unrecorded part is a truck stock count that no longer matches reality. The part has two jobs once it is on the ticket: it gets billed to the customer and it gets replenished on the truck. Miss the entry and you fail at both.
Unbilled parts are a quiet, steady loss. A few wire nuts here, a length of MC there, a couple of breakers on a busy day. None of it feels worth tracking in the moment, and across a year it adds up to real margin that walked off the truck and onto jobs you charged for labor only. The fix is to log the part when it comes off the shelf, not when you get around to it.
The part record also keeps the truck stocked. When the work order knows what was used, the system knows what to reorder, and the tech who needs that breaker next week actually finds it on the shelf. A part captured on the ticket closes two loops at once: the customer's bill and the truck's inventory.
Capturing labor time on the work order
Capture labor time on the work order because that one number feeds two systems that both matter: payroll and job cost. The tech's hours pay the tech, and the same hours tell you whether the job made money. When the time lives on the ticket, both come out of one honest source instead of a timesheet reconstructed at the end of the week.
Time reconstructed from memory drifts, and it drifts in the direction of round numbers. Three jobs become three two-hour blocks even when the first ran long and the third was quick. The payroll might still come out close, but the job cost is now fiction, and you have lost the ability to tell which kind of work actually pays. The clock that starts on arrival and stops on departure, captured on the work order, is the version you can trust.
Job cost is where the time pays you back beyond payroll. Compare the hours on the ticket to the hours the estimate assumed and you learn whether your pricing holds up. That feedback loop, from estimated hours to actual hours, is the same one the estimating and bidding guide leans on to tune the labor units. The work order is where the actual number gets captured.
Photos: proof and protection
Photos on the work order are proof of what you found and protection against what you will be accused of. Before, after, the nameplate, and the damage. Four kinds of photo cover most of what a service ticket needs, and the time to take them is while you are standing in front of the work, not after you have packed up.
The before photo settles the argument that the problem was already there. The customer says the panel cover was scratched, the breaker was already wrong, the water damage predated your visit. A timestamped photo from the moment you arrived ends that conversation before it starts. The after photo shows the work was done right. The nameplate photo captures the model and serial you will need for the next visit and the part you will need to order. The damage photo documents what you are not responsible for, which is its own kind of protection.
Photos also carry the work for the customer who never sees behind the wall. Most of an electrical repair is invisible the moment the cover goes back on. A before and after pair is how the customer understands what they paid for, and it is the difference between a bill that gets questioned and a bill that gets paid without a call.
The customer signature that accepts the work
The customer signature on the work order does two things: it accepts the work and it authorizes the bill. A signed ticket says the customer was there, saw the work, and agreed it was done. That is the cleanest answer there is to a payment dispute, and it is hard to get after the truck has left.
Capture the signature on site, at the end of the job, while the customer is standing there satisfied. Walk them through what was found and what was done, show them the after photos, and have them sign. The signature taken in that moment is worth far more than an approval chased by phone three days later, when the goodwill has cooled and the bill is the only thing left to react to.
On commercial work the sign-off may be a site contact or a facilities manager rather than the person who pays, and that is fine as long as the name and role are captured. The point is the same: someone with authority looked at the work and accepted it. That acceptance, on the ticket, is what stands behind the invoice when accounts payable goes looking for a reason to hold it.
Invoice straight from the work order
Invoice straight from the work order and you cut out the step that loses the most money and time: re-keying. When the parts, labor, scope, and signature are already on the ticket, the invoice is a generated document, not a research project. The office is not calling the tech to ask what the part was or how long the job took, because the answers are on the work order where the tech put them.
Re-keying is slow and it is wrong. Every time a number gets copied from a ticket into a billing system, there is a chance to transpose it, drop a line, or miss a part. The slow part is worse than the errors. A ticket that has to be deciphered, re-entered, and reconciled before it becomes a bill is a ticket that sits in a stack for a week, and days to invoice is the metric that decides your cash flow.
The whole reason to capture the job completely in the field is so the invoice writes itself when the tech hits complete. A work order that is whole on site becomes a bill the same day. A work order that is half-done becomes a phone call, a guess, and a delay. The complete ticket is the fast invoice, and the fast invoice is the cash.
How do you speed up invoicing?
You speed up invoicing by closing the work order in the field so the bill goes out the same day or the next. Days to invoice is the elapsed time between the job finishing and the bill landing, and it is one of the few numbers that moves your cash with nothing but a faster habit, because the invoice clock does not start until you send it. Sit on the ticket for two weeks and you have moved your own payment two weeks out for no reason but paperwork.
The lever is the field capture, not the office. An invoice cannot go out same-day if the office is still missing the part number, the hours, or the scope. When the tech finishes the ticket complete on site, the office has everything it needs the moment the truck leaves, and the bill can go out before the customer has forgotten the visit. Companies that bill within a few days of completion get paid materially sooner than companies that bill in weeks, because the whole collection clock shifts with the send date.
For residential service the target is tight: same day to a few days from completion to invoice. Commercial work runs longer because of purchase orders and approval chains, often a couple of weeks, but the part you control is still the same. Get the bill into their process fast and you sit at the front of the payment queue instead of the back.
Paper work orders vs digital
Paper work orders get lost, get illegible, and get re-keyed, and each of those is a tax on the job. The carbon copy left in the truck, the handwriting nobody can read, the ticket that has to be typed into the billing system by hand. Paper works until you have more than a couple of trucks, and then the cracks it leaves start costing more than the system would.
Digital work orders live on the phone, sync to the office in real time, and are searchable forever. The office sees the job close as it happens instead of waiting for the truck to come back. The ticket is legible because it was typed. The history is one search away instead of a filing cabinet. And the bill is generated from the data, not re-entered from a smudged page.
This is the case for going digital, and it is what FieldOS is built to do. The work order is on the tech's phone, the photos and parts and time attach to it on site, and the office has the complete ticket the instant the tech marks it done. No carbon copy to lose, no handwriting to decode, no second person re-typing the job into a bill. Paper is a real choice for a one-truck shop. Past that, the lost tickets alone pay for the switch.
How work orders build service history
Every work order you close becomes part of the customer and equipment history, and that history is one of the most valuable assets a service company owns. What was done before, by whom, with what parts, and why. The tech who walks into a job with the last three tickets in hand is a different tech than the one walking in blind.
History turns a recurring problem into a diagnosis. The breaker that has tripped three times in a year is not a fourth random call; it is a pattern that points at a real fault, and you only see the pattern if the first three visits are on the record. The panel you serviced two years ago has a nameplate and a parts list already captured, so this visit starts ahead instead of from scratch.
A field tool that keeps the history attached to the customer and the equipment is what makes this usable. FieldOS keeps every closed work order searchable against the site and the asset, so the tech pulls up what happened last time before they get out of the truck. That history is also what justifies a maintenance agreement and what proves your value at renewal: the documented record of everything you have done is the strongest argument you have for the next contract.
Flagging emergency and priority work orders
Flag the emergency and priority work orders so they jump the queue, because not all calls are equal and the schedule has to know the difference. A no-power call to a business losing money by the hour is not the same as a flickering light a customer can live with for a week. The priority on the work order is what tells dispatch which one moves first.
Without a priority flag, jobs get worked in the order they were entered, which is the order that ignores what actually matters. The emergency sits behind three routine calls because nobody marked it. The priority field fixes that: it lets dispatch sort the board by urgency, not just by time entered, and it sets the customer's expectation for when a truck shows up. On true emergencies, the speed of the response is the service, and the work order is where that clock starts.
When the work order prompts the safety steps
A work order can prompt the safety steps the job requires before the tech is standing in front of live gear. Lockout/tagout, the right PPE, a job hazard analysis. On electrical service work these are not optional, and building the prompt into the ticket is how you make sure the steps happen on the rushed call as reliably as on the planned one.
The work order is a natural place to require the safety checkpoint because it is the thing the tech is already looking at. A panel job that flags the need to establish an electrically safe work condition, with the lockout and the live-dead-live verification, keeps the discipline attached to the work instead of relying on memory under time pressure. The full sequence is in the lockout/tagout guide; the point here is that the work order is where the prompt belongs, so the safe step is part of the job, not a thing the tech is supposed to remember on their own.
The numbers that tell you the system works
A few numbers tell you whether your work order management is working, and they all come straight off the tickets. First-time fix rate, days to invoice, revenue per tech, and the count of unbilled or open work orders. You cannot improve what you do not measure, and these four measure the whole call-to-cash chain.
First-time fix rate is the share of jobs resolved in one visit. A common industry reference point is around 80 percent, meaning roughly one job in five needs a second trip, and every second trip is a truck roll you eat. Days to invoice measures how fast the bill follows the work, and it drives your cash. Revenue per tech tells you whether the trucks are productive. The count of open and complete-but-unbilled work orders is the leak detector: it shows you the jobs that got done and never turned into money.
Watch the unbilled count especially. A growing stack of complete-but-not-invoiced tickets is revenue you earned and have not collected, sitting in plain sight. That number should be near zero at the end of every week, and when it climbs, something in the document-to-invoice handoff has broken. The metrics are not a report for its own sake. They are the early warning that a stage in the lifecycle is stalling before it shows up in the bank balance.
Commercial work orders: PO numbers and not-to-exceed
Commercial work orders carry two fields residential tickets usually do not: the purchase order number and the not-to-exceed amount. Miss either and the bill gets held, because on commercial work the customer's accounts payable process is as much a part of getting paid as the work itself.
The PO number is the customer's authorization to spend, and most commercial and property-management clients will not pay an invoice that does not reference it. Get the PO on the work order at the start, not after the job, because chasing a PO number after the fact is how a finished job sits unpaid for a month. The not-to-exceed, or NTE, is the cap the customer sets on what a job can cost without a fresh approval. Hit the NTE and you stop, document where you are, and get a new authorization before you keep going, exactly the way you handle a scope change. Blow past the NTE without approval and you have done work you may not get paid for.
Many commercial and facilities clients also run a vendor portal, where the work order has to be updated and the proof of work uploaded for the invoice to clear. The portal is just their version of the same record. The work order you kept on your side, complete with photos and sign-off, is what feeds it. The cleaner your own ticket, the faster theirs clears.
One system: work order to schedule to invoice to accounting
The payoff of managing work orders well shows up when one system carries the job the whole way, from the work order to the schedule to the invoice to the accounting, with no double entry. Every time data gets re-typed between disconnected tools, you pay in time and in errors. One record that flows is the difference between an office that processes jobs and an office that re-enters them.
Picture the alternative most shops live in. The call goes in one place, the schedule is a whiteboard, the ticket is paper, the invoice is keyed into accounting software by hand, and the parts count is a separate spreadsheet nobody updates. The same job gets entered four times, and each entry is a chance to drop a part, miss an hour, or lose a ticket. The office spends its day moving data between systems that should have been one system.
FieldOS exists to be that one system for a service trade: the work order created from the call, dispatched to the tech, completed on site with parts and time and photos, and turned into an invoice without re-keying, with the numbers ready for the books. The work order is the spine the whole flow runs on. Capture it once, completely, in the field, and every downstream step has what it needs. That is the entire argument for managing work orders well, reduced to one sentence: enter the job once, get paid for all of it.
What to document on every work order
A work order you cannot reconstruct later is a work order you cannot defend, bill, or learn from. The fields below are the ones that answer the questions the office, the customer, and the next tech will ask. Capture them on site, while the job is in front of you, because every one of them is harder and less accurate to recover after the truck leaves.
The note column is where the field discipline lives. Reported problem and findings are separate fields on purpose. Authorized scope and any change order are separate from the work done. Parts and labor are captured as they happen, not estimated at the end. The signature and the PO close the record so the invoice has nothing left to chase.
| Field to record | Why it matters | Note |
|---|---|---|
| Customer, site, contact | Who pays and where the work is | Capture the on-site contact, not just the billing name |
| Reported problem | What the customer said was wrong | In their words, before diagnosis |
| Equipment / asset | Ties the job to a specific unit | Photograph the nameplate for model and serial |
| Authorized scope and price | Turns findings into billable work | Get the yes before the work, in writing |
| Findings | What you actually discovered | Often differs from the reported problem; record both |
| Work done | The fix, for the bill and the history | Specific enough that the next tech understands it |
| Parts used | Billing and truck replenishment | Log as they come off the truck, not from memory |
| Labor time | Payroll and job cost | Clock on arrival, off on departure |
| Photos | Proof and dispute protection | Before, after, nameplate, damage |
| Signature | Acceptance and bill authorization | On site, at completion, with name and role |
| PO and NTE (commercial) | Required for payment to clear | Get the PO up front; stop at the NTE |
Common mistakes
- Closing a job on an incomplete work order you cannot bill, or one so thin it forces a return trip.
- Filling out the ticket from memory at night instead of capturing it on site while the job is in front of you.
- Doing work with no scope authorization, then arguing about the bill after the fact.
- Letting tickets sit so days to invoice climbs and the cash-flow clock never starts.
- Leaving parts and labor off the ticket, so installed material and worked hours never get billed.
- Running paper work orders that get lost in trucks, go illegible, or have to be re-keyed into the bill.
- Skipping the PO number or blowing past the not-to-exceed on commercial work, so the invoice gets held.
- Never watching the complete-but-unbilled count, so earned revenue quietly piles up uncollected.
Field checklist
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
Standards and references
Work order management is a business process, not a code, so what governs it is your own process and the contract, not a published standard you can cite a section from. The framework everyone in field service uses is the call-to-cash lifecycle: create, schedule and dispatch, perform, document, invoice, close. Build your process around those stages and hold each one to completion, because the job stalls wherever a stage gets dropped.
The discipline that does carry weight is the customer authorization. The scope you got approved, the change order you got signed, the not-to-exceed you respected, and the PO you referenced are the contract terms of the job, and on a dispute they are what gets read. Treat the work order as the contract record for one job and you keep yourself clean. Where a job touches safety, the relevant safety standards still apply on their own terms, including OSHA and NFPA 70E for electrical work, covered in the lockout/tagout guide; the work order does not replace them, it prompts them.
Three things hold across every version of the process, and they are where the money is. Keep the work order complete, because you cannot bill what is not on the ticket. Capture it in the field, because memory is not a record. Invoice fast, because days to invoice is the number that decides your cash flow. Get those three right and the rest of the system has room to be imperfect.
Terms and definitions
Work order management has its own vocabulary, and the same idea shows up under different names across software, contracts, and the office. The terms below are the ones that matter on a service ticket.
A work order may be called a job ticket, a service order, or a job. Days to invoice is sometimes called time to invoice or service-to-cash. First-time fix rate is also written FTFR. The not-to-exceed is usually shortened to NTE, and the purchase order to PO. Whatever the label, the record is the same thing: one job, captured once, carried from the call to the cash.
- Work order (job ticket / service order)
- The single record of one job from the call to final payment
- Dispatch
- Assigning a scheduled work order to a specific tech and time
- Days to invoice (time to invoice)
- Elapsed time from job completion to the bill being sent
- First-time fix rate (FTFR)
- Share of jobs resolved in a single visit, no return trip
- NTE (not-to-exceed)
- The cost cap a customer sets before fresh approval is required
- PO (purchase order)
- The customer's authorization number, often required for payment
- Change order
- Authorized addition to the scope, captured on the work order mid-job
FAQ
What is a work order?
A work order is the single record of one job in a service business, from the first call to final payment. It holds the customer and site, the reported problem, the equipment, the authorized scope, the findings, the work done, parts, labor, photos, and the customer signature that accepts the work.
What should a work order include?
A complete work order includes the customer, site, and contact, the reported problem, the equipment worked on, the authorized scope and price, the findings, the work done, the parts used, the labor time, before and after photos, and the customer signature. On commercial jobs, add the PO number and the not-to-exceed amount.
Why is work order management important?
Work order management decides whether jobs turn into cash. Manage the record well and nothing falls through: the scope is authorized, parts and time get billed, and the invoice goes out fast. Manage it badly and you lose money to return trips, disputed bills, unbilled parts, and tickets that sit for weeks.
How do you speed up invoicing in field service?
Speed up invoicing by capturing the job completely in the field so the bill goes out same-day. When parts, labor, scope, and signature are already on the work order, the invoice is generated, not re-keyed. The office is not chasing the tech for details, so days to invoice drops and you get paid sooner.
What is the work order lifecycle?
The work order lifecycle is create, schedule and dispatch, perform, document, invoice, then close. The job moves through each stage in order, and money does not move until the last two are done. A ticket stuck at perform or document is a job you paid for and have not been paid for yet.
Paper or digital work orders: which is better?
Digital work orders beat paper once you run more than a truck or two. Paper gets lost, goes illegible, and has to be re-keyed into the bill. Digital lives on the phone, syncs to the office in real time, is searchable, and generates the invoice from the data. Past a one-truck shop, lost tickets pay for the switch.
What is NTE on a commercial work order?
NTE, or not-to-exceed, is the cost cap a commercial customer sets on a job before a fresh approval is required. Hit the NTE and you stop, document where you are, and get a new authorization before continuing. Blow past it without approval and you may have done work the customer will not pay for.
Why do you need a customer signature on a work order?
The customer signature accepts the work and authorizes the bill. A signed ticket says the customer saw the work and agreed it was done, which is the cleanest defense against a payment dispute. Capture it on site at completion, with the signer's name and role, because chasing approval by phone days later rarely works.
What field service metrics come from work orders?
First-time fix rate, days to invoice, revenue per tech, and the count of open or unbilled work orders all come straight off the tickets. Watch the complete-but-unbilled count especially: a growing stack is revenue you earned and have not collected, and it signals the document-to-invoice handoff has broken.
People also ask
Codes cited in this guide
This guide is written and reviewed against the published standards below. Always confirm the current adopted edition with the authority having jurisdiction.