Recurring jobs

Work that comes round on a cycle — a monthly filter change, a quarterly service, weekday cleaning — does not need creating by hand each time. Put a pattern on the job and the system raises each occurrence for you.

The occurrences are numbered off the original. Dem-983 is the job you set up; Dem-983.1, Dem-983.2, Dem-983.3 are the ones the pattern produced after it. Each is an ordinary job in its own right — it can be rescheduled, reassigned, priced and reported on without touching the rest.

Setting a job to repeat

Repeat this job, under the schedule in the Create New form, turns a one-off into a series. On a job that already exists, Edit Recurring in the header opens the same thing.

Job page → Edit Recurring

How often

The three tabs pick the unit — Daily, Weekly or Monthly — and the Recurring Pattern underneath says how often within it.

Every n week(s) on takes an interval and a set of days. Ticking Monday to Friday with an interval of 1 gives a job every weekday; ticking Monday with an interval of 2 gives one every other Monday. Daily and Monthly work the same way with their own options.

Where it stops

Range of Recurrence decides the span:

Setting	What it does
Starting on	The date the pattern begins
No end date	Runs indefinitely — for open-ended maintenance
End after n occurrences	Stops after a set number of jobs — twelve monthly services, four quarterly visits
End by	Stops on a date, usually the end of the agreement it belongs to

The box below restates what you have set in plain words — “This job will repeat on Monday, Tuesday, Wednesday, Thursday, Friday every 1 weeks starting on 14-July-2026 and repeat indefinitely”. It is worth reading before saving: it is the quickest way to catch a pattern that says something other than what you meant.

What the future jobs look like

Set data for upcoming jobs is where you decide what every occurrence inherits, and it is worth opening rather than assuming — this is the content of every job the pattern will create.

Inside it you can review or change the Project/Site Name and address, the contact details, the schedule start and end times, who the job is assigned to, and the job type, priority, tags, description and instructions. Anything set here applies to the occurrences rather than to the job in front of you, so a repeating job can be handed to a different fieldworker from the one who did the first visit.

Two tick boxes carry the harder-to-retype parts across:

• Copy equipment from parent job — every occurrence points at the same units. This is what makes a maintenance series work: the same four AC units get checked and reported on every month without being re-selected each time.
• Copy items from parent job — every occurrence starts with the same parts and services in its cart. Right for a service where the same filter is replaced every visit.

Update saves the pattern.

The Recurring Schedule

A job with a pattern on it shows a banner at the top of its Overview — (Running) Recurring pattern is added to this job — and the link on it opens the schedule the pattern produces.

Job page → Overview → the recurring banner

The header summarises the pattern — Frequency, Start Date, End Date — with Edit recur pattern to change it.

The table below is the series itself, one row per occurrence:

• Schedule Start — the date and weekday it is due.
• Recur Status — whether the job for that date has been raised yet. Job has been created means it exists.
• Details — the job code, as a link straight to that job.

This is the list to check when someone asks whether next Tuesday’s visit is already booked, or when a job that should have appeared has not.

Pausing, changing and stopping

Pause

The Paused / Running switch — on the Recurring Schedule window and in the footer of the pattern itself — stops the pattern raising new jobs without deleting anything. The pattern, its settings and every job already created stay exactly as they are, and switching back to Running picks it up again.

Pause is the right answer to a site closed for refurbishment, a client on hold over a dispute, or a seasonal service that stops over winter.

Change

Edit recur pattern reopens the settings. Changes affect the occurrences still to come; jobs already raised keep their own details.

Stop

Recurring Job → footer

Delete Recurrence Pattern ends the series for good. It removes the pattern, not the jobs — everything already raised stays in place with its history intact.

To wind a series down gently instead, set End by to a date and let the remaining occurrences run out.

Note

Deleting a single occurrence removes that one job. It does not stop the pattern, and the next date will still be raised. To stop the series, pause it or delete the pattern.

Note

Contracts have their own way of generating recurring work. If the repeat is really the contract’s schedule — a service visit due every month for the life of an agreement — set it on the contract rather than on one job. See contract work patterns.