Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Every quality issue in ION moves through a defined lifecycle: it opens, gets dispositioned, runs through any required reviews, and resolves. Three concepts govern that flow:
  • Status — where the issue is in its lifecycle (Pending → In Progress → In Review → Resolved).
  • Disposition — the decision about what to do with the affected material (Use As Is, Rework, Scrap, Return to Vendor, etc.). Dispositions are configurable per org.
  • Approval gates — the review checkpoints between statuses that require designated approvers to sign off before the issue can move forward.
Understanding the relationship between status, disposition, and approval gates is the difference between an issue closing cleanly and an issue stuck mid-flow because a required signal is missing.

Status: the four states

Issues progress through four statuses in this order:
#StatusMeaning
0PendingIssue has been created but no disposition has been chosen yet. The disposition badge reads DISPOSITION PENDING.
1In ProgressA disposition has been selected and any in-progress work (rework, containment, investigation) is underway.
2In ReviewIssue is staged for resolution and waiting on configured approvers to sign off.
3ResolvedAll required reviews have approved and the issue is closed.
Status moves forward via the Change Issue Status button in the issue header. Backward moves (e.g. reopening a Resolved issue) are possible when an issue needs more work after resolution.

Disposition: what to do with the material

A disposition is the decision recorded against the affected part(s) — the answer to “what happens to this nonconforming material?” ION ships standard dispositions and your org may have custom ones; common examples include Use As Is, Rework, Repair, Scrap, and Return to Vendor.

Selecting a disposition

In the issue header, the disposition badge sits next to the issue title. While the issue is Pending the badge reads DISPOSITION PENDING. Open the issue body to choose a disposition type — once selected, ION updates the badge and unlocks status progression.
The Reviews button is disabled until a disposition is selected. ION shows a tooltip — “Select a disposition type before beginning the review process” — to remind you. This is intentional: reviews ratify a specific resolution path, so the path needs to be chosen first.

Disposition availability behaviors

Disposition types can be configured with one of three availability behaviors that govern when the affected inventory becomes usable again:
  • Available Immediately — Inventory becomes available the moment the disposition is applied. Use for dispositions like Use As Is that don’t require any further action.
  • Permanently Unavailable — Inventory is locked out forever. Use for Scrap or destructive disposals.
  • Release on Resolve — Inventory becomes available only when the issue moves to Resolved (i.e. after all reviews approve). Use for Rework or Repair dispositions where the material isn’t usable until the work is done and signed off.
These behaviors are set per disposition type in admin settings; they’re not chosen per-issue.

Approval gates

Some statuses are gated by approval. ION uses two gate types:
  • In Progress gate — Configured approvers must sign off before the issue can leave Pending and become In Progress. Used when starting work on the disposition itself needs a sign-off.
  • Resolved gate — Approvers must sign off before the issue can move to Resolved. Used to ratify that the work performed actually closes the issue.
Whether a gate is required depends on how the disposition type and issue category are configured in admin. The issue header’s Reviews button shows the current approval state as a badge: <approved>/<total> — for example 2/3 means two of three required approvers have signed off.
Gates can never be the first or last status of an issue — they sit between statuses, not on them. This is enforced by the data model.

Steps

1. Open the issue

Issues are typically created from a run step (operator flags a problem), an inspection result, or a CAPA workflow. New issues open in Pending with no disposition.

2. Pick a disposition

In the issue body, choose the disposition type that matches the action plan: Use As Is, Rework, Repair, Scrap, Return to Vendor, etc. The disposition badge updates and the Reviews button unlocks.

3. Move to In Progress

Click Change Issue Status and move to In Progress. If the disposition or category requires the In Progress gate, ION will route to reviewers first; once they approve, status flips.

4. Do the work

While In Progress, perform the action the disposition calls for — rework, repair, additional inspection, supplier coordination, etc. Track containment, root cause, and any further actions inside the issue body.

5. Move to In Review

When the work is done, change status to In Review. ION sends review requests to the configured approvers. The Reviews button shows live progress (<approved>/<total>).

6. Resolve

Once all required reviews approve, move the issue to Resolved. If the disposition uses Release on Resolve, the affected inventory becomes available at this point. The issue’s transaction history records the resolution.

CAPA workflows

A CAPA (Corrective and Preventive Action) workflow extends the issue lifecycle with structured root-cause analysis and preventive actions that outlive the original issue. CAPAs are linked to issues via the Further Actions dropdown on the issue header — adding a CAPA spawns a related issue that tracks the corrective/preventive actions on its own lifecycle. CAPAs follow the same status/disposition/review model as standard issues but typically sit on a longer timeline and include explicit verification steps before resolution. For deeper coverage of CAPA mechanics, see CAPA workflows.

Tips

  • Pending is not a parking lot — issues stuck in Pending block downstream material flow. If you can’t pick a disposition because info is missing, log a comment and assign a teammate rather than leaving the disposition blank.
  • Use Release on Resolve for Rework — Don’t pick Available Immediately for dispositions where the material is actually being modified. The inventory will be marked available before the rework finishes, and operators downstream can pull it.
  • Read the Reviews badge2/3 means two approvers signed but one is still pending; the issue can’t move forward until the third weighs in. Use the badge to chase outstanding approvers.
  • Backward status moves leave history — Reopening a Resolved issue is recorded in the transaction history. Don’t avoid it when warranted; the audit trail keeps it traceable.