Uzturēt darba aizsardzības instruktāžas un dokumentāciju aktuālas

Kad izmantot

The yearly cycle for an existing company: review the risk assessment, instruct everyone again, keep the records alive. Not for a new hire's first instruction — that belongs to people.onboard-employee and must happen before the first working day, not at the yearly cycle. Not for an accident — use ops.incident-postmortem; this playbook only records that the incident feeds the risk assessment.

Pirms sāc

• The employee list is current, including anyone who joined or left since last year's round.
• Last year's risk assessment and instruction register are retrievable from the documents module.
• It is decided who counts as "owner" here: the company owner, or a named manager with safety duties.

Ko izpilde pieprasa1

Ceļš8 soļi

1. S1

   Inventory last year's recordsaģents

   List: date of the current risk assessment, date and signatories of the last instruction round, health-check dates and which employees they cover, dates of equipment or premises inspections.

   Izdarīts, kad a one-page inventory exists with a date or "missing" on every line.

2. S2

   Check what changed in the law and in the companyaģents

   In the legal-corpus module, check for amendments to Latvian workplace-safety rules that touch the company's activities. Walk the workplace (or ask the owner to) and list new equipment, substances, workstations or working arrangements since last year.

   Izdarīts, kad a change list exists, each line marked "legal" or "company".

3. S3

   Draft the risk-assessment updateaģents

   Update only what changed: new hazards, changed measures, removed items. Keep the previous version intact as a separate document.

   Izdarīts, kad a draft exists that names what changed and why.

4. S4

   Approve the risk assessmentīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S4 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   The owner reads the draft, questions any measure, and approves.

   Izdarīts, kad the approved version is dated, named with its approver, and stored in the documents module.

5. S5

   Run the instruction roundaģents

   Brief every current employee on the updated risk assessment and their workplace hazards; collect a dated signature per employee in the instruction register. Employees who joined mid-year and were already instructed at onboarding are marked as such with the onboarding date.

   Izdarīts, kad the register shows a signature or a valid earlier date for every person on the employee list.

6. S6

   Schedule health checksaģents

   For employees whose work requires obligatory health checks, set the next examination date per person. ⚠ jāpārbauda which roles require them and at what interval — Cabinet of Ministers regulations (likumi.lv).

   Izdarīts, kad every covered employee has a next-check date, and bookings or reminders exist for each.

7. S7

   Verify against the listaģents

   Compare the employee list against: instruction signatures, health-check dates, and any other recurring obligation found in S1. Every gap gets a task with a deadline.

   Izdarīts, kad the gap list is empty or every gap has a named task.

8. S8

   Archive and arm next yearaģents

   Store this year's risk assessment, register and schedules in the documents module under the retention rules the company uses; record the date next year's run must start (before this year's instruction cycle expires).

   Izdarīts, kad a next-year trigger or task exists with that date.

Pārbaudes — kā zinām, ka izdevās

• The approved risk assessment is dated this cycle and names its approver — read the date back from the
• Instruction register: number of signatures equals number of current employees; each signature is dated
• Every employee requiring a health check has a next date, and none is in the past.
• The previous risk assessment version still exists — the update did not overwrite it.

Ja noiet greizi

Ko atstāj katrs solis

1. S1a one-page inventory exists with a date or "missing" on every line.
2. S2a change list exists, each line marked "legal" or "company".
3. S3a draft exists that names what changed and why.
4. S4the approved version is dated, named with its approver, and stored in the documents module.
5. S5the register shows a signature or a valid earlier date for every person on the employee list.
6. S6every covered employee has a next-check date, and bookings or reminders exist for each.
7. S7the gap list is empty or every gap has a named task.
8. S8a next-year trigger or task exists with that date.

Ko saglabāt

Inventory from S1 · change list from S2 · approved risk assessment (version, date, approver) · instruction register for this year · health-check schedule per employee · the S7 gap list · the next-year trigger date.

Kā šī procedūra uzlabojas

After every 2 cycles ask: how long from trigger to approved assessment, and did S4 wait? Did anyone join between cycles and fall outside both onboarding and the yearly round? Did any health check slip past its date? A new version changes the step that caused the wait or the gap, and says so in its change note.