AI INTEGRATION MATURITY

How AI-ready is your studio?

Ten questions about the way work moves through your studio. Get a suggested starting point and three practical opportunities, without sharing contact details.

Your selections are evaluated in this browser tab. They are not stored, submitted or used for analytics. This is a self-assessment, not a certification or scientific score.

01 / Are your core workflows documented?

Mostly individual habitsSome shared methodsOwned, documented and reviewed

02 / Where is current project knowledge kept?

Scattered across messages and filesShared folders with agreed sourcesVersioned context with approved decisions

03 / Which applications are central to delivery?

CAD / BIM / modellingImages / documents / presentationsA mix of design and project tools

04 / Which repeated task takes the most attention?

Research and brief interpretationModelling and checkingDocumentation and schedules

05 / Are templates and standards consistent?

They vary by personShared, but not consistently maintainedVersioned, owned and routinely used

06 / How is AI currently used?

Individual tools or early trialsConnected, repeatable workflowsCoordinated agents with monitored runs

07 / How is sensitive project information handled?

The boundaries are not documentedApproved sources and providers are definedAccess, retention and revocation are enforced

08 / Which decisions require human approval?

Decided informallyNamed reviewers and checkpointsEnforced gates with revision-specific approval

09 / Can objective outputs be checked reliably?

Mostly a visual inspectionDefined rules with some repeatable checksTested rules with coverage and exception reports

10 / How does completed work inform the next project?

It depends on personal recollectionSome reviewed templates and lessonsCurated knowledge with ownership and review

How this recommendation is made

There is no numerical score. Assist is the starting point when documented workflows, shared context, data boundaries or named approval are missing. Integrate requires those foundations. Orchestrate also requires shared standards, repeatable checks, connected AI use and enforced approval. Evolve requires the strongest documented option in all eight readiness areas, including curated memory. Application choice and the repeated task shape the opportunities, not the level. Different workflows in one studio may sit at different stages.