A service contract should remove uncertainty, not bury it in exclusions. Before signing, facility teams should know who answers the call, which components are covered and what happens when a critical entrance fails after hours.
Define the covered system
List every controller, reader, lock, power supply, request-to-exit device, door contact, server, gateway and software subscription. Confirm whether existing third-party equipment is supported or excluded.
Ask the ten operational questions
- What hours are included?
- What starts the response clock?
- Are travel and diagnostic time covered?
- Which parts are excluded?
- Is preventive maintenance included?
- Who handles software and firmware updates?
- How are cybersecurity advisories communicated?
- Is remote support billed separately?
- What documentation is provided after service?
- How can the agreement be ended or transferred?
Separate uptime promises from response promises
A technician arriving in four hours does not guarantee a four-hour repair. Ask about temporary secure-door procedures, stocked parts and escalation. Multi-site buyers should define whether coverage and reporting are consistent across locations.
Protect administrative control
The customer should understand credential databases, administrator accounts, backups and export options. Review the broader access control system architecture before accepting a support plan tied to proprietary components.
Ready to compare practical options? Use the door inventory and operating schedule to compare support coverage on equal terms.
Frequently asked questions
Is preventive maintenance worth it?
It can be valuable for high-cycle doors and critical entrances when inspection scope and documentation are specific.
Should software subscriptions be in the service contract?
They may be, but renewal price, included updates and data access should be itemized.
What is an acceptable response time?
It depends on door criticality, staffed backup procedures, parts availability and operating hours.
