, home
Customer access Request an enterprise demo
Request an enterprise demo Customer access

Construction & infrastructure / APPLICATION BLUEPRINT

Utility Diversion & Construction Access Coordination

Coordinates utility diversions and construction access around conflicting services.

Start generatingExplore illustrative interface

12 workspace menus · 12 business workflows · 5 role profiles

Application blueprint only. This is a proposed design, not a deployed or production-tested system. Screens and sample figures are illustrative; workflows, business rules, approvals, permissions and integrations require confirmation before build.

Designed for project coordinators and the responsible business owners

Utility Diversion & Construction Access Coordination workspace interface preview; illustrative records and figures.
Utility Diversion & Construction Access Coordination — operational workspaceIllustrative interface · Sample dataView full interface →

Explore an illustrative interface.

Illustrative workspace and record review. Select a concept screen to inspect it in full.

Utility Diversion & Construction Access Coordination workspace interface preview; illustrative records and figures.
Utility Diversion & Construction Access Coordination — operational workspaceIllustrative interface · Sample dataView full interface →
Utility Diversion & Construction Access Coordination record interface preview; illustrative records and figures.
Utility Diversion & Construction Access Coordination — record and workflow reviewIllustrative interface · Sample dataView full interface →

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Project / work packagePeriodAssigned teamReview state

Dashboard measures

  • Active delivery records
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Coordinates utility diversions and construction access around conflicting services. Tracks utility-owner designs, approved scopes and contractor dependencies, records authorised access arrangements and confirms completed diversions, with updated service documentation and outstanding handover requirements.

Operations

Operational overview

Review the work position and priority actions.

Utility diversions

Coordinate utility diversions with assigned responsibilities, linked records and review history.

Construction access around conflicting services

Coordinate construction access around conflicting services with assigned responsibilities, linked records and review history.

Utility-owner designs

Coordinate utility-owner designs with assigned responsibilities, linked records and review history.

Scopes

Coordinate scopes with assigned responsibilities, linked records and review history.

Contractor dependencies

Coordinate contractor dependencies with assigned responsibilities, linked records and review history.

Access arrangements

Coordinate access arrangements with assigned responsibilities, linked records and review history.

Completed diversions

Coordinate completed diversions with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Define scope and responsibilities

Establish the scope of utility diversions, capture the required records and assign the accountable team.

02

Coordinate delivery and evidence

Coordinate construction access around conflicting services, utility-owner designs, with linked evidence and visible outstanding actions.

03

Review progress and exceptions

Review the relevant conditions and exceptions. Record the authorised outcome and its supporting evidence.

04

Accept outcomes and follow-up

Confirm the resulting records and handovers. Track remaining obligations, later changes and follow-up actions.

Business workflows

Select a workflow to review the steps, responsibilities, approval and exception handling.

01 · Coordinate utility diversions

Coordinate utility diversions within Utility Diversion and Construction Access Coordination.

Trigger
Utility diversions requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register utility diversions and its operating scope
  • Coordinate the required specialist and business review
  • Accept the release version and permitted recipients
  • Record distribution, acknowledgement and later revisions

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Content conflicts, missing review or a changed recipient permission prevents release.

Outcome
An accepted content version with distribution and revision history.

02 · Coordinate construction access around conflicting services

Coordinate construction access around conflicting services within Utility Diversion and Construction Access Coordination.

Trigger
Construction access around conflicting services requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register construction access around conflicting services and its operating scope
  • Check permitted purpose, prerequisites and authority
  • Record the delegated approval or refusal
  • Track term, withdrawal and later changes

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Authority is missing, permission changes or the requested purpose exceeds the accepted scope.

Outcome
A scoped permission or recorded refusal, its conditions and review history.

03 · Track utility-owner designs

Coordinate utility-owner designs within Utility Diversion and Construction Access Coordination.

Trigger
Utility-owner designs requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register utility-owner designs and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

04 · Track approved scopes

Coordinate approved scopes within Utility Diversion and Construction Access Coordination.

Trigger
Approved scopes requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register approved scopes and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

05 · Track contractor dependencies

Coordinate contractor dependencies within Utility Diversion and Construction Access Coordination.

Trigger
Contractor dependencies requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register contractor dependencies and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

06 · Record authorised access arrangements

Coordinate authorised access arrangements within Utility Diversion and Construction Access Coordination.

Trigger
Authorised access arrangements requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register authorised access arrangements and its operating scope
  • Check permitted purpose, prerequisites and authority
  • Record the delegated approval or refusal
  • Track term, withdrawal and later changes

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Authority is missing, permission changes or the requested purpose exceeds the accepted scope.

Outcome
A scoped permission or recorded refusal, its conditions and review history.

07 · Confirm completed diversions

Coordinate completed diversions within Utility Diversion and Construction Access Coordination.

Trigger
Completed diversions requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register completed diversions and its operating scope
  • Coordinate the required specialist and business review
  • Accept the release version and permitted recipients
  • Record distribution, acknowledgement and later revisions

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Content conflicts, missing review or a changed recipient permission prevents release.

