How to Manage Client Jobs and Work Orders

To manage client jobs properly you open a record for every piece of work you sell the moment the client accepts the quote, carry the agreed amount and the budget of hours and costs into it, then have people log their hours and expenses against that record. You read the margin by comparing what you sold with what you actually spent, while the work is still running rather than at the end of the year. The job closes when delivery is done, the invoice is issued and the final numbers live on the record instead of in somebody's head.

If today you know what you invoiced but not which jobs actually left you something, by the end of this guide you will have a repeatable way to open, track and close a job, and the ability to say at a glance which ones are late and which are burning more hours than planned.

One clarification first: this is not about drawing up a work plan. Visual planning, with dependencies and deadlines, is a separate craft and we covered it in the guide to project management with Gantt and Kanban. A job is the same work seen from the money side.

What you need before you start

• A list of the jobs currently open, even handwritten: client, a one line description, the agreed amount and the promised delivery date.
• An accepted quote as the starting point. The job is born there: if you still write quotes in a separate document, fix that piece first, following the guide on how to write a quote.
• A numbering rule, decided once and never argued about again. For example 2026-014, or ROS-14 if you prefer to see the client straight away. The code has to appear on the quote, the order, the job reports and the invoice.
• An internal hourly cost per role, even a rough one. Without it the final figure stays a list of hours and never turns into a margin.
• The external cost lines that belong to a job: suppliers, travel, materials, freelancers. Deciding in advance avoids arguments once the work is finished.
• One person who closes jobs. If the task has no name attached, three months later you have forty open jobs and no numbers.

Before you open the first record, agree on what gets written down at each stage. This grid covers most situations.

Stage	What happens	What has to be written down
Quote accepted	the client confirms	amount, terms, delivery date
Job opened	work starts	code, owner, budget of hours and costs
Work in progress	the budget gets consumed	hours per person, external costs, progress
Delivery	the client receives	actual date, any agreed extras
Invoice	you get paid	invoiced amount, linked to the job
Closing	you add it up	revenue, total cost, margin, notes for next time

How to manage a job, step by step

1. Open the job on the day it is accepted. Not at the first operational meeting and not when the signed order arrives: the moment the client says yes. From that quote you carry over the amount, the agreed lines and the promised delivery date. The expected result is that no sold work lives outside the system for days, which is the most common way of losing unlogged hours.

2. Give it a code and an owner. The code is how you find everything again, the owner matters because a job without a name next to it never gets updated. Write down the delivery date you promised the client, not the one you are hoping for: those are two different things, and the second protects nobody.

3. Write the budget before work starts. How many hours per role and which external costs you expect. A plausible example: job 2026-014 for Rossi Impianti, value 8,400 euro, budget of 60 technical hours, 12 coordination hours and 1,800 euro of supplies. You need a number, even an imperfect one: without an opening budget there is no variance to look at, and without variance your cost control is just an archive.

4. Have hours logged against the job, not on a separate sheet. Whoever is working needs to pick the job code and enter hours in a few seconds, ideally the same day. Hours reconstructed from memory at the end of the month are always rounded down, and the rounding comes straight out of your margin. How the operational side is organised is described on the page about projects and jobs.

5. Attach external costs as they arrive. The supplier invoice, the travel expense, the freelancer's day rate: each of those documents gets linked to the job when it comes in, not at the end. Loading it three months later means finding out after you have already told the client the job went well.

6. Review progress once a week, always on the same day. Three columns are enough: hours used against hours budgeted, costs incurred against costs planned, share of the work delivered. The useful moment to act is when you have burned 60 per cent of the budget with 30 per cent of the work done: there you can still talk to the client or reshuffle the team.

7. Invoice according to what you agreed. Deposit on signature, a stage payment halfway, balance on delivery: whatever scheme you use, every invoice has to stay linked to the job, otherwise revenue and costs live in two separate worlds. If you still issue everything by hand, the repetitive part can be taken off your desk, as explained in the guide to automatic invoicing for small businesses.

8. Close the job and read the margin. On delivery set the status to closed, check that no hours or invoices are still coming, and write two lines on what came out differently from the quote. The expected result is a readable line such as "sold 8,400, cost 6,950, margin 1,450", plus a note you will be glad to have when you quote a similar job.

Fixed price, time and materials, or retainer: what changes

The commercial arrangement changes what you have to watch, and mixing the three up is why some cost control systems tell you nothing.

On a fixed price job the price is agreed up front. The risk is entirely yours, so the thing to watch is hours used against budget: every extra hour comes out of your margin, and the weekly variance check is the only alarm you have.

On time and materials you invoice what you consume. The risk moves to the client, but a different problem appears: hours that are not logged are not invoiced, and they simply vanish. What counts here is daily discipline, plus transparency with the client about what has been used so far.

