Checklists

Checklists are a per-suite, per-project surface for capturing recurring procedures that need a sign-off trail: NPI gate criteria, line setup steps, field service preflight, anything where "did we actually do step 7?" is a question worth answering later.

Each suite has its own checklists page:

• Engineering -> /projects//engineering/checklists
• Manufacturing -> /projects//manufacturing/checklists
• Operations -> /projects//operations/checklists

The model and the UI are the same on all three; the suite tag scopes what's relevant to which team.

---

Concepts

---

Before you start

• Decide which suite owns the checklist. A "board bring-up" checklist belongs in Engineering. A "weekly line audit" belongs in Manufacturing. A "field service kit prep" belongs in Operations. If a checklist genuinely spans two suites, create one in each and link via the description.
• Pick the primary list early. The primary is what the team opens first every day. Set it once, change it rarely.

---

Quick start (3 minutes)

1. Open the page

1. Open your project
2. In the sidebar, go to -> Checklists
3. You land on the suite's checklist page. New project = empty list.

2. Import a starter from the library

1. Click Import from library
2. The modal lists every RND Square template available for this suite
3. Pick one (e.g. "Board bring-up - first article") and click Import
4. A new checklist appears in your project with all the template items copied in

Tip: The templates are starting points, not handcuffs. After import the checklist is yours - add, remove, or reorder items as needed for your product.

3. Add your own checklist (instead of importing)

1. Click New Checklist
2. Give it a name and an optional description
3. Add items one at a time. Each item gets a title and optional description.
4. Mark one checklist as the Primary for the suite (toggle on the checklist header)

4. Tick items as you work

1. Open the checklist
2. Click the checkbox next to an item
3. The item gets stamped with your name and the current time
4. Add an optional note if context is useful for the next operator

Note: Ticking an item saves immediately. There is no "Save" button to forget. The optimistic-lock token catches the rare case where another operator edited the same checklist at the same time - the UI re-loads instead of overwriting their change.

---

Workflow: weekly line audit (Manufacturing example)

1. Manufacturing manager imports the "Weekly line audit" template into the Manufacturing suite of the active project
2. Marks it primary so it stays at the top
3. Every Monday morning the line lead opens the checklist, ticks each item as the audit is run (paste compound stock check, stencil cleanliness, ESD wrist-strap continuity, etc.)
4. Notes go in the Note field on any item that needed attention
5. End of the audit: the checklist is a self-documenting log of "we did the audit on this date, here's who, here's what was noted"

---

Workflow: NPI gate (Engineering example)

1. Engineering lead creates a "Pre-PCB-spin gate" checklist
2. Items map to gate criteria: schematic review done, BOM costed, DFM pass, EMC pre-scan done, etc.
3. Each item gets a description with the standard the team agreed on
4. Before sending the PCB out for fab, the lead walks the list and ticks each item; the timestamps tell whoever cares that the criteria were verified before send
5. Set the status of the run by ticking the final item (e.g. "Cleared to fab")

---

Workflow: archiving an old checklist

You cannot delete a checklist (the audit trail is permanent), but you can archive it so it stops surfacing in the active view.

1. Open the checklist
2. Click Archive
3. Confirm
4. The checklist drops out of the default list. Archived ones still appear behind a filter for audit purposes.

---

Reference

Where does the template library come from?

The library is curated by RND Square - templates for common hardware-team scenarios (bring-up checklists, line audits, certification prep, RMA intake, etc.). Templates evolve over time; when an upstream template is updated, your imported copy does NOT auto-update (your edits would clash). To pick up a refreshed template you import a new copy next to the old one.

Suite scoping

The three suite pages are sealed off from each other:

• A checklist created in Engineering does not appear under Manufacturing.
• An operator with Operations-only access sees only the Operations checklists.
• Templates from the library are filtered to the matching suite when you open the import modal.

Concurrent edits

Two operators ticking items in the same checklist at the same time will both succeed - they're toggling different items. Two operators editing the same item simultaneously triggers the optimistic-lock check. The losing edit is rolled back and the UI re-loads so the operator sees the current state.

Common pitfalls

• "I imported a template but it has the wrong items for our product." Templates are starting points. Edit freely after import.
• "Two people are editing the same checklist and one keeps getting a stale-data warning." That's the optimistic-lock kicking in. Refresh, see what changed, retry your edit.
• "The primary checklist keeps changing." Make sure only one checklist per suite is flagged primary. The toggle is on the checklist header.

---

Related docs

• Engineering Suite - parent surface for engineering checklists
• Manufacturing Suite - line audits and production gates live here
• Operations Suite - field service prep and weekly health-check rituals
• Project Map & Timeline - see at a glance which suite is making progress