A good job numbering system gives every job one unique, permanent reference that appears on the quote, the job sheet, the certificate, the stock issue and the invoice. For most UK service and engineering firms the safest design is a short prefix, an optional year, and a sequential counter that the software issues automatically, so nobody types or reuses a number by hand. This guide covers the formats you can choose, the rules that keep numbers unique, and how to move across from a spreadsheet without breaking your history.
TL;DR
- A job number identifies the work. An invoice number identifies the bill. One job can have several invoices, so keep the two series separate and link them.
- Keep the number short and mostly meaningless: a prefix, an optional year and a sequential counter. Put detail such as site, trade or customer in fields, not in the number.
- Let software issue numbers. Manual numbering is where duplicates, gaps and arguments start.
- Never reuse or renumber a job. Cancel it, mark it void and keep the record.
- When you migrate, import the old numbers as they are and start the new counter above the highest one.
Table of Contents
- What a job number does
- Choosing a format
- How to create a job numbering system, step by step
- Keeping numbers unique and consistent
- Why numbering matters for compliance and records
- Our perspective
- Replacing spreadsheets without losing your history
- How Curcle handles job numbering
- A worked example
- FAQ
- Sources
What a job number does
A job number is the reference that lets everyone talk about the same piece of work. Wrike describes it as a way to distinguish jobs from one another and to streamline tracking and invoicing. In a service business that means the engineer on site, the office team booking the next visit, the stock controller and the person raising the invoice are all looking at one reference rather than a customer name and a guess about the date.
The number earns its keep when something goes wrong. A customer rings about a leak from a visit in March. A certificate needs reissuing. A warranty claim needs the original parts used. With a clean numbering system, you type one reference and everything attached to the job appears. Without it, you search emails, paper pads and three spreadsheets.
Job number versus invoice number
These are often confused. The job number identifies the work; the invoice number identifies an individual bill, and one job may have several invoices, for example a deposit, a stage payment and a final invoice. Put the job number on every invoice as a reference, but never use it as the invoice number itself.
The reason is not only tidiness. HMRC's guidance says a VAT invoice must carry a sequential number based on one or more series which uniquely identifies the document. If you reused job numbers as invoice numbers, a job with two invoices would break that rule, and a cancelled job would leave a gap in your invoice sequence. Two series, linked by a reference field, solves both problems.
Choosing a format
There are four formats you will meet in practice. Each suits a different kind of business.
| Format | Example | Strength | Weakness |
|---|---|---|---|
| Plain sequential | 104582 | Simplest to issue and say aloud | Tells you nothing at a glance |
| Prefix and sequential | J-104582 | Separates jobs from quotes, POs and invoices | Needs a prefix list that someone owns |
| Year and sequential | 2026-0417 | Easy to see age; counter stays short | Resets need care; busy firms can outgrow four digits |
| Coded (intelligent) | EL-LDN-26-0417 | Searchable by eye | Codes go stale and need training |
Plain sequential numbers
Every new job takes the next number, forever. It is the format with the fewest failure modes. Wrike's comparison of approaches notes that non-intelligent sequential numbers need no training and save time spent crafting identifiers, while intelligent numbers that encode information help searching but demand maintenance. For a firm with one or two trades and a few thousand jobs a year, this is usually enough.
Prefix and sequential
A prefix tells you what kind of record you are holding without opening it. A typical set: J for a job, Q for a quote, PO for a purchase order, C for a contract. Keep prefixes to one or two letters, and write down the list. If a new prefix needs a meeting to approve, that is a good sign the system is under control.
The same idea works inside the job family. Some firms use R for reactive callouts and P for planned preventive maintenance, because the two are managed differently and reported differently. That is a legitimate use of a prefix: it reflects a category that will never change for a given job.
Year and sequential
Year-based numbers such as 2026-0417 show a job's age at a glance and keep the counter short. The catch is the reset. When the year rolls over, the counter restarts at 0001, and the full reference is only unique because the year is part of it. That is fine, provided the year is always written as part of the number. Problems appear when people shorten 2026-0417 to 0417 in emails and phone calls, and two jobs from different years then collide.
Also size the counter honestly. If you issue 600 jobs a month, four digits will run out in the first quarter of the year, so use five digits from day one. Padding with zeros also makes numbers sort correctly in lists, where 9 would otherwise sort after 10.
Coded numbers
An intelligent number packs data into the string: trade, region, year, customer. It looks clever and works well in a small firm where everyone knows the codes. It degrades as the business grows. A customer is renamed, a region is split, a job moves to another trade, and now the number lies about the job. Because a number should never change once issued, you cannot fix it.
The better pattern is to hold that information in searchable fields and filters on the job record, and keep the number plain. You get the findability without the maintenance.
How to create a job numbering system, step by step
- List every record type that needs a reference. Jobs, quotes, contracts, purchase orders, invoices, credit notes, asset tags, certificates. Decide which share a series and which get their own.
- Pick the simplest format that survives growth. Prefix, optional year, then a padded counter. Estimate your busiest year, double it, and choose the digit count from that.
- Decide what a number is never allowed to do. Write three rules: numbers are never reused, never edited after issue, and never encode anything that can change.
- Link, do not merge. A quote converts to a job, a job spawns visits and invoices. Give each its own number and record the parent reference, so the chain is traceable in both directions.
- Decide how visits and variations are referenced. A job with three visits is best written as one job number with visit lines, not three jobs. Likewise, scope changes should hang off the original job. Our guide to contract variation control shows how to keep that audit trail clean.
- Assign an owner. One person or role maintains the prefix list and the rules. Without an owner, the system drifts within a year.
- Automate issue. Configure your software so the number is generated on creation. Nobody should type one.
Keeping numbers unique and consistent
Duplicates and gaps come from the same cause: more than one place deciding the next number.
One issuing point
If the office raises jobs from a spreadsheet while engineers raise them from a phone app, two people will eventually take 0418 in the same hour. Only one system should hand out numbers. The counter lives there, and every other tool, whether accounting, vehicle tracking or a customer portal, receives the number rather than creating it.
Handling cancellations and gaps
A cancelled job keeps its number and gets a status of void or cancelled. Resist the urge to recycle it. Gaps in a job series are not a compliance issue in themselves, but a visible reason for each cancelled number is what an auditor or a customer will want to see. Invoices are different: because VAT invoices need a sequential series, a spoiled invoice is voided and replaced, not deleted.
One number across the whole job
The job number should travel with everything. That includes the stock you issue, which is easier to trace when parts and serial numbers attach to the job (see serial number tracking for field service), photos and notes captured on site, and the cost lines that tell you whether the work made money. Our article on job cost tracking explains why costs only add up cleanly when every line points to one job reference.
Sub-jobs and parent jobs
Larger projects need a parent reference with child jobs beneath it, such as a refit with separate electrical, mechanical and commissioning packages. A simple convention works: the parent has its own number, and children carry the parent number plus a suffix, for example J-104582-01. Because the suffix is a counter rather than a code, it never needs updating.
Why numbering matters for compliance and records
In compliance-led trades, the job number is the thread that ties together the evidence: the certificate, the readings, the photos, the engineer's identity and the date. If you hold F-gas, gas, electrical or lifting equipment records, you will be asked to produce them by job or by asset. Our guide on F-gas record keeping shows how those duties map onto records you can retrieve quickly.
Retention is the other half. Under the standard UK public sector short-form contract, suppliers must keep full and accurate records for five years after the contract ends or is terminated. Your own contracts and regulators may set different periods, so check the terms that apply to you. The practical point is the same either way: a number that is permanent and never reused lets you find a job from years back without ambiguity. A number that was recycled, or that sits only in a spreadsheet nobody maintains, cannot do that.
For VAT records, HMRC's record keeping guidance covers how long you must keep invoices and what they must show; read the VAT record keeping notice for your own situation, and ask your accountant if you are unsure.
Our perspective
We built Curcle inside a real UK service and engineering business, and job numbering is one of the first things we saw go wrong there. Not because anyone chose a bad format, but because the same job lived under three different references: one in the diary, one in the accounts and one on the paperwork in the van.
Our view is that a job number should be boring. It should be short enough to read over the phone, impossible to duplicate, and issued by the system without anyone thinking about it. The intelligence belongs in the data around the number: the site, the asset, the engineer, the compliance type, the SLA and the cost. When you hold those as fields, you can report on them in ways a coded string never allows, and you can correct them without touching the identifier.
We also think software should earn every click. If a team has to decide a number, check it against a list or copy it between tools, the software is working for itself rather than for them. The number should appear when a job is created and then follow the job everywhere: scheduling, mobile app, stock, certificates, invoicing and reports.
— Luke Herridge
Replacing spreadsheets without losing your history
Most firms do not start from a blank page. They have years of jobs in a spreadsheet, a mix of formats and a few numbers everyone remembers wrongly. Moving to a proper system is where numbering goes right or wrong.
What to check before you migrate
- Find the highest number in use. Include quotes and invoices, and check every sheet and every person's local copy.
- Look for duplicates. Sort the list and filter for repeats. Decide which job keeps the number and how the other will be recorded, for instance by adding a suffix in an old-reference field.
- Decide whether old numbers stay. In most cases they should. Import them as they are, into a legacy reference field, so anyone searching an old email still finds the job.
- Start the new counter above the old maximum. Never let new and legacy numbers overlap.
- Keep the old format recognisable. If the old jobs were five digits and the new ones are J- plus six digits, nobody will confuse them.
- Set a cut-over date. From that day, only the new system issues numbers. Archive the spreadsheet as read-only.
- Test with a week of real jobs. Run a handful in parallel, then check that the job number appears on the schedule, the mobile app, the certificate and the invoice.
Also check what each connected tool expects. Accounting software may have its own reference field length, and a label printer or asset tag may only hold a certain number of characters. It is much easier to learn that now than after 500 jobs.
Common mistakes
- Encoding the customer name in the number, then renaming the customer.
- Using a date format that sorts badly, such as day-month-year.
- Running separate counters for each engineer or van, which makes the combined list unsearchable.
- Letting someone "reserve" a block of numbers for a big project.
- Deleting cancelled jobs instead of voiding them.
How Curcle handles job numbering
Curcle brings jobs, customers, engineers, assets, compliance, stock, quoting and invoicing into one connected system, so a job reference is created once and carries through every step. Field and office teams see the same record, and the mobile engineer app works offline, so numbering does not depend on a signal. Plans start from £99 per month on Starter, £249 per month on Professional and £499 per month on Business, with Enterprise priced on request; see the pricing page for what each includes. If you want to see the workflow before deciding, watch Curcle in action or read about our field service management software.
If your job references currently live across spreadsheets, diaries and paperwork, moving them into one platform is usually the point where numbering, scheduling and invoicing stop fighting each other. Our features page shows how the pieces fit together, and the invoice collection guide covers what happens once the invoice is raised.
A worked example
Take a 15-engineer electrical and maintenance firm handling around 4,000 jobs a year, a mix of reactive callouts and planned visits. Growth plans suggest 6,000 within three years.
A workable design: J for jobs, Q for quotes, C for contracts, PO for purchase orders, each followed by a six-digit padded counter that never resets. Jobs are tagged as reactive or planned in a field rather than in the number. Invoices run in their own series, INV-000001 onwards, and each carries the job number as a reference. Visits sit under the job as lines, and a variation to scope is recorded against the original job with its own approval record.
Six digits gives a million numbers, far beyond the firm's needs, and the reference reads easily over the phone: "J one-oh-four-five-eight-two". Reports by trade, site, customer or engineer come from fields, so none of that changes if the firm adds a new region or renames a customer.
If the firm prefers year-based numbers, J-26-00417 works equally well, provided the two-digit year is always written and the system, not a person, manages the reset.
FAQ
What is a job number?
A job number is a unique reference given to a piece of work so that everyone can find and track it. It normally appears on the quote, the job sheet, any certificates and the invoice. It identifies the work, not the bill, so it sits alongside an invoice number rather than replacing it.
Should a job number include the year or customer?
A year is fine if it is always written as part of the number and the system manages the reset. A customer code is riskier, because customers are renamed, merged and lost. Hold customer, site and trade in fields, and keep the number itself plain.
Can I use the job number as the invoice number?
It is better not to. A VAT invoice needs a sequential number from a series that uniquely identifies it, and one job can produce several invoices or none. Give invoices their own series and print the job number as a reference.
What should I do with a cancelled job number?
Keep it and mark the job void or cancelled, with a short reason. Never reuse it, because reused numbers make historic records ambiguous. A visible reason also helps if you are later asked why a number is missing from the sequence.
How many digits do I need?
Work out your busiest year, double it for growth, and choose enough digits that you will not run out within ten years. Six digits with no reset suits most small and mid-sized service firms. If you reset yearly, make sure the year is always part of the written number.
Sources
- How to Use Job Numbers to Manage Work (Wrike)
- How to Add a Job Number to an Invoice (InvoiceAtlas)
- VAT guide (VAT Notice 700), GOV.UK
- Record keeping (VAT Notice 700/21), GOV.UK
- Short form contract for the supply of goods and/or services, Contracts Finder