Summary
- Scope of Work helps convert job requirements into planned reports.
- Instead of relying only on manual report creation, users can define what reports are expected for a Work Order before execution starts.
What you can do
- Plan required reports for a Work Order.
- Generate draft reports from scope requirements.
- Add short instructions to distinguish similar planned reports.
- Give Creators clearer execution guidance.
Plan note
Scope of Work is intended for Professional and Enterprise workflows where report planning and execution control are important.
Why Scope of Work matters
Many work orders require several reports using the same or similar templates. Scope of Work helps show what needs to be done before the user starts creating reports.
This reduces the risk of missing required reports and makes progress easier to track.
Example
A Work Order may require one inspection before heat treatment and one inspection after heat treatment. Both may use the same inspection template.
Scope instructions can identify the planned reports as Pre-heat treatment inspection and Post-heat treatment inspection without relying on hidden template-specific fields.
Typical workflow
- Open the Work Order.
- Open Scope of Work.
- Add required report types or templates.
- Add a short instruction for each planned report where useful.
- Generate planned reports.
- Assign or execute the reports.
- Track progress from planned to completed documentation.