Job lifecycle reference
Jobs use one shared lifecycle across sample analysis, training, and consultation. Each job type adds the delivery gates it needs without creating a separate status model.
Lifecycle stages
| Stage | What it means | Primary next action |
|---|---|---|
| Draft | Request is saved but not submitted. | Complete and submit the request. |
| Under Review | QIAS LIMS is reviewing the request. | Approve for quotation or request changes/cancel as appropriate. |
| Quotation Sent | Client quotation decision is pending. | Client accepts or declines. |
| Invoice Sent | Invoice is available and payment is pending. | Client uploads payment proof. |
| Payment Received | Payment is confirmed; delivery preparation begins. | Send instructions, assign owner, and complete job-type prerequisites. |
| In Progress | Assigned delivery work is active. | Record work and prepare the final deliverable. |
| Pending Validation | Work is submitted to the reviewer. | Reviewer approves or requests changes. |
| Pending Rework | Reviewer requested corrections. | Execution owner resumes and corrects work. |
| Ready for Delivery | Review is approved. | Administrator publishes a clean final deliverable. |
| Published | Client-facing result is released. | Client downloads results; administrator may close the job. |
| Closed | Operational workflow is archived. | Published results remain client-accessible. |
Job-type gates
| Job type | Before Start Work | Before Submit for Review | Client-facing deliverable |
|---|---|---|---|
| Sample analysis | Physical receipt must be recorded. | Required work is complete and final report is clean. | Final report and, if provided, CoA |
| Training | Next instructions must be sent. | Schedule and session completion are recorded; completion report is clean. | Completion report |
| Consultation | Next instructions must be sent. | Schedule and session completion are recorded; session summary is clean. | Session summary |
Client-facing status language
Client views intentionally simplify internal workflow terminology. For example, internal validation and rework states remain grouped as progress rather than exposing staff-only process language. The job’s own page and published-results panel are the authoritative client surfaces.
Why an action may be unavailable
QIAS LIMS removes or disables actions when a required preceding event is missing, when the current user is not the required actor, or when the job is in the wrong stage. Look for the explanation in Next Action before assuming an error.