Skip to main content

Recurring Jobs

Recurring jobs (also called Job Schedules) are templates that automatically create new jobs at a set frequency. They power maintenance contracts, regular service visits, and any work that repeats on a cycle.


What Is a Recurring Job?​

A Recurring Job (Job Schedule) is a definition that says: "Create this job for this customer, at this frequency, and assign it to this technician."

It is not a job itself — it's a schedule that generates individual job instances automatically, each of which is a fully independent job record.


Permission Required​

Creating and managing recurring jobs requires the Recurring Job permission. Without it, staff can see recurring job instances but cannot create or modify the schedule.


Creating a Recurring Job Schedule​

Navigate to: Jobs → Recurring Jobs → + New Recurring Job (or Job Schedules → + New)

Required Fields​

FieldNotes
CustomerWhich customer this recurring job is for
ContactDefault contact for generated jobs
Job TypeCategory of work (must match an existing job type)
StatusThe status each generated job will start in — chosen from the statuses of the job type's workflow
DescriptionDescribes the recurring work. Copied to each generated job.
FrequencyHow often jobs are created (see below), as "Every x days/weeks/months"
Next Run DateThe due date of the next job. Must be today or later.
Create Job x Days BeforeHow many days before the due date to create the next job instance. Maximum 60.

Optional Fields​

FieldNotes
LocationDefault service location for generated jobs
End DateWhen to stop creating jobs. Leave blank for indefinite. Must be after the next run date.
Assigned TechniciansDefault technicians assigned to each generated job
ItemsInventory items/services to add to each generated job (with quantity and billable flag)
Customer AssetsThe customer's equipment (for example an aircon unit) that each generated job is for. Added with the Customer Asset button, which appears once a Job Type is chosen. See Linking equipment to a recurring job.
StoreWhich branch manages this recurring job (multi-store businesses)

Linking equipment to a recurring job​

  1. Open the recurring job, or create a new one, and choose the Customer, Contact and Job Type.
  2. Click Customer Asset.
  3. Pick the asset from the customer's assets. Tick Show assets for all customers to search beyond this customer, or Filter by job location to narrow the list to the schedule's location. A new asset can also be created from the picker if it is not on the register yet.
  4. Click Add, or Add & Next to link another unit, then save the recurring job.

Every job the schedule generates from then on carries the same assets, so the technician sees exactly which unit to service, and each visit appears on that asset's Jobs tab as service history. The same asset can only be linked once to a schedule. The recurring jobs list search also finds a schedule by the asset number or Other Number of a linked asset.

If the Customer Asset button is missing, check the Customer Asset Selection setting on the job type's workflow (Settings → Jobs → Workflow). When it is set to Disabled, users cannot add customer assets to jobs or to recurring jobs that use that workflow. When it is set to Non-serialised, the Customer Asset button still appears but only offers non-serialised items, so the customer's registered assets cannot be picked. Set it to Serialised or Both to link assets.


Frequency Options​

Frequencies are set as intervals within three types:

Daily​

SettingJobs created
Every 1 dayEvery single day
Every 7 daysWeekly (same as weekly but counted in days)
Every 14 daysFortnightly

Weekly​

SettingJobs created
Every 1 weekWeekly
Every 2 weeksFortnightly
Every 4 weeksMonthly-ish (28 days)

Monthly​

SettingJobs created
Every 1 monthMonthly on the same date
Every 3 monthsQuarterly
Every 6 monthsBiannual
Every 12 monthsAnnual

Monthly vs. 30-day daily: For maintenance contracts billed monthly, use the Monthly frequency type — it respects calendar months (so March → April → May). Using "every 30 days" will drift off the calendar date over time.


How Job Instances Are Created​

When a recurring schedule is active, ServCraft's background service creates individual job instances in advance.

What each instance gets:

  • Full job record with the schedule's default customer, contact, location, type, description, technicians, items, and linked customer assets
  • A link back to its parent schedule (so you can see all jobs generated by a schedule)
  • The status chosen on the schedule as its starting status
  • A start date equal to the schedule's run (due) date
  • Independent lifecycle — can be scheduled, worked, invoiced, and closed like any other job

Contact fallback: if the schedule is set to use the primary contact, or the saved contact has since been deactivated, the generated job uses the customer's current primary contact.

After creation:

  • The instance appears in the job list immediately
  • Staff can schedule it, assign technicians, and work it normally
  • Modifications to the instance (additional notes, different technician) do not affect the schedule or future instances

Managing the Schedule​

Viewing Recurring Jobs​

Jobs → Recurring Jobs (or Job Schedules → List) shows all active and inactive schedules.

Each schedule shows:

  • Customer and location
  • Frequency
  • Last job created date
  • Next job due date
  • Number of instances created to date

The list of recurring job schedules can be exported to Excel.

Editing a Schedule​

Editing the schedule changes future instances only. Existing job instances already created are not affected.

What you can change:

  • Frequency, description, assigned technicians, create-before days
  • Customer, contact, and location
  • End date (to stop the schedule from creating more jobs)
  • The Active toggle

Note: changing the customer on a schedule clears any customer-asset items linked to the old customer from the schedule's item list.

Ending a Schedule​

To stop a recurring schedule from generating new jobs:

Existing job instances already created remain as independent jobs and must be managed normally. Setting an end date does not cancel or delete those instances.

Deactivating a Schedule​

Important: A schedule cannot be deleted. It can only be deactivated.


Viewing Instances from the Schedule​

From the recurring job schedule record, you can see all the job instances that have been generated. This gives you visibility over the full history of a maintenance contract — which months were serviced, which technician did each visit, whether invoices were raised, etc.


Recurring Jobs and Invoicing​

ServCraft does not automatically invoice recurring job instances. Each instance must be invoiced manually (or via an invoice template if configured).

Common approach:

  • Job is generated and scheduled
  • Technician completes the work
  • Office reviews the completed job
  • Office creates an invoice from the job
  • Invoice is sent to customer

For high-volume maintenance contracts, some businesses use invoice templates that pre-configure the line items to speed up the invoicing step.


Common Questions​

"The recurring job didn't create an instance on time"​

"The wrong technician is assigned to generated jobs"​

Edit the recurring schedule and update the Assigned Technicians field. Future instances will use the updated assignment. Existing instances need to be updated manually.

"A maintenance customer has cancelled — how do I stop jobs from being created?"​

"Can I have multiple recurring schedules for the same customer?"​

Yes. A customer can have as many recurring schedules as needed (e.g., monthly fire extinguisher checks AND quarterly HVAC service are two separate schedules).

"We need to skip one instance (e.g., the customer was on holiday)"​

Delete or close the specific job instance that should be skipped. The schedule will continue creating the next instance at the correct time. The schedule itself is not affected.

"Can I create recurring appointments (not jobs)?"​

Recurring appointments are not directly supported — recurring schedules create recurring jobs. The appointment for each instance is created manually by the dispatcher once the job exists.