WSOL

Architecture AI POC

Permit-to-Plan AI POC

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.

Client
Planning and construction client
Scope
Architecture AI POC
Focus
POC / AI
  • POC
  • AI
  • Documents
  • Architecture
FIG. 22 / Planning and construction clientPUBLIC WORK
Architecture AI POC
SYSTEM SIGNALSPlanning and construction clientArchitecture AI POCPOCAI

A proof of concept that turns planning materials, permits and requirements into a clearer workflow for professional deliverables.

A documented work map from planning material to execution path.Discuss a similar project

Case study

What needed to work better.

A heavy process of document reading, requirement interpretation and work preparation gained a layer that organizes information, open questions and next actions.

01

The reading pass

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.

02

What we built

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.

03

Scope of the claim

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.

Capabilities

The parts that make the work usable.

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.