Managing a Job Order from Sale to Installation: A Working Example
Connect departments and documents throughout a made-to-order job.
SqualiOnline editorial team · 2026-09-07
In a made-to-order job, the problem is almost never a single stage: it’s the handoff between one stage and the next. The sales rep promised a date, the design changed after approval, the materials were ordered against the previous version, and whoever installs it finds out on site. Every handoff is a point where information can stall, and it does.
Managing a job order means keeping together, under a single number, what today lives in different folders: the quote, the approved design, the materials, the hours, the documents, and the actuals.
The stages, and where time gets lost
Stages vary from company to company, but the structure looks similar: acceptance, design, customer approval, procurement, production, installation, closing. What needs to be decided isn’t the list itself, but what has to be true for a stage to begin.
- What’s needed going in: the signed design, the deposit received, the measurement verified on site.
- Who’s responsible: a person with a name, not a department.
- What it produces going out: a document, a finished part, a confirmation.
- What blocks it: the conditions that prevent moving forward, made visible right away rather than at the deadline.
The question that reveals the weak point is simple: if you ask today where a job order stands, how many people do you need to talk to for a certain answer? If it’s more than one, the system lives in people’s heads, and heads go on vacation.
An illustrative job order: a sign
The case that follows is built for the example: supply and installation of an illuminated sign for a shop. It’s meant to show where the documents attach and where problems arise.
- Acceptance. From the accepted quote, the job order is born, with a number. From that moment, everything — messages, attachments, hours — attaches to that number, not to the inbox of whoever handled it.
- Survey and design. The technician measures, photographs, and checks the constraints: mounting, power supply, required permits. The graphic design and the technical design are two separate documents, with two separate approvals.
- Approval. The customer approves a specific version, identified and dated. It’s the most important moment in the job order: from this point on, every change is a change order, not a clarification.
- Procurement. Materials and outsourced work are ordered against the approved version; every order stays linked to the job order, with an expected arrival date.
- Production. In-house work is logged with hours and who performed it. There’s no need for a stopwatch: what’s needed is knowing what’s been done and what’s still missing.
- Installation. Whoever goes on site needs to find the approved version, the survey photographs, the mounting instructions, and the list of what to bring.
- Closing. Signed report, photographs of the completed installation, documents handed over to the customer, actuals compared against the quote.
What needs to stay attached to the job order
The list is short, but it needs to be followed without exceptions: the system’s value lies exactly in there being none.
- The approved version, identifiable and non-overwritable.
- Purchase orders to vendors, with expected and actual dates.
- The tasks, with an owner and a status.
- Hours and materials consumed, recorded as they happen, not at month’s end.
- The documents exchanged with the customer, in the order they were exchanged.
If even one of these things keeps living elsewhere — in a shared folder, in a conversation, in a notepad — the job order can’t be reconstructed, and the first disagreement with a customer will prove it.
Change orders: the case that breaks improvised systems
A change order isn’t a problem: it’s a legitimate request. It becomes one when it arrives without anyone checking what’s already been done. There’s just one useful rule: before accepting it, check where the job order stands.
| When the change order arrives | What’s already been done | What the system needs to do |
|---|---|---|
| Before approval | Nothing irreversible. | Update the design and the estimate, no impacts to flag. |
| After approval, before ordering | The design is frozen. | Create a new version, require a new approval, recalculate the timeline. |
| After ordering | Materials committed or on the way. | Flag what becomes unusable, open an additional cost line, ask the customer for an explicit decision. |
| During production | Work already underway. | Stop the affected tasks, quantify the rework, update the delivery date. |
| During installation | Everything completed. | Treat the request as a new job, linked to the previous one. |
The value of this scheme isn’t in the classification: it’s in the fact that the response to the customer always contains the cost and the new date, and that response stays in writing. Change orders accepted verbally are the leading cause of vanishing margins in companies that work on job orders.
Closing: documents and actuals
A closed job order needs to be able to answer three questions without any digging: what was estimated and what it actually cost, where the signed documents are, and exactly what was delivered.
Comparing the quote against the actuals is valuable when it’s done at the end of every job, not once a year. It brings out the items that always slip through: the repeated trips, the rework hours, the spare materials used, the time spent chasing an approval. They’re the same items in almost every company, and nobody sees them until they look at one job order at a time.
What this guide doesn’t cover
This guide covers the job order flow from sale to closing. The specifics of a job site — crews, safety, reports signed on site, coordination with other contractors — call for their own discussion. Building quotes from price lists and rules, and organizing purchase requests and their approvals, also have dedicated guides.
Frequently asked questions
Where’s the best place to start if you currently work with spreadsheets?
From the point where information stalls most often: usually customer approval and change orders. Putting that in order gives a visible result within a few weeks, and the rest can follow without rushing.
How do you handle a change order requested verbally during the job?
By recording it before carrying it out, with the impact on costs and dates, and getting even a brief written confirmation. Change orders accepted verbally don’t get lost in the work: they get lost in the actuals, where they no longer show up for anyone.
What’s the difference between a job order and a design?
In common usage, the job order is the work sold to a customer, with a value and a deadline; the design is the document that describes what’s to be built. A job order contains the approved design and changes version when the design changes.
Let’s design the flow of your job orders.
If you’d like to talk it through, the service that handles this is Custom software.