Capstone Workflow: From Site Massing to a Coherent Concept Presentation Model

Capstone Overview: One File, Two Options, One Presentation Set

This capstone is a start-to-finish workflow you can repeat on real projects: bring in a site plan, build two massing options, keep the model organized while you iterate, generate a consistent set of scenes (work, compare, section, diagram), add only the context you need, then export a small presentation package. The emphasis is not on new tools, but on sequencing, checkpoints, and deliverables so the model stays coherent as it grows.

Project Setup: Folder + File Naming Before You Model

Create a simple project folder structure so exports and references never get lost. Keep it boring and predictable.

01_SketchUp/ProjectName_Capstone_v01.skp
02_References/SitePlan.pdf (or .png)
03_Exports/01_Working
03_Exports/02_OptionCompare
03_Exports/03_Sections
03_Exports/04_Diagrams

Save the SKP immediately, then save incremental versions at milestones (v01, v02, v03). Treat each milestone as a “recoverable state,” not just a backup.

Step 1 — Import and Scale a Site Plan (Reliable, Verifiable)

1A. Import as a Reference You Can Lock

• Import the site plan (PDF/image/CAD) into the SKP.
• Place it at the origin if possible; align the plan so primary site edges are orthogonal to model axes (helps later with sections and scenes).
• Immediately group the imported plan and name it REF_SitePlan.
• Lock it so it can’t be accidentally moved while massing.

1B. Scale Using a Known Dimension + Verification

Scale the grouped reference using a known measurement (property line length, road width, grid spacing). After scaling, verify with a second known dimension. The second check is your first quality gate: if it fails, fix scaling now, not after options are built.

1C. Establish a Simple Site Base

Create a minimal site base that supports massing and sections without heavy geometry.

Continue in our app.

• Listen to the audio with the screen off.
• Earn a certificate upon completion.
• Over 5000 courses for you to explore!

Or continue reading below...

Download the app

• Trace the property boundary and key setbacks as simple edges/faces.
• Create a single ground plane face (or a few planar terraces if needed).
• Group and name: SITE_Base.
• If you need topography, keep it coarse (enough to read slopes, not enough to slow orbiting).

Step 2 — Build Two Massing Options (Option A + Option B)

The goal is two coherent alternatives that can be compared in identical views. Build both options in the same file so scenes, section cuts, and context are shared.

2A. Create an Option Container Structure

Set up a predictable hierarchy in the Outliner before modeling the options. This prevents “floating geometry” and makes later audits fast.

00_REFERENCES
  REF_SitePlan (locked)
10_SITE
  SITE_Base
20_OPTION_A
  A_Massing
  A_Cores (if needed)
30_OPTION_B
  B_Massing
  B_Cores (if needed)
40_CONTEXT
  CTX_Neighbors
  CTX_Trees
  CTX_Roads
90_OUTPUT_HELPERS
  SectionPlanes
  DiagramOverlays

Each top-level item is a group/component container. The rule: you never draw raw geometry at the model root.

2B. Option A: Primary Move + Secondary Adjustments

• Inside 20_OPTION_A, create A_Massing as a single group.
• Block the main volume(s) first: footprint, height, step-backs.
• Only after the main move reads clearly, add secondary volumes (podium, tower, courtyard bar, etc.).
• Keep faces clean and orthogonal where possible; avoid micro-offsets that complicate sections.

2C. Option B: Contrast the Strategy, Not Just the Shape

Option B should test a different organizing idea (orientation, courtyard vs. bar, split volumes vs. single mass, different access logic). Keep the level of detail comparable to Option A so comparisons are fair.

• Inside 30_OPTION_B, create B_Massing as a single group.
• Match key constraints (setbacks, max height, site access) so the option is credible.
• Maintain similar geometric “resolution” (don’t make one option highly articulated and the other a block).

Milestone 1: “Two Options Exist” Check

Quality Gate 1 — Organization Audit Before Any Detailing

Do this audit before you add façade hints, terraces, or diagram elements. Fixing organization later costs more than rebuilding small parts now.

Organization Audit Checklist (Fast, Mechanical)

• Outliner: Every major element is nested under the correct container (10_SITE, 20_OPTION_A, etc.).
• Naming: No “Group#123” or “Component#45” for anything you’ll show in scenes.
• Tags: Tags are applied to groups/components, not raw geometry.
• Option isolation: Turning off Option A does not hide any Option B geometry (and vice versa).
• Reference lock: REF_SitePlan remains locked and unchanged.

If any item fails, stop and correct it immediately. This is the gate that keeps the rest of the workflow stable.

Step 3 — Tags for Option Control + Scene Consistency

Use tags to control visibility for scenes and comparisons. Keep the tag list short and purposeful.

Suggested Minimal Tag Set

Assign tags at the container level (e.g., 20_OPTION_A group tagged as OPT_A). This makes scene visibility changes robust and reduces mistakes.

Step 4 — Build a Scene Set That Matches Your Review Story

Create scenes in a deliberate order: working views first (for you), then comparison views (for decisions), then sections and diagrams (for explanation). Keep camera and style consistent across option scenes so differences read as design, not as view changes.

4A. Working Scenes (Navigation + Modeling)

