PERMITTING

Permits that move, with every step on the record.

From application to completion certificate, on the same platform and the same built-in security.

A worked example: permitting on Alaflow.

Every screen and step below is illustrative. They show how the platform handles this kind of work, set up the way your own rules require.

Councils and permitting authorities decide whether work or activity may go ahead: building a structure, opening a business, or carrying out something that affects land, water or the environment. Each application passes through completeness checks, reviews by several specialists, fee handling, a decision, and often an inspection afterwards. The people who apply, and the people who review, both need to know where an application stands, and the authority needs a record it can stand behind if a decision is questioned.

The service on this page is a permitting service. Each application is one record that carries its documents, reviews, comments, fees and decision, moving through stages with owners and deadlines from submission to completion certificate. Applicants submit and follow their application in a portal of their own. The sections below show how that service is made up.

What this service is made of.

  1. The people who use it

    Staff work on their own screens. People outside your organisation use a separate portal.

    • Staff
    • Applicants on the portal

  2. Your services

    Set up for each kind of work, in days, and changed as your rules change.

    • Municipal permitting

    This layer and the two below it are set up in days and changed as your rules change.

  3. What you keep track of

    records

    The record types your services need.

    • An application
    • The applicant
    • Reviews and their comments
    • Fee-payment state
    • A permit
    • An inspection and its findings
    • A completion certificate

  4. What each record can do

    capabilities

    Building blocks you switch on for each record type.

    • Stages with deadlines
    • Parallel reviews assigned to specialists
    • Tasks and checklists
    • Versioned documents
    • Interactions

  5. What is built in

    controls

    Built in from the first day, tuned to your rules when your services are built, and not switched off by accident.

    • Access control
    • Classification
    • Protected identifiers
    • Retention and legal hold
    • Audit trail
    • Emergency access

    Built in from day one. Cannot be switched off by accident.

The storyline.

How a permit will move, from application to completion certificate.

  1. The applicant will submit an application and documents.
  2. Staff will check completeness and assign parallel reviews to specialists.
  3. Reviewers will leave structured comments.
  4. The applicant will respond and resubmit.
  5. Staff will record the fee-payment state.
  6. Authorised staff will issue the permit.
  7. The applicant will ask for an inspection.
  8. Staff will record pass or fail, and the findings.
  9. A final pass will produce a completion certificate.

Two examples, one flow.

The same flow serves municipal and environmental permitting.

Municipal

A residential accessory structure, or a business licence.

Environmental

The same flow, kept general.

What already works.

The capabilities underneath are available today.

Stages with deadlines

Every step has an owner and a deadline.

Versioned documents

Find any document, and see every version.

Tasks and checklists

Work is assigned to a person or a team, with a checklist.

The client portal

A portal of their own, kept apart from staff.

The audit trail

Every action on the record.

Talk to us about your work.