Service and maintenance checklist
What a supported system looks like, and what happens to one that is not. Complete this annually, or the first time you realise nobody is sure who maintains it.
Print it, or fill it in here. Nothing you type is sent anywhere.

Critical — define these first
Nothing else can be scoped, quoted or compared until these are answered.

Conditional — define if these apply
Work through each trigger. If it applies to your site, the item becomes critical.
Optional — worth defining
Not required, but each one makes the next conversation shorter.
Traps to avoid in service and maintenance
Buying hardware without a support pathway, then discovering the supplier has moved on.
Choosing a system only one staff member knows how to operate.
Training one staff member, then rostering a different team on weekends.
Never testing whether the system works for actual users.
Adding connected devices without involving ICT in access, security and documentation.
What happens next
1Anything left blank in the critical section is a gap, not an oversight. It will surface later, usually during installation.
2Bring the completed sheet to a site review. It replaces about half the meeting.
3If a conditional trigger applies and you are unsure how to answer it, that is exactly what the review is for.
This checklist is general guidance. Requirements vary by project, jurisdiction, building classification and approval pathway.
