Getting Started with Blueprints AI
Blueprints AI helps A/E teams move from design to construction documents faster—while staying aligned with your scope, references, and internal standards.
Pro tips
-
One project = one permit application. Keep scope and outputs clean (e.g., “ADU Garage Conversion” separate from “Kitchen Remodel”).
-
Use the Knowledge Base for better consistency. Upload company guidelines, templates, and libraries and past project sets to match your firm’s standards.
What you need to start
Minimum required
Provide these items in your first message before generation:
-
Full address (e.g., 1234 Main St, Los Angeles, CA 90012)
-
Program (e.g., 2 bed / 2 bath, single level)
-
Area (total square footage, e.g., 2,500 SF)
-
New build or existing (existing structure vs. new construction)
-
Use & Occupancy (e.g., Residential, SFR, R-3)
Optional (but strongly recommended)
Upload anything that clarifies design intent, existing conditions, or constraints:
-
Hand sketches / markups
-
Floor plans, elevations, sections, details
-
Code notes, checklists, local amendments
-
3D scans / point clouds (if applicable)
-
Your firm’s title block, sheet templates, typical details
Accepted formats
PDF, JPG, PNG, DWG/DXF (AutoCAD), RVT (Revit), SKP (SketchUp), Zip
Step-by-step workflow
01
Create a new chat (one per project)
Set up one project per permit application to keep scope, revisions, and outputs organized.
Examples
-
Project A: Office Building New Construction
-
Project B: Single Family Remodel
-
Project C: ADU Garage Conversion
02
Send the minimum required info in one message
Include the minimum checklist above in a single message. This improves accuracy and reduces credit usage.
Copy/paste starter template
-
Address:
-
Project type: (new / existing)
-
Use & Occupancy:
-
Program:
-
Total area (SF):
-
Notes/constraints: (setbacks, parking, existing conditions, design intent, etc.)
03
Upload reference files (recommended)
Reference files help the system understand your intent and constraints—resulting in clearer drawings and fewer revision cycles.
Helpful uploads
-
Design documents: plans, elevations, sections, details, markups
-
Models/scans: Revit, SketchUp, 3D scans
-
Code/standards: local amendments, typical details, checklists
-
Firm standards: title blocks, annotation styles, line weights, sheet templates
04
Request generation
Once the project details and files are in place, request the outputs you need, such as:
-
2D drawings: plans, elevations, sections, details
-
3D models: where applicable
-
Drawing sets: organized sheets aligned to your standards and references
05
Review and request revisions (be specific)
For edits, specify exactly what to change to accelerate turnaround:
-
Sheet name/number
-
View (plan/elevation/section/detail)
-
Dimensions, notes, tags, or layout changes
-
Style updates (line weights, annotation conventions, title block)
06
Optimize workflow
-
Consolidate information to reduce iteration cycles.
-
Pause/stop a generation stream anytime if you need to adjust inputs.
The Knowledge Base is where you store reference materials that guide output quality and consistency across projects.
(^ click to navigate to the section)
What to upload at 'General'
What past projects to upload
-
Past permitted and final drawing sets, final design files
-
Format: PDF + native file of software used (CAD, Revit, SketchUp)
How to organize it (recommended)
By project type (single family, townhouse, condominium, data center, pre-school, storefront, etc.)
How many past projects should I upload?
The Baseline: at least 10 projects to get started.
The Sweet Spot: firms that upload 50+ projects see a significant improvement in output quality.
The more files you provide, the smarter your results become.
How to use it during chat
Simply reference the relevant Knowledge Base folder or files in your message (e.g., “Apply our Title Block v3 and Residential Notes Library”).