Check Whether We Can Support Your Building and Request
- 01 · Current issue
Visitors do not know whether BAS can support their building, location, urgency, or system.
- 02 · What is affected
A poorly matched request wastes scheduling time and can leave a building problem waiting on the wrong geography, skill set, or service class.
- 03 · Support path
A local-only workflow that records location, building type, consequence, access, and required service class for human coverage review.
- 04 · Information that helps
Compare the agreed scope with field findings, test records, completed work, open items, and the named next owner.
Begin with operating impact, then add only the technical facts needed to choose and confirm the next step.
A human review confirms scope, service area, access, authority, timing, and responsibility before work is scheduled.
Support boundary: Availability depends on project fit, service area, access, staffing, authority, and a written agreement.

Representative technical collaboration—not a building automation system (BAS) team or customer meeting.
Connect the building condition to qualified field work, measured checks, documented limits, and the next owner action.
Share the condition, consequence, and safe access details
A human review confirms scope, service area, access, authority, timing, and responsibility before work is scheduled.
Check immediate responsibility
Describe the building problem, consequence, access, history, and available evidence.
Gather useful history
Qualify scope, geography, authority, safety boundaries, and the right service path.
Route the next action
Perform the agreed work and hand over findings, tests, open items, and next responsibility.
A clearer issue record for the people doing the work
Keep timestamps, symptoms, recent changes, access limits, and open responsibility together.
Defined scope, prerequisites, and exclusions
Test and evidence record appropriate to the service
Closeout, open items, and ownership of the next action
Give the support team enough context to choose the next safe action
Compare the agreed scope with field findings, test records, completed work, open items, and the named next owner.
- Geography has not been publicly committed
- Urgency must be separated from promised response
- Site and access conditions affect dispatch

Representative field-service teamwork—not building automation system (BAS) employees or a building automation system (BAS) site.
Support boundary
Availability depends on project fit, service area, access, staffing, authority, and a written agreement.
Reach the right support path with less back-and-forth
Useful context helps the service conversation start closer to the actual problem.
Get an honest fit decision without relying on unverified nationwide or response-time claims.
A documented scope and test plan reduce blind work and make responsibility clear before the visit.
Closeout evidence shows what was tested, changed, verified, and still needs attention.
Service qualification
Coverage is not assumed. Prepare location, consequence, access, and service needs for human qualification.


