Job Settings
Settings → Jobs controls how jobs behave across the whole business: what statuses exist, what transitions are allowed, what's required at each stage, and how jobs are numbered. Most job-related support escalations trace back to something here.
Tabs in Settings → Jobs
| Tab | What it configures |
|---|---|
| Statuses | All job statuses — colours, close behaviour, required fields per status |
| Workflow | The business's workflows. Every account has a Default workflow; creating more needs the Advanced workflows feature (see below) |
| Job Types | Categories of work with linked forms, and with Advanced workflows, the workflow each type follows |
| Settings | Custom field labels on jobs, plus job card and recurring job numbering (prefix and sequence) |
| Fault Causes / Fault Codes / Fault Reasons | Diagnosis option lists for workshop/repair jobs |
| Terms | Default job terms and conditions text |
Job Statuses
Job statuses are the engine of ServCraft's workflow. Every status change can trigger automations, require fields, and change what options are available.
Configuring a Status
| Property | Effect |
|---|---|
| Description | The name shown in the UI and on documents |
| Status colour | Colour used in lists, calendar, mobile app |
| Start Status | Marks this as a starting status |
| Close Job | If ON, transitioning to this status closes the job — moves it out of the active list. This happens even for an employee whose Close job permission is off. Moving a closed job to a status that does not have Close Job ticked reopens it and clears its closed date |
| Mark Materials as In Progress / as Used | Controls what happens to the job's materials when this status is reached |
| Supplier Status | Marks this as a supplier-related status |
| Start Timer / End Timer | Starts or stops the job timer when a job reaches this status. Any status can have Start Timer, so a workshop can start the timer at its assessment status, its repair status or wherever suits it. A status can have one of the two ticked, never both |
| Complete Forms | Not offered on the start status. If ON, the web app and mobile app will not move a job to this status until every form linked to its job type is completed and not expired. The web app shows "You need to complete all required forms." and the mobile app shows "Forms need to be completed and expired forms need to be renewed and completed." |
| Complete Tasks | Not offered on the start status. If ON, a job cannot be moved to this status while any of its tasks is incomplete. The web app shows "You need to complete all tasks." and the mobile app shows "Tasks need to be completed." |
| Active | If OFF, status is hidden from users (can't transition to it) |
| Next Statuses | Only on statuses in an enforced workflow: which statuses a job may move to from this one |
Required Fields Per Status (Status Options)
Each status can have required fields — fields that must be filled in before a technician can move to that status.
To add one, open the status on Settings → Jobs → Statuses and, under Select required field for statuses, click Add field. The Add Fields to Status list opens; tick the fields and click Add. Each added field then has an Optional / Required switch. An optional field is shown on the job at that status; a required one must be filled in before the job can move to it.
Keep in mind: A business might require a fault code before marking a job as assessed, or an invoice number before closing a job. This is configured per-status.
Common required fields:
- Fault Code, Fault Cause, Fault Reason (for workshop/repair businesses)
- Assessment fee
- Serial number, reference number, previous job number
- Quote / invoice / credit note amounts and numbers
- Supplier and courier details
- Custom fields (text 1–4, checkboxes, dates, numbers), listed under the labels set on the Settings tab
- Customer Assets (shown with the note "Add Customer Assets"), for linking customer assets to the job
Capturing the machine at booking-in. For repairs on serialised items, add Customer Assets to the status a job starts in (for example "Item Booked In") and set it to Required. The web app then refuses to create the job, or move a job to that status, until a customer asset is linked, and shows "Customer assets are required". The mobile app does the same on its required fields screen when a job is moved to that status, blocking the save with "Customer Assets are required" until a customer asset is added. With Advanced workflows, add it to the start status of each workflow that needs it. The workflow's Customer Asset Selection setting (Settings → Jobs → Workflow) must not be Disabled: disabling it blocks adding customer assets to jobs and greys out Customer Assets on that workflow's statuses. Its other choices are Both, Non-serialised and Serialised.
Workflows and Advanced Workflows
A workflow is a named set of job statuses. Every account starts with one workflow called Default, and all its jobs use that workflow's statuses. On the Default setup, a job can move from its current status to any other active status in its workflow.
With Advanced workflows switched on:
- Create the workflow. On Settings → Jobs → Workflow, click Create and give the workflow a name.
- Add its statuses. On the Statuses tab, pick the workflow from the Workflow dropdown. The list then shows that workflow's statuses, and new statuses are added to it.
- Link job types to it. On the Job Types tab, each job type has a Workflow field. A new job follows the workflow of its job type, and its first status is that workflow's start status.
- Decide whether to enforce it. Each workflow has an Enforced Workflow switch.
| Workflow | What staff can pick when changing a job's status |
|---|---|
| Not enforced | Any other active status in the job's workflow |
| Enforced | Only the statuses listed as Next Statuses on the job's current status |
On an enforced workflow, each status on the Statuses tab gets a Next Statuses field. Use it to lay out the steps in order, for example Item booked in → Assessment → Repair in progress, so jobs cannot skip a step.
Limiting which statuses an employee can pick. On Settings → Employees → [employee] → Job Statuses tab, either switch on Access all job statuses, or switch it off and move the statuses the employee may use into the Assigned Job Statuses list. A status the employee is not assigned still appears when they change a job's status, but they cannot move the job to it. The tab appears for employees with a login when the account has Advanced workflows or advanced permissions. On an account with neither, every employee can pick every status. See Roles & Permissions.
Job Types
Job types categorise the kind of work. They control:
- Which workflow the job follows (which statuses are available)
- Which forms are attached by default
- How the job appears on reports and the scheduler
Configuring a Job Type
| Property | Effect |
|---|---|
| Name | Display label (e.g., "Service Call", "Installation", "Warranty Repair") |
| Workflow | Which workflow jobs of this type follow. Only shown, and then required, when the account has Advanced workflows |
| Default | Whether this type is pre-selected on new job creation |
| Only Linked Forms | If ON, only forms explicitly linked to this job type are shown on jobs of this type |
| Form Definitions | Forms linked to jobs of this type. Click Add Form on the job type to link one, or pick the job type in the Job types field on the form itself (Settings → Templates → Forms, Details tab). These are the forms a Complete Forms status waits for |
| Job Card Content | Rich text template for job card documents |
Record Sequence (Job Numbering)
Found on the Settings tab of Settings → Jobs, alongside the recurring-job sequence. Controls how job card numbers are generated.
| Setting | Effect |
|---|---|
| Prefix | Text prepended to the number (e.g., "JC-" or "2026-") |
| Sequence Value | The next number to use. Change this to adjust numbering (e.g., to start from 1000). |
| Latest Record Number | Preview of what the next job number will look like |
| Store-specific | Multi-store businesses can have separate sequences per store |
Changing the sequence: If a business migrated from another system and wants to continue their existing numbering, set the Sequence Value to match where they left off.
Warning: Setting the Sequence Value lower than the current highest job number will cause duplicate job numbers. Always set it higher.
Custom Fields on Jobs
Custom fields on the job record itself (not on statuses — those are Status Options) are configured on the Settings tab of Settings → Jobs.
For jobs, up to 10 custom fields are available:
- 4 text fields
- 2 number fields
- 2 date fields
- 2 checkbox fields
On the Jobs Settings tab you give these fields your own labels (the label must not clash with an existing column name). Unlike other modules, jobs have no per-field required/hidden toggles here — a job custom field is made mandatory by adding it as a required field on a job status. See Field Settings.
Related Topics in Job Configuration
Fault Codes
Fault codes are used on workshop/repair jobs for capturing diagnosis:
| Part | What it is |
|---|---|
| Fault Code | The broad category of fault (e.g., "Mechanical", "Electrical", "User Damage") |
| Fault Cause | What caused it (e.g., "Wear and Tear", "Power Surge", "Physical Damage") |
| Fault Reason | The specific diagnosis (e.g., "Faulty capacitor", "Screen crack") |
Configured on the Fault Codes, Fault Causes, and Fault Reasons tabs of Settings → Jobs.
Quote Settings
Settings → Quotes includes:
- Quote Expiry Period — how many days a quote is valid
- Terms & Conditions — default text appearing on all quotes
- Quote Numbering — prefix and sequence
Invoice Settings
Settings → Invoices includes:
- Invoice Due Period — days from invoice date until due
- Invoice Numbering — prefix and sequence
- Deposit display and payment display options on documents
Frequently Asked Questions
"A technician says they can't change the status on a job"
- Check Settings → Jobs → Statuses → the target status → its required fields
- Confirm the required fields are filled in on that specific job
- If the job's workflow is enforced, check that the target status is in the Next Statuses of the job's current status
- Check the employee's Job Statuses tab: if Access all job statuses is off, the target status must be in their Assigned Job Statuses
- If the target status has Complete Forms or Complete Tasks ticked, the job's forms or tasks must be finished first
"How do we stop a technician closing a job on the app until they've filled in a form?"
- On Settings → Jobs → Job Types, open the job type, click Add Form and pick the form.
- On Settings → Jobs → Statuses, open the status the technician moves the job to (for example the one with Close Job ticked) and tick Complete Forms.
From then on the web app and the mobile app refuse to move a job of that type to that status until every form linked to the job type is completed and not expired. Tick Complete Tasks on the same status to also require every task on the job to be done. With Advanced workflows each workflow has its own statuses, so tick Complete Forms on the matching status in every workflow where it should apply.
"We need a new status — how do we add it?"
Settings → Jobs → Statuses → + New Status. Set name, colour, and whether it's a close status. With Advanced workflows, first pick the workflow the status belongs to from the Workflow dropdown, and on an enforced workflow add it to the Next Statuses of the status that comes before it.
"How do we record that a customer cancelled a job?"
Set up a close status for it. Settings → Jobs → Statuses → + New Status, name it "Cancelled" (or similar), tick Close Job and link it to the workflows that need it. Moving a job to that status closes it, and the status name records the reason. The full cancellation steps are in The Job Lifecycle.
"Job numbers jumped — how do we reset them?"
Settings → Jobs → Settings tab → Record Sequence → adjust the Sequence Value to the desired starting point. Keep it higher than the current highest job number.
"How do we enforce that technicians fill in the fault code before closing?"
Settings → Jobs → Statuses → [your close status] → add Fault Code, Fault Cause, Fault Reason as required status fields. Technicians will see an error if they try to close without filling these in.
"Can we have different numbering for different branches?"
Yes, for multi-store businesses — the record sequence settings support a prefix per store.