Subtasks, attachments, and evidence

Many operational issues are too detailed for a single status change alone. WorkOrder V3 supports subtasks and attachments so teams can organize execution work and show what was actually done.

Overview

Use this workflow when the main work order needs supporting steps, handoffs, or evidence. This is especially valuable for corrective work, inspections, shutdown-related issues, and any activity where reviewers or customers may later ask for proof.

When to use this

one work order contains several smaller execution steps
multiple people contribute to the same operational issue
the team needs to attach photos, reports, screenshots, or documents
reviewers need evidence before approving closure

Step-by-step workflow

Open the parent work order and decide whether the job should be broken into smaller actions.
Add subtasks for the checks, repairs, verifications, or handoffs that need separate tracking.
Assign subtask owners or due dates where they help clarify execution.
Upload attachments such as site photos, inverter screenshots, test results, or signed reports.
Keep the main work order focused on the overall issue while using subtasks and files for supporting detail.
Review the evidence before resolving the work order so approval is not delayed later.

Expected outcomes

the main work order stays readable and decision-focused
execution detail is organized instead of buried in long notes
supervisors can review proof of work alongside the work order record
customer-facing or audit review is easier because evidence is already attached

Caveats and operational notes

Use subtasks to clarify execution, not to hide the primary issue from the main work order.
Evidence should support the operational outcome, not just document activity for its own sake.
Attachments are especially valuable before approval, because they reduce avoidable Action Needed cycles.
If a file is outdated or incorrect, remove it promptly so the record stays trustworthy.