Service Scopes & Checklists
Make the promised scope clear from public service selection through completed work.
Try TidyOps free
The Reality
Generic service names leave customers and cleaners interpreting what is included differently, especially when the scope changes over time.
The TidyOps Workflow
Authorized staff maintain normalized service scopes and publish approved versions. Public service details show the current released scope, while jobs retain the applicable checklist context for operational completion.
In Practice
Customer clarity
Show buyers the current included tasks and scope detail before they choose a service.
Versioned publication
Draft and publish approved scope changes without rewriting the meaning of historical work.
Cleaner checklist
Carry the applicable service tasks into job execution and completion controls.
Concrete Capabilities
- Normalized tasksManage reusable task definitions, service-specific inclusion, and approved public labels.
- Published releasesExpose only approved service-scope releases to public pages and booking flows.
- Job completion contextUse the applicable checklist during work and require configured completion conditions.
Frequently Asked
Can scope changes alter old jobs?
Published scope versions preserve the context that applied to existing work rather than silently replacing it with a later draft.
Do customers see internal checklist notes?
No blanket claim is made that internal operational notes are public. Public service details are based on approved published scope content.