Planning Applications
Design and access statements, planning statements and validation checks drafted against the local plan, each policy quoted with its version. An architect reviews and submits.
Open pageA professional still signs the drawings. Planning statements, specifications, BIM checks and bid responses, drafted from your own past projects and standards. The model carries the documentation load; a registered professional still signs what is issued.
AI in architecture is mostly discussed as rendering and massing. For a practice, the larger gain is in documentation: planning statements, specifications, model checks and bids drafted from your own past work, with an architect or engineer reviewing and signing everything that leaves the office.
The AI tools for architects that dominate search results (Midjourney, Gendo, Finch, TestFit, D5) are good at concept imagery, massing and layout. We build the other half: systems that read your archive of issued drawings, specifications, planning decisions and bids, and draft new documents with every clause traceable to its source.
The design rule is that the model drafts and checks, and the professional decides. Under the UK Building Safety Act 2022 the dutyholder regime and the golden thread of building information put named people on the hook for higher-risk buildings; in Spain the Código Técnico de la Edificación and the visado regime do similar work. None of that moves to software. What changes is how much of a professional’s week is spent re-typing rather than reviewing.
Design and access statements, planning statements and validation checklists drafted from the brief, the site and the local plan, with each policy reference cited.
SEE PLANNING APPLICATIONS →Specification sections drafted from your master spec and the model, structured to Uniclass or MasterFormat, with products and standards checked for currency.
SEE SPECIFICATION WRITING →Every model drop checked against the BIM execution plan: naming, classification, required properties and level of information, reported as BCF issues.
SEE BIM CHECKS →Quality answers for bids and frameworks drafted from your past submissions and project sheets, mapped to the evaluation criteria and word limits.
SEE TENDER RESPONSES →These are engineering controls we build into the architecture, not certifications. QQuantum.ai holds no security certifications, and the audits and attestations your sector requires remain yours to run — see our trust centre.
Design and access statements, planning statements and validation checks drafted against the local plan, each policy quoted with its version. An architect reviews and submits.
Open pageSpecification sections drafted from your NBS or MasterFormat master and the model, with standards and products checked for currency. Unverified references are flagged, never written.
Open pageEvery IFC model drop checked against the BIM execution plan and ISO 19650 information requirements, reported as BCF issues. A well-formed model is not an approved design.
Open pageTender and framework answers drafted from your past bids, project sheets and CVs, mapped to the criteria. A claim with no source document is shown as a gap, never invented.
Open pageIn two broad ways. Design tools generate concept imagery, massing options and floor-plan layouts from sketches or rules. Practice tools, which is what we build, draft and check the documents around the design: planning statements, specifications, BIM model checks and bid responses, drawn from the practice archive. In both cases the architect stays responsible for what is designed and issued.
It depends on the stage. For concepts and rendering, tools such as Midjourney, Gendo, LookX and D5 Render are widely used; for feasibility and layout, TestFit and Finch; for model checking, Solibri and rule engines on IFC. The gap most practices feel is documentation, which is specific to your standards and archive, and is where a system built around your own work pays off.
Not the accountable part of the job. Design judgement, client relationships, coordination and the professional duty that comes with signing drawings stay with people, and regulators expect a named person to be responsible. AI reduces the time spent producing documentation and checking models, which is a large part of the week in most practices.
Yes. We read IFC exports from any authoring tool, and Revit or Archicad data through their APIs where a check needs native parameters. Findings go back as BCF issues so they open at the right element in the tool your team already uses, and documents sit in your common data environment with the revision they belong to.
No. Your drawings, specifications and bids stay on infrastructure you control, or behind hosted-model terms that exclude training. The model retrieves from your archive at the moment of drafting rather than learning from it, so a past client project is cited when it is used, and access can follow the same permissions as your file server.
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Start with one document type your practice writes every week, drafted from your own archive and judged by the people who sign it.
30-minute technical call · no deck