Campaign startup checklist: base checklist, templates, item library

Every unit and every campaign is different. So there is one base checklist per unit and one checklist per campaign: the campaign checklist is copied in from the chosen source when it is created, and from then on it belongs to the campaign. You edit the checklists on the Campaigns page — on the Startup checklists card and on the Startup checklist tab of the campaign drawer.

A copy, not a live link

An inserted item remembers its source (e.g. “Template · Acid chloride startup · v1”), but later changes to the source do not rewrite it. When the source is updated, the item shows “The source was updated — adopt it?” on the base checklist, in templates, in the library and on a campaign checklist that has not started yet; Adopt brings the new content over.

Before you start

• The Campaign add-in is on and the unit is a campaign unit (Campaign settings).
• Permissions: the unit base checklist needs campaign:configure; the campaign checklist, templates and the item library need campaign:checklist:edit. With campaign:view alone the checklist is read-only.
• Base and campaign checklists are visible only for units of your own site; templates and the library belong to every site of the organisation.

Steps

1. The unit’s base checklist. On the Startup checklists card, in the unit’s row: Create base checklist, then Edit. Add sections (e.g. “Safety systems”) and type the items at the bottom of the section — Enter saves and opens the next line.
2. Item details. In the item’s ⋮ menu choose Edit: how it is completed (tick · inspection pass / fail / N.A. · measurement with unit and limits), the photo and comment rules, whether it is required, close before startup or can be closed after startup, and the responsible role. The preview shows what the person completing it sees.
3. Templates and library. A new template starts empty or from the built-in PSSR sample template (sections A–K, a starting point — every item can be changed). You can save any checklist as a template (Save as template), and a single item to the item library (Save to the item library).
4. Insert from a source. In the Insert from a source… panel choose a source (built-in sample, template, library, another unit’s base checklist, another campaign’s checklist), tick sections or single items, then Insert.
5. The campaign’s checklist. On the campaign drawer’s Startup checklist tab choose where it starts from: the unit base checklist (default) · a previous campaign (on the same unit; same product first) · a template (by section) · empty — then Create checklist. Afterwards you can add product-specific items.

After a signed gate, a change invalidates the signature

A campaign checklist can be edited freely in the Planned and Start-up phases until the first gate is signed. After that (or from Ramp-up on) a change needs a reason and invalidates the signed gates — they must be signed again, because a signature covers exactly the checklist that was signed. The phase does not step back. The checklist of a closed or withdrawn campaign cannot be edited.

How you know it worked

The sections show as cards; each item shows its kind, the “Required” / “Close before startup” badges and — for a copy — its source. The checklist version is shown at the top of a campaign checklist: a gate signature records it. Required “close before startup” items are gate conditions: until they are done, the gate (by default) cannot be signed.

Common errors

What you see	Why	What to do
“From the unit base checklist” is disabled	The unit has no (or an empty) base checklist.	Create it on the Startup checklists card, or pick another source.
“Give a reason for the change…”	The campaign is live (signed gate / phase after startup).	Enter the reason at the top of the editor — the gates must be signed again afterwards.
“Someone else changed the checklist meanwhile…”	Two people edited at once.	The view has been refreshed — repeat the action.
“The source is not available…”	The source belongs to another site, or was archived.	Pick a source you can see.
“A template with this name already exists.”	Template names are unique in the organisation.	Use another name.
Read-only view	You do not have the edit right.	The production manager (or another permitted user) edits it.

Related

Campaigns: production planAdding, approving and changing a campaign plan.

Campaign phasesStepping, gate signatures, interruptions.