On a retainer or ongoing contract you sell a block of hours or a recurring service. The job becomes periodic, and the useful question is whether the client consumes more than they pay for: it is the kind of loss nobody notices, because the invoice goes out every month regardless.

Managing jobs in a service business

Maintenance, installations, field service, technical support: here a job collects work done in different places by different people, often in the same week. The weak point is the step from the on site report to the cost line.

The practical rule that works is that the technician records three things on site and not one more: job code, hours, materials used. Everything else is added by whoever coordinates. A report asking for twelve fields gets filled in badly in the evening, or not at all.

The other habit that pays off is separating contracted work from extras straight away. If the client asks for something more while you are on site, it either becomes its own line on the job or it becomes a gift: there is no third option, and you decide that day.

Managing jobs in a firm or an agency

In a professional firm, or in any business selling qualified time, the job usually coincides with the engagement and the main cost is people. You therefore need a different hourly cost per role, because an hour of coordination and an hour of execution do not weigh the same.

The line that escapes most often, though, is revisions: the third round of changes, the one that was never in the quote, is what turns a healthy job into a loss making one. Putting it on the record as a visible line, even at zero, means you can discuss it with the client with a number in hand. The same goes for percentages paid to agents or introducers: they are a genuine cost of the job and belong in the margin calculation, not in a separate corner of the accounts.

Managing jobs in the cloud: what actually changes

A spreadsheet works as long as one person keeps it. The problem starts when there are four: two versions of the file, one broken formula, and nobody able to say which copy is the good one.

With a cloud system the real advantage is not the technology, it is three concrete things. The technician logs hours from a phone while still on site, instead of reconstructing them on Friday. The accepted quote becomes a job without anybody retyping amounts and lines, and retyping by hand is where a good share of margin errors begin. Whoever coordinates sees the same screen as whoever made the sale, so questions about the status of a job stop being phone calls.

Connecting to the accounting side is the last piece: if issued invoices attach themselves to the right job, the final figure updates without anybody compiling it. In Flusia that runs through the Fatture in Cloud integration, and the point is to remove double entry.

Alternative method: start with what you already have

If you cannot change tools right now, there is a reduced version that still delivers most of the value and can be set up in an afternoon.

Take a sheet with one row per job and six columns: code, client, amount sold, hours used, external costs, status. Update only the hours, once a week, for the open jobs. That is enough to notice that three jobs out of twenty are consuming twice what was planned.

The limit is worth knowing: it holds up to around twenty open jobs and two or three people writing into it. Beyond that, keeping the sheet aligned costs more time than it saves.

Common mistakes

• Opening the job too late. Days pass between acceptance and the record being created, and somebody has already worked in the meantime. Nobody gets those hours back. The rule is to open it on the day of acceptance, even empty.
• A budget nobody ever wrote. With no planned hours there is no variance, and with no variance you are looking at figures that do not tell you what to do. A badly estimated budget beats no budget.
• Changes agreed verbally. "While you are at it, could you also..." erodes margins more than any quoting error. Every extra request becomes a line on the job, priced or with an explicit zero, before it gets done.
• Jobs that stay open forever. The work was delivered months ago but the record is still open, so your totals are wrong and nobody trusts them. It is worth reviewing open jobs once a month.

How long it takes, and what comes next

Setting up the numbering, defining hourly costs and bringing the open jobs into the system usually takes one working day if you have fewer than thirty jobs running. The slow part is the two or three weeks it takes for logging hours to become a habit rather than something the team leader has to remember.

After the first month look at one number only: the share of hours logged within a day. If it sits below half, the figures you are reading are not reliable, and the problem is not the tool but the moment at which you ask people to write their hours down.

The natural next step is upstream, making the path from opportunity to accepted quote clean enough that nothing has to be retyped when a job opens: how that part is organised is covered in the guide to the sales pipeline, and the quoting side is described on the quotes page.

Frequently asked questions

What is the difference between a job and a project? In everyday use, a project is the work seen from the side of tasks and deadlines, while a job is the same work seen from the money side: what was sold, what it is costing, what is left. In a small business they are often the same record looked at by two different people, and the advantage of keeping them together is not having to reconcile two lists.

How often should job figures be updated? Hours and costs get logged as soon as they exist, so the same day. Reading them is weekly: a fixed day when you go through the open ones and check the variance. Updating constantly and never looking is the most common situation, and it makes all the collecting pointless.

How do you handle changes requested after work has started? They become an extra line on the job, with a date, a description and an amount, even when that amount is zero because you chose not to charge for it. It lets you redo the sums on the remaining budget, and gives you a shared record for when somebody remembers the agreement differently.

Do you really need software to manage jobs? No. Below a certain size a tidy spreadsheet is enough, and the method matters more than the tool. A shared system starts to pay when several people have to write into the same data, when hours have to be logged away from the office, or when you notice you are retyping the same amounts from quote to job and from job to invoice. The guidance above is operational and general: for the accounting and tax treatment of what you record, check with your own accountant.