Lock and tag register

Register

Which lock or tag exists, who has it, and what your periodic inspection found.

Custody, and a place to write down a periodic inspection

Two ordinary problems: nobody knows how many locks there are or who has them, and the periodic inspection somebody carried out lives on a sheet in a drawer. This register answers the first and gives the second a dated home, per device.

It is not an energy control procedure

This matters enough to say plainly. Your written procedure for a machine — how it is isolated, in what order, how stored energy is released, how isolation is verified, who is authorized to do it — is a specific document about specific equipment, and it is the thing that keeps people alive. It is not here, and this register does not stand in for it.

There is no isolation sequence field, no verification step and no authorization line in this tool, and there is no field for one. If you are looking for somewhere to write your procedure, this is not it.

No inspection frequency is stated

The register has a field for the date you recorded a periodic inspection and what it found. It does not tell you how often that is done, nothing falls due, and no reminder exists. What your program requires comes from your program and from the rules you operate under.

Kept alongside: Hot work permit · Attendant log · PPE & equipment issue register

A custody register for lockout/tagout locks and tags, kept per site on your device. IT IS NOT AN ENERGY CONTROL PROCEDURE: there is no isolation sequence, no stored-energy step, no verification procedure and no authorization here, and no field for any of them — those belong in your own written procedure for that machine. CompliMaint states no inspection frequency and makes no determination that any program complies with anything. Everything runs on your device.

Questions people ask

Can I write my lockout procedure in this?
No, and you should not try. An energy control procedure is specific to a machine and describes how it is isolated, in what order, how stored energy is released and how isolation is verified. There is no field for any of that here, deliberately, because a procedure kept as a note on a lock register is a procedure nobody will find when it matters.
How often does a periodic inspection have to be done?
CompliMaint does not say. There is a field for the date you carried one out and what it found; nothing falls due, nothing is calculated and no reminder exists. What your program requires comes from your program and the rules you operate under.
What does the register actually answer?
Which devices exist, who holds each one, when it was issued, whether it came back, where it is kept, and what your last recorded inspection of it found. Those are the questions a lock register is for.
Does it decide whether my program is compliant?
No. It makes no compliance determination of any kind. It is a list of devices and dates you typed.
Does anything leave the device?
No. Rows stay in this browser. No account is needed and no upload.