A national facilities maintenance conversation should become specific enough to evaluate location by location. A broad coverage statement is a starting point; the actual request still needs confirmation of the trade, scope, timing and service arrangements involved.
NCRC’s coverage information retains that location-specific review. The checklist below is a suggested way for a multi-location customer to prepare a provider conversation. It is not an acceptance of work or a promise that every service is available everywhere.
Start with a location and trade matrix
List the sites included in the proposed program, the trade or work type needed and the operating constraints already known. Separate current requests from possible future needs.
Ask the provider to identify what is confirmed, what needs further assessment and what is outside the proposed arrangement. A single “national” label does not communicate those distinctions.
| Question | Information to confirm |
|---|---|
| Where is the work? | Site identifier, address and local contact |
| What is needed? | Observed condition and requested outcome |
| Which trade is involved? | Known trade or the need for assessment |
| When can access occur? | Operating hours, restrictions and required coordination |
| What is confirmed? | Scope, availability and the next responsible person |
Understand how a request becomes work
Ask what happens after a request is received. Who assesses the information? What additional facts may be needed? Who confirms the service arrangement, and how will that confirmation reach the customer?
NCRC describes its service approach through assessment, coordination and completion review. The details of a specific job or program still need agreement. A submitted form should not be mistaken for a confirmed dispatch or accepted scope.
Make approval boundaries explicit
Clarify who can authorize the initial work, who handles a proposed scope change and how an unresolved cost or access question is escalated. Where a customer uses a not-to-exceed amount, portal or purchase-order process, confirm how it applies to the proposed arrangement.
Keep these answers in the program record. Do not assume that a process discussed for one location or trade automatically applies to every other site.
Agree what an update should explain
A useful update distinguishes reported, assessed, scheduled, in progress, completed and awaiting review when those states apply to the agreed workflow. Ask what information accompanies each update and who receives it.
The exact labels can vary. The important question is whether the customer can tell what happened, what remains uncertain and who owns the next step. Avoid treating a changed status label as sufficient evidence of a completed repair.
Define the completion evidence
Discuss the records needed to review completion for the work involved. These may include the reported condition, work performed, relevant photos, final observations, exceptions and follow-up ownership, subject to the agreed scope and privacy requirements.
Ask how incomplete work or a recommended next step will appear. A useful record makes an exception visible; it does not force every request into a completed state.
Compare proposals on the same basis
Keep the location matrix, scope assumptions, authorization process, communication expectations and evidence requirements beside each proposal. Identify which answers are confirmed and which are still open.
This makes the comparison inspectable without assuming that the provider with the broadest description is the best fit for every site. Use NCRC’s service conversation to discuss the actual locations and trades. Availability, commitments and the relevant service arrangements remain subject to confirmation.