Recurring Jobs
A recurring job pairs a standard request with one OMC and a frequency — weekly, monthly, quarterly, annually — so that the next occurrence of the work is always in view. Recurring jobs are used for planned preventative maintenance and other tasks that have to happen consistently across every managed development: fire safety checks, lift servicing, grounds maintenance, insurance renewals.
Each job tracks when its next request is due, the last request it created and that request’s status. A job that falls overdue is highlighted so nothing is missed.
List View
Section titled “List View”
| Column | Type | Description |
|---|---|---|
| Owner Management Company | picklist | The OMC this recurring job is configured for. |
| Standard Request | picklist | The standard request this recurring job is based on. |
| Supplier | link | The supplier assigned to handle this recurring job. |
| link | The number of open requests currently assigned to this supplier. | |
| + | icon | Indicates whether a new request should be created for a different supplier. |
| frequencyIndicator | icon | A visual indicator of how frequently this job recurs. |
| Frequency | text | The name of the recurrence frequency. |
| Prev Year | number | The number of times per year this job is scheduled to run. |
| Next Occurrence | date | The date the next occurrence of this job is due. |
| plannedDateIndicator | icon | A visual indicator of whether the next planned date is on time, due, or overdue. |
| Edit | icon | Edit the details of this recurring job. |
| Last Request | link | The reference number of the most recently created request for this job. |
| Last Status | picklist | The status of the most recently created request for this job. |
| Create Next Request | icon | Additional status indicator for the last request. |
| Last Planned | date | The planned completion date of the most recently created request. |
| lastPlannedDateIndicator | icon | A visual indicator of whether the last request's planned date was met. |
| Last Owner | picklist | The team member who owns the most recently created request. |
| Occurrences | link | The total number of times this job has run to date. |
| Property Manager | picklist | The property manager for the OMC this job belongs to. |
| Admin | picklist | The administrator for the OMC this job belongs to. |
| Finance | picklist | The finance team member for the OMC this job belongs to. |
| Delete | icon | Remove this recurring job. |
| Notes | longText | Notes about this recurring job. |
The Next Occurrence column is the date the next request needs to be planned for. Last Request links to the most recent request the job created. The Create Next Request button raises that request; it is hidden while the job’s last request is still open, so a job never gets ahead of itself. A job is retired by setting its frequency to Never rather than deleted.
Detail View
Section titled “Detail View”
| Field | Type | Description |
|---|---|---|
| Owner Management Company | picklist | The OMC this recurring job is configured for. |
| Standard Request | picklist | The standard request this recurring job is based on. |
| Supplier | link | The supplier assigned to handle this recurring job. |
| frequencyIndicator | icon | A visual indicator of how frequently this job recurs. |
| Frequency | picklist | The recurrence frequency — e.g. Weekly, Monthly, Quarterly, Annual. |
| Prev Year | number | The number of times per year this job is scheduled to run. |
| Next Occurrence | date | The date the next occurrence of this job is due. |
| plannedDateIndicator | icon | A visual indicator of whether the next planned date is on time, due, or overdue. |
| lastPlannedDateIndicator | icon | A visual indicator of whether the last request's planned date was met. |
| Notes | longText | Notes about this recurring job. |
Where recurring jobs come from
Section titled “Where recurring jobs come from”Recurring jobs are normally created in bulk from the Setup Jobs action on a standard request, which lists every OMC and lets you schedule it against as many of them as needed at once.
Creating the next request
Section titled “Creating the next request”Clicking Create Next Request on a job opens the new request stepper, already filled in from the standard request — the standard request itself fixed, since it is the job’s, and the planned date set to the job’s next-occurrence date. Stepping through gives you the request to review and its checklist of actions, each dated from the planned date.
An action can never be planned for a date that has already passed. If the job is due soon enough that the earlier steps of its checklist would fall in the past, those steps are shown with their real dates and the stepper will not let you finish until you have given each of them a new one.
Creating the request advances the job’s next-occurrence date by one interval and links the job to the request it just created.
- Click [Recurring Jobs] on the main menu
- Click Create Next Request to raise this quarter's request from the standard request
- Click Next - the standard request and its planned date come from the job
- Click Next to confirm the details filled in from the standard request
- Click Next to confirm who the request is for
- Click Create Case to raise the request with its plan of actions