Outcome
An accepted content version with distribution and revision history.

08 · Register the operating requirement

Coordinate operating requirement within Utility Diversion and Construction Access Coordination.

Trigger
Operating requirement requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register operating requirement and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

09 · Resolve operating exceptions

Coordinate operating exceptions within Utility Diversion and Construction Access Coordination.

Trigger
Operating exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register operating exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

10 · Verify completion and follow-up

Coordinate completion and follow-up within Utility Diversion and Construction Access Coordination.

Trigger
Completion and follow-up requires a new record, an agreed review or a controlled change.

Responsible role
Commercial reviewer

  • Register completion and follow-up and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

11 · Review controlled operating changes

Coordinate controlled operating changes within Utility Diversion and Construction Access Coordination.

Trigger
Controlled operating changes requires a new record, an agreed review or a controlled change.

Responsible role
Commercial reviewer

  • Register controlled operating changes and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

12 · Prepare scoped operational reports

Coordinate scoped operational reports within Utility Diversion and Construction Access Coordination.

Trigger
Scoped operational reports requires a new record, an agreed review or a controlled change.

Responsible role
Project coordinator

  • Register scoped operational reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised project approver records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

Governance and control

  • Role permissions reflect the agreed responsibilities and restricted record access.
  • Required information and evidence are checked before the relevant decision or handover.
  • Exceptions have a named owner, recorded reason and an authorised resolution.
  • Approved changes retain their previous values, accountable decisions and linked evidence.
  • Integration mappings, business rules and acceptance criteria are reviewed with the customer.
Operating rules by business workflow
  • For utility diversions, the released version and authorised audience remain traceable to the accepted review.
  • For construction access around conflicting services, the request stays within the recorded permission and delegated authority.
  • For utility-owner designs, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For approved scopes, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For contractor dependencies, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For authorised access arrangements, the request stays within the recorded permission and delegated authority.
  • For completed diversions, the released version and authorised audience remain traceable to the accepted review.
  • For operating requirement, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For operating exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For completion and follow-up, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For controlled operating changes, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For scoped operational reports, the record retains an accountable owner, its supporting evidence and accepted outcome.

Data, interfaces and operating requirements.

Core records

Delivery recordUtility diversionsConstruction access around conflicting servicesUtility-owner designsScopesContractor dependenciesDecisionSupporting evidenceActivity history
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Project / work package — Business scope used for responsibility and reporting.
  • Operating subject — The request, commitment or work item being handled.
  • Accountable owner — Named responsibility for the next action.
  • Workflow stage — Current position in the agreed business journey.
  • Review requirement — Required review and outstanding decision.
  • Due or review date — Agreed action window or review trigger.
  • Linked evidence — Source records supporting the operating decision.
  • Decision authority — The delegated authority relevant to the accepted outcome.
  • Accepted outcome — Recorded decision and its business consequences.
  • Follow-up obligation — Remaining responsibilities after an accepted action.
  • Revision history — Trace of accepted changes and their evidence.
  • Utility diversions reference — Link the relevant utility diversions to the operating transaction and its decision evidence.
  • Construction access around conflicting services reference — Link the relevant construction access around conflicting services to the operating transaction and its decision evidence.
  • Utility-owner designs reference — Link the relevant utility-owner designs to the operating transaction and its decision evidence.
  • Scopes reference — Link the relevant scopes to the operating transaction and its decision evidence.
  • Contractor dependencies reference — Link the relevant contractor dependencies to the operating transaction and its decision evidence.

Systems and interfaces

  • Project, commercial and document records
  • Approved design, cost or work-package interfaces
  • Identity and role-based access services
  • Approved document and communication services

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Confirm the operating boundaries, utility diversions, responsible roles, review authority, record retention, interface mappings and acceptance scenarios.

Mobile and tablet access

Authorised users can review utility diversions, supporting records and assigned actions through mobile and tablet access. The relevant tasks and permissions are agreed for the deployment.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

Apple App Store ↗Google Play ↗

AI extensions

Core workflows and approval rules are defined with your business owners. Operational AI can be assessed separately against a specific business outcome and review requirements.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

AN EXAMPLE OPERATING SCENARIO

What to validate in a scoped demonstration.

Start with utility diversions and follow the record through coordinate delivery and evidence. Introduce a missing item or operating exception, record the authorised resolution and inspect the final handover, evidence and history.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report
Discuss this solution

Questions before implementation.

What can we review in a tailored demonstration?

Review a representative delivery record, its workflow stages, accountable roles, an exception and the resulting operational report. Bring the business process and existing system requirements that matter to your organisation.

How is the solution adapted to our organisation?

The operating scope covers your records, role permissions, review authority, business rules and integration boundaries. These requirements are agreed with the responsible business owners.

How does the solution connect with existing systems?

Connection design defines interfaces, data ownership, mapping, authentication and exception handling. The agreed implementation includes validation against the selected systems and workflows.

How are subsequent changes controlled?

The agreed engineering approach covers review of change impact, bounded implementation, validation and accepted revisions. Discuss the relevant Genesis Context Memory and support requirements during solution scoping.