Capability template for health, safety and environment
Temporary change register
For a site or operations manager with temporary changes to equipment, layout or process still in place: a register of every change with its expiry date, the checks still outstanding and the procedures and training it touches, ready for the competent person who decides what happens next.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
Every temporary change on the site sits on one list, in the same shape each time. For each one the manager can see when it was made, who approved it, when it was meant to end, which checks have been done and which have not, and which procedures and briefings it affects. The ones that have run past their date come first, then those with no date at all, then those about to expire.
A temporary change rarely fails loudly. It gets a date, the date passes, and the guard, the rerouted aisle or the shortened cycle becomes how the site works. The register puts the date, the days past it and the unfinished checks in front of the person who can act, before the change quietly becomes permanent.
A competent person approves, extends or ends each change. The register decides nothing. It does not say a change is safe to continue, it does not extend an expiry, and it does not close a change; it lays out the facts and leaves the choice, by name, with the person who holds it.
Who starts the work, and when
The site manager, operations manager or the person who keeps the change log starts it on the site's agreed review rhythm, monthly for example, and again before an audit, a visit from an inspector or a change of site leadership. They bring the log and the records of checks, procedure updates and briefings. The competent person, such as the site engineer or the safety lead, reads the result and makes each decision.
What they supply
- The change log, one row per change, with set column headers: the change number, a description, its type (equipment, layout or process), the area, the date it was made, the owner, who approved it and when, the expiry date, how many times it has been extended, and whether it is open, extended or ended.
- The item records, one row per check, procedure update or briefing a change needs, with its due date, the date it was done and a reference to the evidence.
- The settings: the review date, the site, who decides, how far ahead to look for expiries, how long a change may stay in place before the register flags it, and how many extensions count as too many.
What comes out
A register in a fixed order: changes past their expiry, changes with no expiry date, changes expiring soon, changes in date with items outstanding, changes in date with nothing outstanding, ended changes with items still open, ended changes with nothing open, and any rows that could not be read. Each change shows its dates, its approval, how many times it has been extended, and every item with its state. Each change that needs a decision names who decides. The register closes with numbered questions for the facts the files left out, such as a missing approver or an expiry written as "after the audit".
It is distinct from preventive maintenance plan, which plans the routine upkeep of equipment on a calendar. This one follows the departures from normal: what was changed for now and what has to happen before it ends.
An invented example
Illustrative example with invented data. The site, the changes, the dates and the evidence references below are all invented. The site is an invented 90-person plastics moulding and packing site, called the Site here. The site manager runs the review; the site engineer is its competent person and decides each change. People are referred to by role.
The inputs come first, in full, so the template can be run on them. The register follows.
The inputs
1. Settings (typed by the site manager)
Site: the Site, moulding hall, packing hall, warehouse and yard
Review date: Monday 2026-12-07
Prepared for: the site manager
Decides each change: the site engineer
Expiring soon means: expiry within 30 days of the review date
In place too long: more than 180 days
Extended too often: 2 or more extensions
2. Change log (export)
change_id,description,type,area,date_made,owner,approved_by,approval_date,expiry_date,extension_count,status
TC-101,"Conveyor C3 run at reduced speed with a temporary clear guard panel fitted",Equipment,Packing hall,2026-08-17,maintenance supervisor,site engineer,2026-08-17,2026-10-31,0,open
TC-102,"Two pallet-stacking bays moved into the east walkway, leaving a marked route",Layout,East aisle,2026-11-02,warehouse supervisor,site engineer,2026-11-02,2026-12-14,0,open
TC-103,"Mould cooling time shortened from 20 to 15 minutes on Line 1",Process,Moulding hall,2026-06-01,production manager,,,2026-07-31,0,open
TC-104,"Chiller pump replaced with a different model",Equipment,Plant room,2026-03-23,maintenance supervisor,site engineer,2026-03-23,,0,open
TC-105,"Additives weighed by hand while the dosing unit is repaired",Process,Moulding hall,2026-11-23,production manager,site engineer,2026-11-23,2027-01-15,0,open
TC-106,"Temporary cabin placed in the yard for visiting inspectors",Layout,Yard,2026-10-19,facilities coordinator,site engineer,2026-10-19,2027-01-31,0,open
TC-107,"Forklift charger moved to the loading bay",Equipment,Warehouse,2026-10-05,warehouse supervisor,site engineer,2026-10-05,2026-12-03,0,ended
TC-108,"Packing line 2 layout moved for a trial run",Layout,Packing hall,2026-09-14,production manager,site engineer,2026-09-14,2026-11-15,0,ended
TC-109,"Compressor discharge pressure setpoint lowered",Process,Plant room,2026-02-09,maintenance supervisor,site engineer,2026-02-09,2026-12-04,2,open
TC-110,"Loading dock door 4 closed and traffic redirected to door 5",Layout,Dock,2026-11-16,warehouse supervisor,site engineer,2026-11-16,after the audit,0,open
3. Item records (export)
change_id,item,kind,due_date,done_date,evidence
TC-101,Fit permanent guard panel,check,2026-10-31,,
TC-101,Update SOP-14 for reduced speed,procedure,2026-08-24,2026-08-20,signed SOP-14 rev C
TC-101,Brief night shift on reduced speed,training,2026-08-31,2026-08-24,briefing roster 24 Aug
TC-102,Measure clear walkway width,check,2026-12-04,,
TC-102,Update fire-route plan,procedure,2026-12-11,2026-12-02,
TC-102,Brief supervisors on the new route,training,2026-12-11,,
TC-103,Compare part quality at 15-minute cooling,check,2026-06-30,2026-06-26,QA sheet 26 June
TC-103,Update moulding procedure MP-07,procedure,2026-06-15,,
TC-104,Update maintenance procedure and spare list,procedure,2026-04-30,,
TC-104,Train maintenance team on the new pump,training,2026-04-30,2026-05-06,sign-in sheet 6 May
TC-105,Check dust extraction at the weighing station,check,2026-11-27,2026-11-24,check sheet 24 Nov
TC-105,Brief operators on manual weighing steps,training,2026-11-27,2026-11-24,roster 24 Nov
TC-106,Test fire alarm link to the cabin,check,2026-12-20,,
TC-106,Add cabin to the evacuation plan,procedure,2026-11-02,2026-11-02,plan rev 7
TC-107,Confirm original charging bay floor marking restored,check,2026-12-04,,
TC-107,Brief forklift drivers on return to the original bay,training,2026-12-04,2026-12-03,roster 3 Dec
TC-108,Confirm original line layout restored,check,2026-11-15,2026-11-14,photo 14 Nov
TC-109,Inspection of the pressure system by the competent person,check,2026-06-30,2026-06-12,report PS-26-3
TC-109,Update compressed-air operating note,procedure,2026-03-01,2026-03-02,note rev 2
TC-111,Re-test emergency stop,check,2026-12-01,,
The register
TEMPORARY CHANGE REGISTER: the Site, review as of 2026-12-07
For: the site manager. Prepared from the change log and item records supplied. Nothing here approves, extends or ends a change.
Counts: 7 open changes: 3 expired, 1 with no expiry date, 1 expiring within 30 days, 1 in date with items outstanding or not recorded, 1 in date with nothing outstanding. 2 ended changes: 1 with items still open, 1 with nothing open. Flags: approval not recorded 1; in place over 180 days 3; extended 2 or more times 1; no items recorded 0. Rows not read: 2.
- Expired: 3
TC-103 Mould cooling time shortened from 20 to 15 minutes on Line 1. Process, Moulding hall. Owner production manager. Made 2026-06-01 (189 days ago). Approval: not recorded. Expired 2026-07-31 (129 days ago). Extended 0 times. Flags: approval not recorded; in place over 180 days. Items: Compare part quality at 15-minute cooling (check): done 2026-06-26, evidence QA sheet 26 June. Update moulding procedure MP-07 (procedure): due 2026-06-15, 175 days overdue. Decision: the site engineer chooses whether to restore, extend or reassess. Nothing is recorded as decided.
TC-101 Conveyor C3 run at reduced speed with a temporary clear guard panel fitted. Equipment, Packing hall. Owner maintenance supervisor. Made 2026-08-17 (112 days ago). Approval: site engineer on 2026-08-17. Expired 2026-10-31 (37 days ago). Extended 0 times. Flags: none. Items: Fit permanent guard panel (check): due 2026-10-31, 37 days overdue. Update SOP-14 for reduced speed (procedure): done 2026-08-20, evidence signed SOP-14 rev C. Brief night shift on reduced speed (training): done 2026-08-24, evidence briefing roster 24 Aug. Decision: the site engineer chooses whether to restore, extend or reassess. Nothing is recorded as decided.
TC-109 Compressor discharge pressure setpoint lowered. Process, Plant room. Owner maintenance supervisor. Made 2026-02-09 (301 days ago). Approval: site engineer on 2026-02-09. Expired 2026-12-04 (3 days ago). Extended 2 times. Flags: in place over 180 days; extended 2 or more times. Items: Inspection of the pressure system by the competent person (check): done 2026-06-12, evidence report PS-26-3. Update compressed-air operating note (procedure): done 2026-03-02, evidence note rev 2. Decision: the site engineer chooses whether to restore, extend or reassess. Nothing is recorded as decided.
- No expiry date recorded: 1
TC-104 Chiller pump replaced with a different model. Equipment, Plant room. Owner maintenance supervisor. Made 2026-03-23 (259 days ago). Approval: site engineer on 2026-03-23. No expiry date recorded. Extended 0 times. Flags: in place over 180 days. Items: Update maintenance procedure and spare list (procedure): due 2026-04-30, 221 days overdue. Train maintenance team on the new pump (training): done 2026-05-06, evidence sign-in sheet 6 May. Decision: the site engineer chooses whether to restore, extend or reassess. Nothing is recorded as decided.
- Expiring within 30 days: 1
TC-102 Two pallet-stacking bays moved into the east walkway, leaving a marked route. Layout, East aisle. Owner warehouse supervisor. Made 2026-11-02 (35 days ago). Approval: site engineer on 2026-11-02. Expires 2026-12-14 (in 7 days). Extended 0 times. Flags: none. Items: Measure clear walkway width (check): due 2026-12-04, 3 days overdue. Update fire-route plan (procedure): done 2026-12-02, evidence not supplied. Brief supervisors on the new route (training): due 2026-12-11, in 4 days. Decision: the site engineer chooses whether to restore, extend or reassess. Nothing is recorded as decided.
- In date, items outstanding or not recorded: 1
TC-106 Temporary cabin placed in the yard for visiting inspectors. Layout, Yard. Owner facilities coordinator. Made 2026-10-19 (49 days ago). Approval: site engineer on 2026-10-19. Expires 2027-01-31 (in 55 days). Extended 0 times. Flags: none. Items: Test fire alarm link to the cabin (check): due 2026-12-20, in 13 days. Add cabin to the evacuation plan (procedure): done 2026-11-02, evidence plan rev 7.
- In date, nothing outstanding: 1
TC-105 Additives weighed by hand while the dosing unit is repaired. Expires 2027-01-15. 2 of 2 items done with evidence.
- Ended, items still open: 1
TC-107 Forklift charger moved to the loading bay. Ended. Owner warehouse supervisor. Items: Confirm original charging bay floor marking restored (check): due 2026-12-04, 3 days overdue. Brief forklift drivers on return to the original bay (training): done 2026-12-03, evidence roster 3 Dec.
- Ended, nothing open: 1
TC-108 Packing line 2 layout moved for a trial run. 1 of 1 items done with evidence.
- Rows not read: 2
Change log, TC-110: expiry_date "after the audit" is not a date. Item records, TC-111: no matching change in the change log.
Questions: 5
- TC-103: approval not recorded (approved_by and approval_date are blank). The production manager, who owns the change, can answer.
- TC-104: expiry date not recorded. The maintenance supervisor, who owns the change, can answer.
- TC-102: "Update fire-route plan" is shown as done on 2026-12-02 with no evidence reference. The warehouse supervisor, who owns the change, can answer.
- TC-110: row not read because the expiry date "after the audit" is not a date. The warehouse supervisor, who owns the change, can answer.
- TC-111: the item "Re-test emergency stop" matches no change in the log. The settings name nobody for the item records, so the site manager, for whom the register is prepared, can answer.
Every date and count traces to the change log and item records supplied, with the review date as the reference. The register changes no records and sends nothing.
Where it fits
- Health, safety and environment, where a change that outlives its approval is exactly what a competent person wants to see first.
- Operations and process improvement, where the manager who keeps the site running is the one who makes the temporary fixes.
- Manufacturing, where a line runs on a workaround through the next order.
- Construction, where site layouts, access routes and temporary works change week by week.
- Logistics and trade, where a closed dock door or a moved charging bay becomes the new routine.
- Energy, where a changed setting or a bridged arrangement needs an owner and an end.
- Established businesses, where a site has accumulated years of fixes that nobody listed.
- Growth & scaling, when new volume forces layout and process changes faster than the paperwork follows.
What has to change for your company
Name who decides: the competent person for your site, and what your own rules say they must confirm. Set your review rhythm, how many days ahead counts as "expiring soon", and how long a change may stay in place before it is questioned. Decide what your site counts as a change, and which of your documents the item records should point to. Agree where the log lives and who keeps it current, because the register is only as good as that file. It runs in ChatGPT, Claude, Copilot or Gemini from the exports you supply, with no connection to any system. Which changes need formal assessment, and what that assessment holds, is set by your own procedures and by the rules that apply to your site; the register does not say. Incident investigation and corrective actions covers what to do when a change is linked to something that went wrong, and site safety induction pack covers what newcomers are told about the site as it now stands.
What has been checked
Fully Powered AI wrote this capability template in its own words. It was editorially reviewed on 10 November 2026. It was tried on its invented example on 10 November 2026; the record is published with it, and lists the edits made afterward that have not been run again. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past month of your own log that the site manager already knows, plus hard cases written in advance, each with its expected behavior: a renamed column, an expiry that is not a date, a change with no approver, an extension that was never recorded, a check marked done with no evidence, an ended change with a restoration check still open. The site manager checks every date and count against the log, and the competent person confirms every decision before anyone relies on it. Pilot acceptance-test preparation builds that test set, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: