# The Lifecycle of a Check

You've now created every kind of quality record. Two of them are templates you configure, and two are created each time a check runs:

| Record | Kind | Cleanliness Check example |
|---|---|---|
| Check sheet | Template | `Cleanliness Check` |
| Check item | Template | `Machining Area` |
| Check event | Execution | The check you started from Active Checks |
| Check item event | Execution | The `Dirty` you entered for Machining Area |

Each check item belongs to a check sheet. Each check item event belongs to both a check event and a check item, which is how a report can show "every answer for Machining Area" or "every answer on this check".

## Check statuses

A check that nobody starts moves through these statuses on its own, driven by its trigger's timers:

**Coming Due → Due → Over Due → Missed**

When someone completes it:

- **Submit** moves it to **Submitted**. If the sheet doesn't require a sign-off, it goes straight on to **Approved**, as your Cleanliness Check did.
- An **Approved** check can later be **Rejected** so it can be corrected. You'll do this in the Receiving Inspection chapter.
- A check that hasn't been approved can be **Cancelled**.

Reports and SPC treat **Approved** checks as final, valid data.

::embed-section{src="../../../kanoa-quality/checkSheets.md#timers" collapsed="true" summary="Reference Materials: Trigger Timers"}

:::note
The statuses are listed in [updateChkShtStatus](../../../systemFunctions/quality/event/updateChkShtStatus.md), for when you need to change a status from a script.
:::