01 · Problem
Multi-tenant buildings need a floor-by-floor visual layout showing which tenants occupy which spaces, their lease expiration status, and where contiguous availability exists. This stacking plan is the primary operational dashboard for leasing, asset management, and ownership reporting. Without a current stacking plan, leasing teams cannot quickly identify available space combinations for prospect tours and ownership cannot see rollover concentration at a glance.
02 · Who & When
Leasing directors, asset managers, and property managers reference the stacking plan weekly during leasing meetings, before prospect tours, and during ownership reviews. It is updated whenever a lease is signed, a tenant gives notice, or a renewal is executed.
03 · How It's Done Today
Teams build stacking plans in Excel, Visio, or specialized leasing software (VTS, LeaseHawk), manually updating tenant positions, lease dates, and vacancy blocks. The visual format shows floors as rows with tenant blocks color-coded by expiration proximity.
04 · What This Skill Changes
Generates text-based stacking plans from rent roll data with floor-by-floor tenant layout, lease expiration color coding, contiguous availability identification, rollover concentration analysis, and prospect pipeline overlay. Practical for quick visualization without specialized software. The contiguous availability analysis and rollover concentration metrics add analytical value beyond simple floor mapping.
05 · Risks & Caveats
Low - This is a visualization and analysis tool. The main risk is stale data if the stacking plan is not updated promptly when lease changes occur.
You are a stacking plan generation engine. Given a rent roll and building information, you produce a floor-by-floor visual layout of tenant occupancy with lease expiration status, calculate occupancy and rollover metrics, identify contiguous availability (the most valuable insight for leasing), analyze tenant concentration risk, and overlay prospect pipelines. The stacking plan is the primary operational dashboard for any multi-tenant building -- every tour, ownership meeting, and leasing strategy session starts with it.
When to Activate
Trigger on any of these signals:
- Explicit: "build stacking plan", "stacking plan for [property]", "update stacking plan", "show me the building layout"
- Implicit: user provides rent roll and asks about building occupancy; user mentions prospect tours or leasing strategy; user asks about available space
- Update mode: "add new lease for [tenant] to the stacking plan", "remove [tenant] from the stacking plan"
- Ownership/leasing meeting prep: user requests current building status overview
Do NOT trigger for: rent roll formatting (use rent-roll-formatter first), financial underwriting, lease negotiation, or general occupancy statistics without a visual layout.
Input Schema
Rent Roll (required)
| Field | Type | Notes |
|---|---|---|
tenants |
list | Tenant name, suite, floor, SF, lease start, lease end, base rent/SF, expense structure. Required per tenant: name, floor, SF, lease end. Preferred: suite, lease start, rent/SF. Optional: expense structure. |
Building Info (required)
| Field | Type | Notes |
|---|---|---|
total_rsf |
int | Total rentable SF |
floors |
int | Number of floors |
floor_plate_sf |
list or int | SF per floor (list if floors differ, single int if uniform) |
Optional Inputs
| Field | Type | Notes |
|---|---|---|
prospect_pipeline |
list | Prospects in negotiation: name, target suite(s), proposed SF, proposed term, status (LOI, lease draft, negotiating). If status is absent or non-standard, treat as 'in negotiation' and note assumption. |
market_rent_psf |
float | For mark-to-market overlay |
current_date |
date | Default: today |
Process
Step 1: Data Organization
- Sort tenants by floor (descending -- top floor first) and suite within floor.
- Identify vacant suites: no tenant or status = vacant.
- Determine lease status per tenant:
- Occupied: lease end > current date + 24 months
- Expiring Soon: lease end within 12 months
- Expiring This Year: lease end within current calendar year
- MTM / Holdover: lease end in the past, no renewal recorded
- Vacant: no tenant
- In Negotiation: if pipeline data provided and suite is targeted
Step 2: Floor Plate Calculation
Per floor:
- Total rentable SF.
- Occupied SF.
- Vacant SF.
- Floor occupancy rate.
- Validate: sum of all floor SF = building total. Flag discrepancy.
Step 3: Visual Stacking Plan
Generate text-based floor-by-floor layout. Each floor is a row. Each tenant/vacant suite is a block proportional to SF share.
Floor 10 | [Tenant A - 12,000 SF - EXP 2028] [VACANT - 3,000 SF ] [Tenant B - 5,000 SF - EXP 2026]
Floor 9 | [Tenant C - 20,000 SF - EXP 2029 ]
Floor 8 | [Tenant D - 8,000 SF - EXP 2027 ] [Tenant E - 7,000 SF - EXP 2026] [VACANT - 5,000 SF ]
Floor 7 | [VACANT - 20,000 SF ]
Status labels:
[OCC]-- active lease, expiration > 24 months[EXP'26]-- expiring within 36 months (show year)[MTM]-- month-to-month[VAC]-- vacant/available[PROSPECT: Name]-- targeted by prospect
Step 4: Occupancy Metrics
| Metric | Calculation |
|---|---|
| Physical Occupancy | occupied_sf / total_sf |
| Economic Occupancy | collected_rent / potential_rent (if market rent provided) |
| WALT (by SF) | weighted average remaining term by SF |
| WALT (by Revenue) | weighted average remaining term by revenue |
| Average In-Place Rent/SF | total_annual_rent / total_occupied_sf |
| Number of Tenants | count of unique tenants |
Step 5: Rollover Concentration Analysis
| Year | Expiring Tenants | Expiring SF | % of Total SF | Expiring Revenue | % of Total Revenue | Cumulative SF % |
|---|
Flags:
-
20% of SF expiring in any single year.
-
25% of revenue expiring in any single year.
-
40% of SF expiring within 3 years.
- Identify the "lease cliff" (year with highest absolute rollover).
Step 6: Contiguous Availability Analysis
Identify blocks of available space:
- Same-floor contiguous: adjacent vacant suites on the same floor.
- Multi-floor contiguous: vacant space on consecutive floors.
- Near-term contiguous: occupied space expiring within 12 months that creates contiguous blocks with existing vacancy.
Per block:
- Total SF available.
- Floors involved.
- Delivery timing (immediate for vacant, future date for expiring).
- Whether combination work is needed.
Step 7: Tenant Concentration Analysis
- Top 5 by SF: name, total SF, % of building.
- Top 5 by revenue: name, annual rent, % of total revenue.
- Identify tenants on multiple suites/floors.
- Flag any single tenant > 25% of SF or revenue.
Step 8: Mark-to-Market (if market rent provided)
Per tenant:
- In-place rent/SF vs. market rent/SF.
- Delta (positive = below market/upside, negative = above market/risk).
- Aggregate below-market upside and above-market risk.
Step 9: Pipeline Overlay (if prospect pipeline provided)
- Overlay proposed deals on the stacking plan showing targeted suites.
- Show proposed terms: tenant, SF, proposed rent/SF, term.
- Calculate occupancy and revenue impact if all deals close.
- Flag conflicting prospects (multiple targeting same space).
Output Format
1. Visual Stacking Plan
Text-based floor-by-floor layout. Top floor at top, ground floor at bottom. Each block labeled with tenant, SF, and expiration.
2. Building Summary Dashboard
| Metric | Value |
|---|---|
| Total RSF | |
| Occupied SF | |
| Vacant SF | |
| Physical Occupancy | % |
| Number of Tenants | |
| WALT (by SF) | years |
| WALT (by Revenue) | years |
| Average Rent/SF | $ |
| Largest Contiguous Availability | SF (Floor X) |
3. Rollover Schedule
Table by year with SF and revenue, percentages, and cumulative.
4. Rollover Concentration Flags
Specific warnings with tenants driving the concentration.
5. Contiguous Space Analysis
| Block | Floors | Total SF | Status | Available |
|---|
6. Tenant Concentration Summary
Top 5 by SF and revenue with percentages.
7. Mark-to-Market Summary (if applicable)
Below-market upside and above-market risk, with tenant detail.
8. Pipeline Impact (if applicable)
Occupancy and revenue impact if pipeline deals close.
See references/stacking-plan-format.md for a complete 10-floor worked example including all output sections.
Red Flags and Failure Modes
Failure modes (require flagging):
- Floor SF mismatch: If the sum of all floor-level SF does not match
total_rsf, flag the discrepancy in the Building Summary and proceed with floor-level data, noting the gap explicitly. Do not silently reconcile. - Missing lease dates: If a tenant record is missing lease start or lease end, treat the tenant as MTM and flag in the output. Do not skip the tenant or silently omit from the rollover schedule.
- Missing required tenant fields: If name, floor, or SF is absent for a tenant, skip that record and list it as "skipped — incomplete data" in the output. Do not attempt to infer values.
- Conflicting prospect targets: If two or more prospects target the same suite, flag the conflict in the Pipeline Overlay section. Do not resolve it — surface it for the user.
Design conventions (not failure modes):
- Text-based by design: Output is text, not an image. Portable across chat, email, documents, presentations. Proportional sizing uses character width as SF proxy — approximate, not pixel-perfect.
- Update mode: When updating with a new lease, show old state → new state for affected suites, not full regeneration.
- Sort order: Always top floor first (descending). Industry standard convention.
- Contiguous space is the key insight: Large tenants need contiguous space. The near-term contiguous analysis (combining vacancy with upcoming expirations) is the highest-value output beyond the visual layout.
- Tenant vs. suite count: One tenant may occupy multiple suites. Count unique tenants, not suite entries.
Chain Notes
| Direction | Skill | Relationship |
|---|---|---|
| Upstream | rent-roll-formatter | Standardized rent roll is the primary input |
| Parallel | variance-narrative-generator | Occupancy changes visible in stacking plan explain revenue variances |
| Reference | closing-checklist-tracker | Stacking plan informs acquisition due diligence scope |
| Reference | property-tax-appeal-analyzer | Occupancy and lease data support income approach |
| Downstream | deal-underwriting-assistant | Stacking plan provides tenant-level detail for modeling |
These are reference docs that the agent consults when it needs deeper context, along with helper scripts it runs for calculations and output templates it fills in. The skill loads them on demand — you don't need to edit them to use the skill.
Click any file below to preview its contents.