• SCN_00_Work_Axon: a comfortable axonometric for modeling.
• SCN_01_Work_SiteTop: top view for alignment and setbacks.
• SCN_02_Work_Street: eye-level from primary approach.

These scenes can show guides, reference plan, and section planes if helpful. They are not for export; they are for speed and orientation.

4B. Option Comparison Scenes (Same Camera, Different Visibility)

Duplicate the same camera position and create paired scenes where only option visibility changes. This is the simplest way to produce fair comparisons.

Lock in: camera position, field of view, style, and shadow settings (if used). Only toggle tags for options.

4C. Section Scenes (One Cut, Two Options)

Create one or two section cuts that reveal the main spatial idea (entry sequence, courtyard relation, height transitions). Then create paired scenes for A and B using the same cut location.

• SCN_20_SectionLong_A / SCN_21_SectionLong_B
• SCN_22_SectionCross_A / SCN_23_SectionCross_B

Keep section plane objects in a dedicated container (e.g., 90_OUTPUT_HELPERS > SectionPlanes) so they can be toggled reliably.

4D. Diagram Scenes (Explain the Concept with Minimal Geometry)

Diagram scenes should be lightweight: simplified masses, poche, circulation arrows, and context hints. The key is clarity, not completeness.

• SCN_30_Diagram_Parti: simplified mass + key voids.
• SCN_31_Diagram_Access: entry points, drop-off, service.
• SCN_32_Diagram_SunWind (optional): only if it supports the concept.

Use a dedicated DIAGRAM tag so diagram elements never pollute working or comparison scenes.

Quality Gate 2 — Performance Check Before Adding Context

Context is where models often become sluggish. Before you add neighbors, trees, cars, or entourage, confirm the file is responsive and stable.

Performance Check (What to Test)

• Orbit test: orbit in a comparison scene with shadows off; navigation should feel smooth.
• Scene switching: click through 6–10 scenes; transitions should not stall excessively.
• Outliner responsiveness: expanding/collapsing major containers should not lag.

If performance is already borderline, reduce complexity now: simplify massing segmentation, purge unused items, and keep context extremely minimal.

Step 5 — Add Lightweight Context (Only What Improves Readability)

Add context as a framing device: enough to understand scale, edges, and adjacencies, but not so much that it competes with the concept model.

5A. Neighboring Masses

• Model adjacent buildings as simple extrusions with flat tops.
• Group them under 40_CONTEXT > CTX_Neighbors and tag as CTX.
• Keep them slightly muted (style/material) so your options remain primary.

5B. Streets, Sidewalks, and Key Trees

• Represent streets/sidewalks as simple faces with minimal linework.
• Add only a few trees to indicate scale and outdoor space; avoid dense scattering.
• Keep all context on the CTX tag so it can be disabled for diagram scenes.

Step 6 — Finalize a Small Presentation Set (Views You Can Place Immediately)

Your export set should be small but complete: enough to communicate the concept, compare options, and show key sections/diagrams. Aim for consistency: same aspect ratio, same resolution, same visual language.

6A. Define the Export List (Example Set)

6B. Export Settings (Consistency Over Experimentation)

• Choose one image size for the entire set (e.g., 2500–4000 px wide depending on your layout needs).
• Use the same style for all comparison scenes; use a diagram style only for diagram scenes.
• Keep file naming aligned to scene names so sorting is automatic.

Example export naming pattern:

03_Exports/02_OptionCompare/SCN_10_Compare_A.png
03_Exports/02_OptionCompare/SCN_11_Compare_B.png
03_Exports/03_Sections/SCN_20_SectionLong_A.png
03_Exports/04_Diagrams/SCN_30_Diagram_Parti.png

Quality Gate 3 — Final Scene Verification Before Exporting

This is the last checkpoint: verify that every exported view is intentional and repeatable. Do it once, then export confidently.

Scene Verification Checklist

• Correct visibility: Option A scenes show only OPT_A; Option B scenes show only OPT_B.
• Reference hidden: REF tag off in all export scenes (unless explicitly needed).
• Context discipline: CTX on for exterior presentation scenes, off for diagrams if it competes.
• Section correctness: Section cuts are active only in section scenes; no accidental cuts in axons.
• Camera consistency: A/B paired scenes match camera position and FOV exactly.
• Style consistency: Comparison scenes share the same style settings; diagram scenes share their own.
• Axis/origin sanity: Nothing is far from origin due to accidental moves; navigation remains stable.

Deliverable Package: What You Hand Off (Structured and Ready)

Deliverable 1 — SKP File (Clean, Auditable)

• File: ProjectName_Capstone_v##.skp
• Outliner: matches the container structure (References, Site, Option A, Option B, Context, Output Helpers).
• Tags: minimal set; no unused tags; tags applied only to groups/components.
• Scenes: named and ordered (Working, Compare, Sections, Diagrams); paired A/B scenes aligned.
• Context: lightweight and fully toggleable via CTX tag.

Deliverable 2 — Export Folder (Ready for Layout)

• Folder: 03_Exports with subfolders by category.
• Files: exported images named exactly like scenes for automatic placement and revision tracking.
• Set completeness: option comparison views, key sections for both options, and diagrams that explain the concept.