Asset Type Requirements

Want to save time and make your asset checks more consistent? Then you'll love our Asset Type Requirements feature.

Instead of adding document or checklist requirements to individual assets one at a time, we can set rules based on the asset type.

We highly recommend using this feature if you've got multiple assets of the same type. Get in touch with your requirements and we can set this up for you.

Here are some examples of Asset Type Requirements

Type Document Requirement(s) Checklist Requirement(s)

Ladders - Monthly ladder check

Security (eg CCTV, alarms) Annual service -

Fork Lift Trucks 12 month service, LOLER Daily Pre use check

Racking Annual external inspection Monthly Visual Inspection

Roller Shutter Doors Annual service -

Gas Annual Gas safe -

Need more examples? Just give us a shout.

Apart from being a huge time saver, when a type requirement is added you will see tasks automatically generated to provide the document or complete the checklist.  The same goes for new assets – tasks are generated straight away so nothing gets missed.

Using Asset Type Requirements doesn't preclude you from doing things on a 'per asset' basis. You can still add documents and checklist requirements to individual assets where Asset Type Requirements wouldn't work.

A couple of things to remember:

1.  If you add a type requirement, it applies to all assets in that type. You might want to consider adding more types (our system can handle multiple types per asset) or splitting a type by adding a new one and adding assets to it.

2. If you've already added the documents or checklists manually to assets, you'll need to archive them, even if they have the same name as the type requirements.

Need help setting up type requirements? Get in touch!

Changing an Asset's Type when it has Asset Type Requirements

When you change an asset type, you'll need to deal with any Asset Type Requirements the asset had before. 

After changing the asset type you will need to click on 'Save & Process':

You'll see a message: and then you can choose whether to keep or archive each requirement based on what's still relevant: