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

Local government / APPLICATION BLUEPRINT

Development Application & Agency Referral Coordination

Coordinates development applications, submission completeness and specialist agency referrals.

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 council service officers and the responsible business owners

Development Application & Agency Referral Coordination workspace interface preview; illustrative records and figures.
Development Application & Agency Referral 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.

Development Application & Agency Referral Coordination workspace interface preview; illustrative records and figures.
Development Application & Agency Referral Coordination — operational workspaceIllustrative interface · Sample dataView full interface →
Development Application & Agency Referral Coordination record interface preview; illustrative records and figures.
Development Application & Agency Referral 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.

Service area / wardPeriodAssigned 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 development applications, submission completeness and specialist agency referrals. Tracks information requests, consultation responses and outstanding conditions, then records authorised planning determinations with traceable evidence and clear responsibility for subsequent approval requirements.

Operations

Operational overview

Review the work position and priority actions.

Development applications

Coordinate development applications with assigned responsibilities, linked records and review history.

Submission completeness

Coordinate submission completeness with assigned responsibilities, linked records and review history.

Specialist agency referrals

Coordinate specialist agency referrals with assigned responsibilities, linked records and review history.

Information requests

Coordinate information requests with assigned responsibilities, linked records and review history.

Consultation responses

Coordinate consultation responses with assigned responsibilities, linked records and review history.

Outstanding conditions

Coordinate outstanding conditions with assigned responsibilities, linked records and review history.

Planning determinations

Coordinate planning determinations 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 development applications, capture the required records and assign the accountable team.

02

Coordinate delivery and evidence

Coordinate submission completeness, specialist agency referrals, 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 development applications

Coordinate development applications within Development Application and Agency Referral Coordination.

Trigger
Development applications requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register development applications 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
Delegated decision maker 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.

02 · Coordinate submission completeness

Coordinate submission completeness within Development Application and Agency Referral Coordination.

Trigger
Submission completeness requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register submission completeness 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
Delegated decision maker 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.

03 · Coordinate specialist agency referrals

Coordinate specialist agency referrals within Development Application and Agency Referral Coordination.

Trigger
Specialist agency referrals requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register specialist agency referrals 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
Delegated decision maker 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.

04 · Track information requests

Coordinate information requests within Development Application and Agency Referral Coordination.

Trigger
Information requests requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register information requests 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
Delegated decision maker 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.

05 · Track consultation responses

Coordinate consultation responses within Development Application and Agency Referral Coordination.

Trigger
Consultation responses requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register consultation responses 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
Delegated decision maker 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 · Track outstanding conditions

Coordinate outstanding conditions within Development Application and Agency Referral Coordination.

Trigger
Outstanding conditions requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register outstanding conditions 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
Delegated decision maker 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.

07 · Record authorised planning determinations

Coordinate authorised planning determinations within Development Application and Agency Referral Coordination.

Trigger
Authorised planning determinations requires a new record, an agreed review or a controlled change.

Responsible role
Council service officer

  • Register authorised planning determinations 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
Delegated decision maker 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.

08 · Register the operating requirement

Coordinate operating requirement within Development Application and Agency Referral Coordination.

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

Responsible role
Council service officer

  • 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
Delegated decision maker 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 Development Application and Agency Referral Coordination.

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

Responsible role
Council service officer

  • 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
Delegated decision maker 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 Development Application and Agency Referral Coordination.

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

Responsible role
Technical inspector

  • 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
Delegated decision maker 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 Development Application and Agency Referral Coordination.

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

Responsible role
Technical inspector

  • 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
Delegated decision maker 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 Development Application and Agency Referral Coordination.

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

Responsible role
Council service officer

  • 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
Delegated decision maker 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 development applications, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For submission completeness, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For specialist agency referrals, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For information requests, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For consultation responses, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For outstanding conditions, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For authorised planning determinations, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • 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 recordDevelopment applicationsSubmission completenessSpecialist agency referralsInformation requestsConsultation responsesDecisionSupporting evidenceActivity history
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Service area / ward — 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.
  • Development applications reference — Link the relevant development applications to the operating transaction and its decision evidence.
  • Submission completeness reference — Link the relevant submission completeness to the operating transaction and its decision evidence.
  • Specialist agency referrals reference — Link the relevant specialist agency referrals to the operating transaction and its decision evidence.
  • Information requests reference — Link the relevant information requests to the operating transaction and its decision evidence.
  • Consultation responses reference — Link the relevant consultation responses to the operating transaction and its decision evidence.

Systems and interfaces

  • Council property, service and records systems
  • Approved application, inspection or finance 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, development applications, responsible roles, review authority, record retention, interface mappings and acceptance scenarios.

Mobile and tablet access

Authorised users can review development applications, 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 development applications 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.