Skip to content

Work order lifecycle

WorkOrder V3 gives SolarSENS teams a shared lifecycle for operational issues that need more than observation alone. It turns alarms, inspection findings, and service activities into tracked work with ownership, review, and history.

The lifecycle is the operating model behind every work order. It answers a simple question: what stage is this issue in right now, and what should happen next?

In SolarSENS, that lifecycle is designed to support both day-to-day execution and accountable close-out. Operators can see what is still open, supervisors can review what is ready for sign-off, and managers can look back at how work was handled over time.

Placeholder for a lifecycle diagram showing New, Assigned, Resolved, Action Needed, Completed, and Archived work orders

  • It keeps issues from disappearing into inboxes, chat messages, or informal notes.
  • It clarifies when work is ready for action, ready for review, or truly finished.
  • It supports better backlog management across plants, contractors, and internal teams.
  • It creates a reliable historical record for customer reporting and internal audits.

Some work orders begin as drafts before they are published into active operations. Draft work is not yet part of the active queue and should be completed or published before assignment, resolution, or archiving.

After publication, work typically moves through these stages:

  • New: the work order is active but not yet assigned to a specific person.
  • Assigned: an owner has been set and execution is expected to begin.
  • Resolved: the assigned work has been completed and submitted for review.

Resolution is not the same as final closure. Once a work order is resolved, it can enter review.

  • Pending Approval: the work is waiting for supervisor or admin review.
  • Completed: the resolution has been accepted and the work order is fully closed.
  • Action Needed: the reviewer has asked for rework or more evidence before closure.

When a work order returns to Action Needed, the assigned technician or responsible executor can update the work and send it back for review.

Archived work orders are no longer part of the normal active queue. Teams use archive to keep the live workspace focused while preserving the record for search, reporting, and future reference.

Unarchiving restores the work order back into an active state so it can continue moving through the workflow if needed.