Set Up Recurring Scope Inheritance

The problem

A strata cleaner running 12 buildings on weekly schedules has to apply the same scope template 624 times a year. That's the kind of repetitive work that operators stop doing — and then audit evidence falls behind.

The fix

Set a default scope template once per recurring schedule. Every spawned job materialises the template's items automatically.

Step 1 — Pick a template

From Dashboard → Recurring Jobs, find the schedule you want to configure. Click the green Scope link in the Actions column.

You'll land on a focused settings page showing:

• The schedule's context (title, customer, frequency)
• A list of available templates (system + your tenant templates)
• The current selection highlighted with an emerald ring + Current badge

Step 2 — Tap a template to set as default

Tap any template card. The selection saves immediately. From now on, every job spawned from this schedule will:

1. Be created normally (job number, scheduled date, site address, etc.)
2. Have the template's items copied into cleaning_job_scope_items automatically
3. Carry the source_template_id for audit trail

Step 3 — Verify the dashboard

The Recurring Jobs listing now shows a Scope Template column. Each schedule with a default template shows the template name as an emerald chip. Schedules without one show a "None — set" link.

If any schedules don't have a template set, the cleaning dashboard surfaces a nudge tile at the top: "Wire up scope templates on N recurring schedules".

Step 4 — Generate the audit trail

Over a 12-month contract cycle, your spawned jobs accumulate scope evidence. At AGM time (strata) or accreditation cycle (medical), generate the per-job PDF or use the proof-of-service workflow to bundle the evidence.

Caveats

• Each spawned job carries its own independent scope items — editing the template later doesn't propagate to historical jobs.
• If the source template is deleted, spawned jobs keep their items (the FK is set to NULL on delete).
• Items are only materialised on spawn — applying a template after the fact is a manual step from the job's scope page.