Jobs

A job is a work record that groups one or more of a customer’s assets together — an installation project, a service visit, a site inspection, or whatever piece of work you want to track. Every job belongs to exactly one customer, and any asset you add to a job has to belong to that same customer.

From a job’s detail page you can link and remove assets (including by scanning their QR codes), flag assets that have problems, upload files, and — on higher plans — attach maintenance.

What a job tracks

A job records:

• The customer it belongs to (chosen at creation, and not changeable afterward).
• An optional location — one of the customer’s locations, if they have any. This can be changed after the job is created.
• A name and an optional description.
• An optional work order with a status. Every org gets three fixed stages — Open, Completed, and Voided — plus whatever custom stages your org has added (an org starts out with In progress too, though it’s just an ordinary custom stage). A job without a work order has no status; see Job statuses under Service Tickets.
• Assigned techs (any internal team members — a job can go out to a whole crew), a service date, and work-performed notes. All three live on the job’s Service Ticket card, and the card only offers them once the job has a work order — a plain job has nowhere to set them. Each tech you add is emailed a link to the job — see Assigning techs.
• Structured parts & labor line items.
• The assets linked to it, each with an at-a-glance OK or Flagged badge.
• Created and last-updated dates.

Note

On the Pro plan, once an admin turns the feature on, a job can carry a work order — added from the job’s own page by picking a ticket type and filling in its fields. You then complete it as a signed service ticket, recording work performed, parts and labor, and a customer signature, then producing a branded PDF. Work orders are optional per job, and every job still starts out plain — see Service Tickets.

Creating a job

Both admins and members can create jobs.

1. Go to Jobs in the navigation.
2. Click New Job at the top right of the list.
3. In the Customer field, search for and select the customer this job is for. This is required — there’s no way to create a job without a customer.
4. If the customer has locations, a Location field appears, preselected to their primary location. Leave it as-is, pick a different one, or choose “No specific location.”
5. Enter a Job Name (for example, “Installation Project”).
6. Optionally add a Description.
7. Click Create Job. You’ll land on the new job’s detail page.

Every job is created as a plain job — there’s no work order yet. If your org has service tickets on, add one from the job’s detail page when the work is ready to be written up; see Writing up the ticket.

Tip

You can pre-fill the customer by clicking New Job from a customer’s detail page instead of from the Jobs list.

Editing a job

1. Open the job from the Jobs list.
2. Click Edit in the header.
3. Update the Job Name, Description, and/or Location.
4. Click Save Changes.

The name, description, and location can be changed — the dialog notes that the customer cannot be changed after a job is created. The Location field only appears if the customer has locations, and you can also clear it back to “No specific location.” Editing is available to both admins and members.

Deleting a job

Admins only

The Delete control is shown only to admins (and leads). Deleting a job removes the job and its asset links — it does not delete the assets themselves.

A job can be deleted until its work order is completed. Once a job has been completed as a signed service ticket, it’s a permanent record — the Delete control is hidden, and to correct it you void the ticket instead.

1. Open the job from the Jobs list.
2. Click Delete in the header (or Delete in the actions menu).
3. Confirm in the prompt.

If the job was created by an integration (Jobber, Trello, or HouseCall Pro), the confirmation warns that the source system may re-create the job the next time it updates.

Working with assets on a job

Everything below happens in the Assets card on a job’s detail page.

Link existing assets

1. Open the job and, in the Assets card, click Add Asset.
2. Optionally type in the search box (it matches unit number, model, serial, QR label, or description).
3. Tick the checkbox next to each asset you want, or use Select All.
4. Click Add N Asset(s).

The picker only lists assets that belong to the job’s customer, and it hides any already on the job. If you add several at once and one fails, you’ll see a message about which ones didn’t attach rather than losing the whole batch.

Add an asset by scanning its QR code

1. Open the job and, in the Assets card, click Scan QR.
2. Allow camera access and point your device’s camera at the asset’s QR label.
3. On a successful scan, the asset is added and a green “successfully added to job” message appears.

If no asset matches the code, you’ll see “No asset found with QR code #…”; if it’s already on the job, you’ll see an “already in this job” message. As with the picker, the scanned asset must belong to the job’s customer.

Create a new asset while adding one

When the equipment isn’t in the system yet, you can add it on the spot.

1. Open the job and click Add Asset.
2. Click New Asset (or Create your first asset if the customer has none yet).
3. Fill in the asset form — the customer is pre-filled to the job’s customer.
4. Save. The new asset is automatically selected in the add list.
5. Click Add N Asset(s) to attach it.

Remove an asset

1. Open the job and find the asset’s row in the Assets table.
2. Click Remove.
3. Confirm “Remove this asset from the job?”.

This only unlinks the asset from the job; the asset itself stays in your system.

Flag an asset

If something’s wrong with a piece of equipment, you can flag it right from the job.

1. In the Assets table, click Flag on the asset’s row.
2. Choose a Severity.
3. Write an Issue Description.
4. Click Flag Asset (or press Cmd/Ctrl+Enter).

The asset’s row then shows a red Flagged badge instead of OK. Issue flags are a Basic feature and above — see Issue flags & reports for the full picture.

Attaching maintenance to a job

Pro plan

Maintenance plans and tasks on jobs are available on the Pro plan and above. Compare plans →

On a Pro-or-higher org, a Maintenance card and controls appear on the job:

• Click Set Plan to attach a job-type maintenance plan (admins and leads only).
• Click Add Task to create a one-off maintenance task.

Below the Pro tier, the Maintenance card is hidden entirely. For the full workflow, see Maintenance plans and Completing maintenance tasks.

Uploading files to a job

Basic plan

Uploading files requires file storage, which is available on the Basic plan and above. Compare plans →

When your org has storage connected — FieldLabel Storage (the one-click default) or Google Drive — and job file storage is turned on, a file upload area appears at the bottom of the job page. Drag in or select files to attach them. See File uploads & storage for setup details.

Comments on a job

Every job has a private Comments thread for your team, the same kind of internal notes you can leave on a customer. Anyone on your team — members, leads, and admins — can add a comment.

1. Open the job and scroll to the Comments section.
2. Type your note in the Add an internal comment… box.
3. Click the send (arrow) button, or press Cmd/Ctrl+Enter.

Each comment shows who wrote it and when. The section is labeled Private — comments are internal notes and are never shown to the customer, whether in the Customer Portal or on a QR scan page, and they never appear on a service ticket or its PDF.

Adding a comment emails everyone currently assigned to the job (aside from whoever just wrote it) a copy of the comment and a View job link, so the crew doesn’t have to keep checking back for updates.

Importing jobs in bulk

If you’re moving existing work into FieldLabel, you can bring jobs in from a spreadsheet rather than entering them one by one.

1. Go to Jobs and click Import CSV.
2. Follow the modal to upload your file and preview the rows.
3. Confirm the import.

Each row must reference an existing customer, matched by name, so import your customers first. See CSV import for formatting and tips.

Jobs from integrations

Jobs can also be created automatically by your connected tools. When that happens, the job shows a via Jobber, via Trello, or via HouseCall Pro badge along with a link back to the original record. Learn more in the integrations overview.