How to Use Autodesk Forma for Constraint-driven site layouts

Autodesk Forma works well for constraint-driven site layouts when you run it like production work: locked brief, SOURCE facts, then review before publish. Autodesk Forma is AI-powered cloud software for site planning, massing, and environmental analysis; Forma Site Design may be available standalone or in AEC Collection. Confirm live access and pricing with Autodesk. Start at /explore/autodesk-forma.

This guide focuses on constraint-driven site layouts in detail. Related Autodesk Forma articles: /blog/how-to-use-autodesk-forma-for-design-option-documentation, /blog/how-to-use-autodesk-forma-for-site-planning-massing-studies, /blog/how-to-use-autodesk-forma-for-environmental-analysis-reviews.

When this workflow is the right job

Use constraint-driven site layouts when the deliverable is specifically this Autodesk Forma job. Switch to site planning massing studies when that workflow already owns the asset.

Step by step workflow

1. Brief Constraint-driven site layouts

Write what must stay true for constraint-driven site layouts in Autodesk Forma before settings or spend.

Brief: Constraint-driven site layouts
Keep: verified SOURCE facts only
Avoid: invented pricing or features
Success: one reviewable output

2. Open Autodesk Forma for Constraint-driven site layouts

Use the Autodesk Forma surface that owns constraint-driven site layouts. Do not mix a neighboring workflow in the same pass.

Surface: Constraint-driven site layouts
Start: pilot with one representative input
Plans: www.autodesk.com/products/forma/overview

3. Pilot Constraint-driven site layouts

Run a single constraint-driven site layouts pilot. Score clarity, grounding, and whether the output is reviewable.

Pilot: Constraint-driven site layouts
[ ] SOURCE facts match
[ ] Output reviewable
[ ] Settings logged

4. Refine Constraint-driven site layouts

Change one constraint-driven site layouts dimension only. Save a template from the best run.

Refine: Constraint-driven site layouts
Change: one control only
Keep: SOURCE and success criteria

Practical constraint-driven site layouts examples

Non-goals list

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Non-goals list".

Objective:
Map initiatives to measurable outcomes for Non-goals list without inventing unsupported product features.

Inputs:
- Business objective for Non-goals list
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Non-goals list → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Non-goals list with gaps, owners, and open questions marked TBD where unknown.

Owner RACI

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Owner RACI".

Objective:
Map initiatives to measurable outcomes for Owner RACI without inventing unsupported product features.

Inputs:
- Business objective for Owner RACI
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Owner RACI → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Owner RACI with gaps, owners, and open questions marked TBD where unknown.

Timeline 6 weeks

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Timeline 6 weeks".

Objective:
Map initiatives to measurable outcomes for Timeline 6 weeks without inventing unsupported product features.

Inputs:
- Business objective for Timeline 6 weeks
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Timeline 6 weeks → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Timeline 6 weeks with gaps, owners, and open questions marked TBD where unknown.

Budget TBD flag

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Budget TBD flag".

Objective:
Map initiatives to measurable outcomes for Budget TBD flag without inventing unsupported product features.

Inputs:
- Business objective for Budget TBD flag
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Budget TBD flag → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Budget TBD flag with gaps, owners, and open questions marked TBD where unknown.

Training handoff

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Training handoff".

Objective:
Map initiatives to measurable outcomes for Training handoff without inventing unsupported product features.

Inputs:
- Business objective for Training handoff
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Training handoff → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Training handoff with gaps, owners, and open questions marked TBD where unknown.

Integration needs

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Integration needs".

Objective:
Map initiatives to measurable outcomes for Integration needs without inventing unsupported product features.

Inputs:
- Business objective for Integration needs
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Integration needs → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Integration needs with gaps, owners, and open questions marked TBD where unknown.

Data readiness

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Data readiness".

Objective:
Map initiatives to measurable outcomes for Data readiness without inventing unsupported product features.

Inputs:
- Business objective for Data readiness
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Data readiness → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Data readiness with gaps, owners, and open questions marked TBD where unknown.

Compliance note

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Compliance note".

Objective:
Map initiatives to measurable outcomes for Compliance note without inventing unsupported product features.

Inputs:
- Business objective for Compliance note
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Compliance note → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Compliance note with gaps, owners, and open questions marked TBD where unknown.

Change management

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Change management".

Objective:
Map initiatives to measurable outcomes for Change management without inventing unsupported product features.

Inputs:
- Business objective for Change management
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Change management → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Change management with gaps, owners, and open questions marked TBD where unknown.

KPI dashboard

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "KPI dashboard".

Objective:
Map initiatives to measurable outcomes for KPI dashboard without inventing unsupported product features.

Inputs:
- Business objective for KPI dashboard
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for KPI dashboard → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for KPI dashboard with gaps, owners, and open questions marked TBD where unknown.

Review cadence

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Review cadence".

Objective:
Map initiatives to measurable outcomes for Review cadence without inventing unsupported product features.

Inputs:
- Business objective for Review cadence
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Review cadence → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Review cadence with gaps, owners, and open questions marked TBD where unknown.

Decision log

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Decision log".

Objective:
Map initiatives to measurable outcomes for Decision log without inventing unsupported product features.

