Home/One Missing Gate Code Can Derail a Roof Visit. Ask These 7 Questions First.

One Missing Gate Code Can Derail a Roof Visit. Ask These 7 Questions First.

The truck is ready. The appointment is on the calendar. Then the crew reaches a locked gate, the contact on the work order is unavailable, and nobody knows which entrance the property manager meant.

That is a hypothetical scene, but it is a useful test for your next dispatch: could someone who did not take the original call explain exactly how the visit is supposed to begin?

A scheduled appointment leaves several practical questions unanswered. Use the seven questions below as a suggested administrative preflight for a commercial roofing visit. Adapt them to the property, the agreed scope and your company’s procedures. The goal is a clear arrival plan, with an owner for anything still unresolved.

1. Are we talking about the same building?

Start with the property name, street address and the specific building or area involved. On a campus or multi-building property, ask the customer how they identify the location. A general account address and a service entrance may be different places.

Record the customer’s description in the work order. If an approved site map or marked image is available, connect it to the same record. Keep the original description alongside your clarification rather than silently replacing it with a guess.

A useful confirmation is specific: “Building C, north service entrance, reporting to the facilities office.” Treat that as an example of a clear instruction, not a detail to copy into a real customer’s job.

2. Who can actually help the crew arrive?

Ask who the arrival contact is, how that person should be reached and whether they expect to be available during the agreed window. Distinguish the person who requested the work from the person responsible for access.

Then agree on an escalation contact or next step if the first person is unavailable. Avoid assuming that a number in an old email is still the right one. Record when and with whom you confirmed the arrangement.

Share contact details only through your approved work systems and with the people who need them. A useful dispatch record should not become a public directory of a customer’s staff.

3. Which entrance, parking area and check-in process apply?

Ask the site contact to explain the arrival sequence: entrance, vehicle parking, reception or security check-in, and any site-issued visitor arrangements. Clarify whether an escort or a separately arranged access step is expected.

If the customer provides a gate code or other access credential, follow the customer’s instructions and your company’s approved process for handling it. Keep credentials out of public photos, broadly shared notes and marketing material.

Do not improvise when the expected access arrangement fails. Agree in advance on whom the crew should contact and who can authorize a change to the arrival plan.

4. What time has actually been agreed?

Confirm the date and arrival window with the relevant site contact. Include the time zone when people are coordinating across regions. Ask whether the property has check-in hours, an escort appointment or other timing restrictions that affect the visit.

Keep the difference between a proposed time and a confirmed arrangement visible. “Requested for Tuesday morning” should not quietly turn into “Customer confirmed Tuesday at eight.”

When the plan changes, update the work record and use your normal acknowledgment process with the affected people. If confirmation is missing, leave that item open and assign someone to obtain it.

5. What is the crew being asked to do?

Write down the agreed purpose of the visit in plain language. Is this an initial assessment, a planned inspection or work within an already approved scope? Keep customer-reported symptoms separate from a diagnosis that has not been established.

Ask what background information the team should review before arrival: the original request, relevant prior work, approved photos or a customer-provided location reference. Flag missing information as missing.

Also identify who handles questions about additional work. Do not turn an access conversation into an implied approval for a repair, a price or a change in scope.

6. What site conditions need qualified review?

Invite the site contact to flag known restrictions or changes relevant to the visit, and route that information through your established planning process. Examples to ask about include restricted areas, other contractors working on site and customer-controlled access arrangements.

This checklist does not determine whether roof access or any task is safe. Your qualified personnel must make the required assessments and follow applicable requirements and company procedures. For authoritative background, consult OSHA’s construction fall-prevention resources and the rules relevant to the work and jurisdiction.

Keep unresolved safety or access concerns visible for the responsible person. A calendar entry, a customer assurance or a checked administrative box is not a substitute for that review.

7. What happens if the plan does not match the site?

Decide who the crew should contact if the entrance is locked, the escort is missing or the location description does not match. Agree on how the team reports the problem and who decides the next step.

A simple exception note can capture the arrival time, the issue encountered, the person contacted and the next instruction received. Use neutral wording. Record what happened without assigning blame or inventing a reason for someone’s absence.

Afterward, have the appropriate owner update reusable property information. Preserve any visit-specific limitation so that a temporary arrangement does not accidentally become a permanent instruction.

Give every open question an owner

Try a compact preflight record: property and building; arrival contact; entrance and check-in; confirmed window; agreed purpose; conditions requiring review; and exception contact. Add the confirmer, confirmation date and an owner for each open item.

Use it as a conversation aid. Do not label an unanswered item complete simply because the dispatch screen needs to look tidy. Your team can decide how unresolved items affect dispatch under its own procedures.

Arrival preparation is one part of the service workflow. For the other end of the visit, read our service-ticket closeout checklist. To discuss your team’s workflow with Centerpoint Connect, request a demo.

Related Posts

Scroll to Top