22Permit-to-Plan AIPilot

From planning material to an organised working layer.

A proof of concept that reads permits, requirements and planning material and returns what they state, which questions stay open and what happens next.

Client
Permit-to-Plan AI
Type
Pilot
  • Planning-material intake
  • Requirement extraction
  • Open questions
An abstract cover of the workflow steps — not a capture of the system.

Context

A planning and construction client works from permits, requirements and planning material spread across long documents. Before a single professional deliverable can be drafted, someone has to read all of it and hold the open questions in their head.

The challenge

Preparing a professional deliverable starts with reading. Permits, requirements and planning material arrive as long documents, each written for a different reader. Whoever prepares the work extracts what applies, marks what is missing or contradictory, and decides what happens next. That pass repeats per project, and its output tends to stay in personal notes and memory.

Our work

A proof of concept running over the same material: intake · read · structure · next actions. It takes planning materials, permits and requirements and returns an organised working layer — what the documents state, which requirements attach to a specific deliverable, which questions stay open, and what the next actions are. The output is a workflow, not an auto-generated document.

What was built

Planning material intake
Reads permits, requirements and planning material as one input set instead of a manual pass file by file at the start of every project.
Requirement extraction
Pulls the requirements that attach to a given deliverable and holds them as discrete, addressable items rather than running prose.
Open-question register
Marks what the material does not resolve — gaps, contradictions and missing inputs — so unknowns stay visible instead of implicit.
Next-action mapping
Turns the material that was read into an ordered set of next actions for preparing the deliverable, with every step under human review.

How the process looks

Before

  • Long documents, each written for a different reader
  • Open questions stay in notes and memory

With the system

  1. Intake
  2. Read
  3. Structure
  4. Next actions

The evidence

No system captures have been cleared for publication yet. This page describes what was built and how it works, without passing off a mock-up as a real screen.

Scope boundary

What is claimed: a proof of concept was built and run against real planning material, and it produces an organised working layer over that material. What is not claimed: this is not a production system, it does not generate or approve a professional deliverable, no client name or documents appear here, and no operational or commercial result is presented as measured. Professional judgment stays with the professional.

A similar project in your business?

Tell us where the work gets stuck today, and we'll look together at what makes sense to build, connect or improve.