Attachments, evidence, and optional subtasks

Attachments keep operational evidence with the work order. Subtasks can organize smaller execution steps, but they are a deployment-dependent beta capability and may not appear in your interface.

Overview

Use attachments for photos, reports, screenshots, spreadsheets, and other files that help another reader understand what was found or done. Add them while the work is active; uploads are unavailable once a record is resolved or archived.

Add and review attachments

Open an active work order or add files during creation.
Upload one or more supported files.
Preview the files from the work-order detail.
Confirm that the evidence is understandable without relying on private messages or external storage.
Add final files before selecting Resolve and Close.

Resolved work-order PDF exports include image evidence and a file summary for every attachment. Non-image files are listed by name, type, and size so the export still records the supporting evidence.

Supported uploads are:

images
PDF
XLS or XLSX spreadsheets
CSV

The maximum size is 20 MiB per file.

Attachment deletion

Attachment removal is available only to admin or supervisor users and only while the work order is active. If an attachment is wrong and you cannot remove it, contact a user with the required access before resolving the record.

If subtasks are enabled

Some deployments expose a subtask beta inside create, detail, and resolve views. When it is available, use subtasks to divide one work order into smaller, independently trackable actions.

A subtask can include:

title and description
assignee
due date
sort order
an execution state such as Open, In Progress, or Done

The detail view may also offer an in-record My tasks filter. This is not a separate route and should not replace the shared work-order list.

If no subtask controls are visible, continue the ordinary workflow using the main work order and attachments. Do not rely on subtasks until the target deployment is confirmed to enable them.

Expected outcomes

evidence is stored with the operational record
supported files remain previewable to users who can read the work order
optional execution steps are clearer when subtasks are available
the workflow remains usable when the subtask beta is disabled

Caveats and operational notes

Keep the main subject and description understandable even when attachments are present.
Use production-safe evidence and avoid unnecessary personal or customer-sensitive information.
Upload and subtask actions remain subject to plant access and lifecycle state.