For administrators#

This guide covers setting up and running Carrotz: the structure the work rests on, the automation that creates the jobs, and control over who sees what.

Most of it is done on a computer.

The order that works#

Setting Carrotz up from scratch, it pays to work in this order — each step builds on the previous one:

1. Locations — where things are
2. Objects — what is to be looked after
3. Checklists — how the work is to be done
4. Maintenance plans — when it should happen
5. Measuring points and triggers — condition-based triggering
6. Users and permissions — who does what

Then, as needed:

• JSA and risk assessment
• Documents and signing
• Planning, projects and hours
• Reports and statistics

The structure you build in steps 1–2 is the hardest to change later, because all history hangs off it. Spend a little extra time there. Checklists and plans can be changed at any point.