Hi Rainier Swart! It's a bit hard to suggest recommendations without knowing a bit more about what your maintenance process looks like/how you envision it to look. I am curious, however, to know what the limitations with processes that you found were? We're currently working on some major improvements to the processes tool, so I'd love to hear your thoughts here.

Other methods you could potentially try:

KB articles
- We have a decent amount of clients who forego using processes and just document everything within our KBs.
- There's obviously various ways you could set this up, but I've definitely seen customers using them for a sort of \"maintenance playbook\". You could create a standardized 'baseline', convert it into a template and then customize it for each client with any specific needs.
- KBs give a bit more of that 'freeform' documentation, but they do lose out on a bit of the 'task-tracking' abilities that processes have.
Combo KB articles with processes.
- Create a sort of maintenance playbook/documentation page, as mentioned above, but also include various processes for each task category.
- The benefit of using processes, is that there is always a clear record of what tasks have been completed for a particular company or asset, and by who. Anytime someone needs to check back on the status, they have a method and visibility to do so.

Hopefully this makes sense, but feel free to reach out with further questions!

Maintenance processes