Inputs:
- Business objective for Decision log
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Decision log → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Decision log with gaps, owners, and open questions marked TBD where unknown.

Ticket -15% Q4

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Ticket -15% Q4".

Objective:
Map initiatives to measurable outcomes for Ticket -15% Q4 without inventing unsupported product features.

Inputs:
- Business objective for Ticket -15% Q4
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Ticket -15% Q4 → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Ticket -15% Q4 with gaps, owners, and open questions marked TBD where unknown.

Chatbot scope gap

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Chatbot scope gap".

Objective:
Map initiatives to measurable outcomes for Chatbot scope gap without inventing unsupported product features.

Inputs:
- Business objective for Chatbot scope gap
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Chatbot scope gap → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Chatbot scope gap with gaps, owners, and open questions marked TBD where unknown.

Stakeholder map

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Stakeholder map".

Objective:
Map initiatives to measurable outcomes for Stakeholder map without inventing unsupported product features.

Inputs:
- Business objective for Stakeholder map
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Stakeholder map → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Stakeholder map with gaps, owners, and open questions marked TBD where unknown.

Metric definition

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Metric definition".

Objective:
Map initiatives to measurable outcomes for Metric definition without inventing unsupported product features.

Inputs:
- Business objective for Metric definition
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Metric definition → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Metric definition with gaps, owners, and open questions marked TBD where unknown.

Dependency list

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Dependency list".

Objective:
Map initiatives to measurable outcomes for Dependency list without inventing unsupported product features.

Inputs:
- Business objective for Dependency list
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Dependency list → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Dependency list with gaps, owners, and open questions marked TBD where unknown.

Risk register

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Risk register".

Objective:
Map initiatives to measurable outcomes for Risk register without inventing unsupported product features.

Inputs:
- Business objective for Risk register
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Risk register → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Risk register with gaps, owners, and open questions marked TBD where unknown.

Pilot success bar

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Pilot success bar".

Objective:
Map initiatives to measurable outcomes for Pilot success bar without inventing unsupported product features.

Inputs:
- Business objective for Pilot success bar
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Pilot success bar → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Pilot success bar with gaps, owners, and open questions marked TBD where unknown.

Workshop agenda

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Workshop agenda".

Objective:
Map initiatives to measurable outcomes for Workshop agenda without inventing unsupported product features.

Inputs:
- Business objective for Workshop agenda
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Workshop agenda → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Workshop agenda with gaps, owners, and open questions marked TBD where unknown.

Initiative portfolio

Scenario:
A stakeholder uses Autodesk Forma for Constraint-driven site layouts about "Initiative portfolio".

Objective:
Map initiatives to measurable outcomes for Initiative portfolio without inventing unsupported product features.

Inputs:
- Business objective for Initiative portfolio
- Current AI initiatives
- Stakeholders
- Success metrics

Workflow:
Capture objective → List initiatives → Identify gaps for Initiative portfolio → Prioritize → Agree owners

Requirements:
- Stay within verified Autodesk Forma capabilities; do not invent features.
- Confirm live plan notes on www.autodesk.com/products/forma/overview before promising volume.
- Change one variable between iterations.
- Human-review before external publish, send, billing, or clinical/legal use.

Expected output:
An alignment brief for Initiative portfolio with gaps, owners, and open questions marked TBD where unknown.

How to improve constraint-driven site layouts

Cut noise from constraint-driven site layouts by removing extra adjectives while preserving SOURCE facts in Autodesk Forma.

Raise quality by insisting on a single success check before debating style.

Make review easier by labeling fields that must never change.

Speed iteration by cloning the last good run and altering only one control.

Stabilize outputs by pinning settings after the pilot is approved.

Reduce rework by rejecting drafts that invent claims.

Improve handoffs by recording which control produced the best result.

Harden the workflow by testing an incomplete input before trusting defaults.

Prompting and usage guidance

Name the constraint-driven site layouts job, audience, and success check before opening Autodesk Forma.

Paste only verified facts under SOURCE so Autodesk Forma cannot invent details.

Specify the deliverable shape up front.

Call out fixed details versus flexible style choices.

Ask Autodesk Forma to flag unsupported claims before you accept the draft.

Limitations to respect

Check Autodesk Forma plan gates for constraint-driven site layouts on www.autodesk.com/products/forma/overview before you promise timelines.

Keep drafts unpublished until a human confirms SOURCE facts.

Autodesk Forma can be wrong. Treat constraint-driven site layouts as provisional until review.

If documentation is silent on a claim, leave it out rather than guessing.

Practical tips for this workflow

Pilot once before batching constraint-driven site layouts in Autodesk Forma.

Keep a reusable template with variables for constraint-driven site layouts.

Separate creative instructions from SOURCE facts.

Log settings from the best run.

Common mistakes

• Skipping the pilot run before scaling volume
• Inventing pricing, quotas, or features not on official pages
• Mixing unrelated workflows in one session
• Publishing without a human review gate

Treat constraint-driven site layouts in Autodesk Forma as a production workflow: brief, pilot, refine, then ship with review. Related reading: /blog/how-to-use-autodesk-forma-for-design-option-documentation, /blog/how-to-use-autodesk-forma-for-site-planning-massing-studies, /blog/how-to-use-autodesk-forma-for-environmental-analysis-reviews.