New development utility connection tracking needs to distinguish four milestones that are often treated as one: physical installation, inspection or testing, utility authorisation, and usable service at the property. A contractor’s report that cables or meters are installed does not establish that electricity has been energised, that other utility services are available or that the building may legally be occupied. Each milestone needs its own evidence, responsible organisation and decision authority.

The coordination problem grows near handover. The fit-out team may finish its works while a utility application is still awaiting a reference number; a meter can be installed while commissioning evidence is incomplete; and the property team may have committed to a move-in date based on an assumed connection. A follow-up plan makes dependencies visible early enough for a project manager to adjust the sequence through authorised channels.

Five utility dependencies before occupation: application, enabling works, inspection, connection and official energisation

Separate construction completion from operational utility service

For a new development, potential utility workstreams include electricity, water, wastewater, gas where applicable, telecoms, access infrastructure and any site-specific energy system. The sequence for each is different and varies with local utility companies, statutory authorities, design requirements and service agreements. Do not assume that inspection rules or energisation permissions are identical across countries, states or building types.

For electricity in particular, create distinct statuses for Installation reported complete, Inspection/testing evidence submitted, Utility authorisation pending, Energisation confirmed by authorised party and Service verified for intended use. The authority to energise normally belongs to the relevant utility or properly authorised professional under the applicable rules. A task-owner phone response cannot grant that authority. U.S. Department of Energy guidance for interconnected energy systems similarly treats utility permission to operate as a separate step after paperwork and checks; specific new-build arrangements need confirmation from the relevant utility.

Create a connection dependency register, not a single handover item

DependencyInformation to trackHuman authority
Application and agreementApplication reference, design status, fees if applicableDeveloper and utility representatives
Onsite enabling worksTrench, duct, riser and plant-room readinessCompetent construction / engineering lead
Inspection or testingRequired reports, outstanding defects, scheduled visitInspector or qualified professional
Meter and connectionInstallation reference, scheduled connection appointmentUtility / authorised installer
Service availabilityOfficial energisation or activation noticeRelevant provider
Occupation prerequisitesOther certificates, access and operating systemsBuilding control / relevant authority

The register should capture the supporting evidence link and the latest verified date, not merely a green status. If the provider has not issued authorisation, the project board must not report that it has. The wording “contractor states meter installed” is more accurate than “power ready” when authorisation and testing remain outstanding.

Find the critical path to occupation

Map utility milestones against elevator commissioning, fire and life-safety systems, ventilation, communications, access controls, final testing, tenant fit-out, furniture delivery and planned occupancy. Some of those systems may require temporary supply for installation and permanent supply for final commissioning. The exact dependency must be established by competent designers and contractors, not assumed from a generic project template.

Consider a hypothetical residential building with six weeks remaining before the intended handover. The electrical subcontractor reports that its distribution works are complete, but the permanent connection appointment has not been confirmed. A site-wide status of 80% complete hides the issue. A dependency-based register shows which final tests and certifications cannot proceed until the authorised connection step occurs, allowing the project manager to seek a verified appointment and inform the client about schedule risk.

Use targeted calls to clear information gaps—not to approve connections

At each planned checkpoint, ask the assigned person which activity has been completed, the evidence or reference supporting it, the next external dependency, the current promised date and the name of the decision-maker. When a utility provides a new appointment date, capture whether it is tentative or formally confirmed. Do not translate a verbal prediction into a contractual promise or confirmed energisation date.

A safe status call to an electrical contractor might ask: “Which installation and test records have been issued?”, “Which documents are still required by the utility?”, and “Who is responsible for the next submission?” The right escalation may be a project engineer contacting the provider directly. It is never an AI caller issuing technical instructions for energising equipment.

Track exceptions using evidence and accountable owners

Create an exception record when the planned date changes, a required certificate is rejected, site access is not ready, or two parties disagree about responsibility. Record Issue, Affected milestone, Evidence missing, Current owner, Escalation contact and Next verified update. If the issue affects occupation, tell the relevant development and property leaders promptly so they can follow the contractual and statutory process.

A particularly common source of confusion is that different teams use “connected” differently. For an installer it may mean the physical cable is connected. For the developer it may mean the building has usable service. For the utility it may mean a formal activation notice has been issued. Agree definitions before progress meetings and keep each milestone separately labelled.

Put the workflow into monday.com without overstating AI capabilities

A monday.com board can group milestones by utility and block of the development, with People, Date, Status, Dependency and Files columns. Suggested fields are Utility type, Provider reference, Responsible owner, Scheduled action, Evidence link, Authorised decision status and Occupancy dependency. Restrict approval-related fields where appropriate and use a named human reviewer for any formal status that requires certification.

AI Workflow Design describes Autoza AI for monday.com as a tool for scheduled calls that capture status and update configured boards. That can support routine owner check-ins; it does not establish direct access to utility systems, independent inspection authority or permission to energise. Related guidance on development permit and inspection follow-up covers how to coordinate other statutory milestones without turning a status update into an approval.

Create a handover evidence pack before making occupancy claims

As the target date approaches, assemble utility agreements, approved test and commissioning reports, provider notices, asset information, maintenance responsibilities, emergency contacts and any handover documents required by contract or law. The project manager should know who accepted each item and where it is stored. Use links and access controls rather than moving sensitive engineering material into call transcripts.

The readiness meeting should ask whether every essential service is documented as available for the intended use, not simply whether suppliers have finished their tasks. If an unresolved issue remains, follow the authorised sign-off and occupation process. No automated status report can replace a statutory occupation certificate, fire-safety approval or utility’s own decision.

For developments managed in monday.com, a scheduled project follow-up review can help determine which routine supplier enquiries may be automated while keeping engineering and legal authorisations with the people responsible.

Frequently asked questions

Does a contractor completion update mean power is live?

No. Physical installation, inspection, provider authorisation and verified service availability may be separate milestones. Require the evidence and confirmation relevant to the utility and jurisdiction.

Who confirms official utility service availability?

The relevant utility provider or other legally authorised party confirms connection, activation or energisation as required. The developer’s project team should retain and verify the corresponding official records.

Which utility delays can hold up occupation?

Depending on the building and local rules, electricity, water, wastewater, fire-system commissioning, lifts, access systems and other required services can affect lawful or practical occupancy. Ask the appropriate professionals and authorities which dependencies apply.

Can AI status calls update the utility connection tracker?

They can collect routine responses and, when configured and authorised, populate mapped task status fields. They cannot grant utility permission, conduct technical inspections or issue occupation approval.

How should a tentative connection appointment appear on the board?

Record it as provisional, with the source, timestamp and owner responsible for confirming it. Do not use the same status as a formally confirmed appointment or completed connection.

Keep utility dependencies visible until occupation

Explore scheduled AI check-ins for monday.com to collect administrative status from contractors and installers, while official energisation and occupation decisions stay with the responsible authorities. See the pricing page or browse more industry workflows.

Related reading