Work patterns — the schedule that creates jobs
A work pattern is the engine that turns a contract into actual visits. You describe the routine once, and the system creates the jobs on the dates they fall due for the life of the contract.
The useful way to think about it: a pattern is a job template plus a schedule. Everything you set on it — the services, the equipment, the tools, who does it — is stamped onto every job it creates, so those jobs arrive ready to work rather than as empty placeholders.
Add one from the Work Patterns / Jobs step of the contract, with + Add Work Pattern.
The schedule
Section titled “The schedule”
Add Contract → Work Patterns / Jobs → Create New Pattern
Pattern dates default to the contract’s own dates, so a pattern normally runs for exactly as long as the agreement does. Edit lets you narrow that — useful when a routine only applies to part of the term.
Recurring Schedule is the cadence: Daily, Weekly or Monthly. Each opens its own options — a daily pattern, for example, can run every N days, or only on weekdays (Monday–Friday).
Schedule Start Time and Schedule End Time set the time window each generated job carries.
Create New Pattern → schedule times
What each job will carry
Section titled “What each job will carry”Everything below is copied onto every job the pattern produces.
The services
Section titled “The services”
Create New Pattern → Job Type/Services
This is the work to be performed — and the note under it restates the most important rule on any contract:
Only services defined in Service Rate Configuration are treated as invoice items. Services selected here but not configured there remain to-do job services and are not billed as invoice items.
In other words, putting a service on a pattern schedules the work; putting it on the rate card is what makes it billable.
Items, equipment, location and tools
Section titled “Items, equipment, location and tools”
Create New Pattern → job contents
- Items for this Job — materials the visit normally consumes, attached up front so nobody has to remember them.
- Client’s Equipment to be serviced — either no equipment service required, or specific equipment picked from the contract’s list. That second option is what lets one contract cover a large estate: each pattern targets its own subset of units.
- Job Location/Site — optional, for when the work happens somewhere other than the client’s default site.
- Tools Required — a checklist of tools, each with its model number, so the technician turns up equipped instead of driving back for a multimeter.
Crew and instructions
Section titled “Crew and instructions”
Create New Pattern → assignment and instructions
- Assign Fieldworker(s) — the generated jobs come pre-assigned rather than landing unassigned in the scheduler.
- Job Description and Job Instruction — what the visit is, and how to carry it out.
- Job Priority and Tag(s) — so recurring work sorts and filters alongside everything else.
Save Pattern adds it to the contract, and the jobs then appear on their scheduled dates on their own.
Several patterns on one contract
Section titled “Several patterns on one contract”A single contract can hold several patterns, each on its own cadence — which is what lets one agreement cover quite different routines.
Contract page → Work Terms / Pattern
Office cleaning. Daily dusting and a weekly window clean become two patterns on one contract, each with its own services.
A shopping mall with 100+ cameras. Instead of one impossible visit, set up four weekly patterns, each pointing at a different 25 cameras through Select specific equipment from contract list. The whole estate gets serviced every month under a single contract, and each visit tells the technician exactly which units to check.
Related
Section titled “Related”- Fixed price and service based contracts — whether a pattern’s services are free, quota-limited or charged
- Jobs under a contract — how the generated jobs behave once they exist
- Equipment on a contract — linking the equipment a pattern can target