top of page

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

(to save time and credits)

  • One project = one permit application. Keep scope and outputs clean (e.g., “ADU Garage Conversion” separate from “Kitchen Remodel”).

  • Send key details in one message. Consolidating inputs reduces back-and-forth and rework.

  • Use the Knowledge Base for better consistency. Upload title blocks, annotation standards, typical details, and past sets to match your firm’s style faster.

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

Step 1 create a new chat

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.)

Step 2 minimal text input
Step 3 upload reference file

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

Step 4 request generation
Step 5 review and request revisions

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.

building model

The Knowledge Base is where you store reference materials that guide output quality and consistency across projects.

What to upload

  • Title blocks and sheet templates

  • Annotation standards, line weights, typical notes

  • Typical details and detail library

  • Past drawing sets that represent your firm’s “standard”

  • Code checklists and internal QA references

How to organize it (recommended)

  • By drafting standards (title blocks, notes, styles)

  • By detail library (structural, architectural, MEP typicals)

  • By project type (ADU, SFR, multifamily, TI)

  • By jurisdiction (if you maintain city-specific checklists/notes)

How to use it during chat

When you want outputs to follow your standards, reference the relevant Knowledge Base folder or files in your message (e.g., “Apply our Title Block v3 and Residential Notes Library”).

bottom of page