Use this worksheet to turn a broad coverage statement into a site-specific service schedule. For each Illinois location, identify the systems supported, operating hours, access conditions and incidents that need onsite work. Ask prospective providers to document what they commit to at that address rather than assuming a service-area listing establishes a response guarantee.
Purpose and limitations
This is a coverage-planning framework, not a map of confirmed provider capacity or measured response times. Nexus service availability, dispatch arrangements and commitments must be confirmed for the actual site and proposed agreement.
How to use this worksheet
- Build one record per location, with the address, local contact, operating hours and critical systems.
- Describe representative incidents and agree which party owns diagnosis, remote action, dispatch and escalation.
- Request written coverage terms and record assumptions, exclusions and evidence still needed before acceptance.
Define coverage by task, not only geography
Separate remote monitoring, remote troubleshooting, onsite labor and equipment replacement. A provider may offer different coverage for each activity, system or time period. Identify carrier and manufacturer responsibilities explicitly so a location is not treated as fully covered merely because someone receives its alerts.
- Covered sites, devices and supported applications
- Business-hours, after-hours and planned-maintenance arrangements
- Included onsite work, exclusions and authorization requirements
Distinguish response from restoration
Ask how the agreement defines acknowledgment, remote response, dispatch, arrival and restoration. Record the priority criteria, measurement start point and any exclusions for each commitment. Do not substitute a general marketing response claim for the terms that apply to your location and incident type.
- Who declares incident priority and who may change it
- How customers receive status and escalate an unresolved incident
- Which dependencies can delay restoration and who coordinates them
Prepare the site for an effective visit
Document building access, authorized contacts, equipment locations and approved work windows. Identify special access or operational coordination that a technician must arrange. Keep current diagrams and asset records available through an approved channel; do not place passwords, entry codes or other secrets in a widely shared worksheet.
- Site contact, escort and access-approval responsibilities
- Equipment records, diagrams and service history
- Spare-parts ownership and customer or third-party prerequisites
Review the operating evidence
Ask for the reporting and review process that will show whether the agreed service is being delivered. Use incident records from your own agreement to examine recurring issues and unresolved dependencies. For a multi-site portfolio, retain location-level exceptions rather than averaging away differences in operating hours or support coverage.
- Reporting frequency, incident fields and review owner
- Process for changing coverage when a site or system changes
- Renewal, transition and escalation-contact review dates
Your planning worksheet
- Site and operations
- Record the Illinois address, site contact, operating hours and access-approval owner.
- Covered systems
- List devices and applications, with provider, customer and third-party boundaries.
- Representative incidents
- Describe priority, expected impact, remote actions and likely onsite requirements.
- Written commitments
- Record response, dispatch or restoration terms exactly as proposed, including definitions and exclusions.
- Onsite preparation
- Identify approved records, equipment locations, work windows, escorts and spare-parts arrangements; do not enter secrets.
- Escalation and reporting
- Name the escalation owner, status channel, reporting interval and review participants.
- Coverage gaps
- List unresolved assumptions and the evidence or agreement change needed to close each gap.