Task guide

Build a Mixed-Use document

Combine Retail, Office, Residential, Industrial, Hotel, and Storage components in one property workflow.

30 to 75 minutesFor Teams marketing properties with multiple integrated usesAdvancedLast verified September 6, 2026

Outcome

The document identifies each real component and presents its data with the correct component-specific terminology.

Navigation path

Create New > Mixed-Use > Document wizard

Access

Document creation access

On this page

Before you start

Data, sources, and access to prepare

  • A single integrated property with at least two supported uses
  • Source data separated by component

Distinguish Mixed-Use from multi-property

Populated mixed use editor showing the property-specific fields used in this example.
Review the populated mixed use example and verify the units, property facts, and applicable model before preparing your own document.

One property, multiple components

Mixed-Use keeps one subject property while component tags control financial sub-tables.

  • One PropertyRetail and Office
  • One PropertyResidential
  • One PropertyIndustrial, Hotel, Storage
  • Retail and OfficeCombined Document
  • ResidentialCombined Document
  • Industrial, Hotel, StorageCombined Document
Distinguish Mixed-Use from multi-property
Use Mixed-Use whenUse Multiple Properties when
One integrated property has several usesSeveral buildings, parcels, or addresses need separate records
One subject-level address and property storyEach building needs its own address, type, and data
Financial rows should be grouped by componentFinancial rows should be grouped by building or portfolio

Use the six supported components

Use the six supported components field reference
FieldRequirementWhat it meansFormatUnitsSave behaviorDownstream effect
RetailOptionalCommercial retail tenant fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; a component with saved rows cannot be deselected until those records are addressed.Opens Retail commercial tenant rows under the one global projection choice.
OfficeOptionalCommercial office tenant fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; a component with saved rows cannot be deselected until those records are addressed.Opens Office commercial tenant rows under the one global projection choice.
ResidentialOptionalMultifamily unit fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; a component with saved rows cannot be deselected until those records are addressed.Opens Residential unit inventory with its selected detail layout under the one global projection choice.
IndustrialOptionalCommercial industrial tenant fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; a component with saved rows cannot be deselected until those records are addressed.Opens Industrial commercial tenant rows under the one global projection choice.
HotelOptionalRoom Inventory fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; saved hotel rows must be resolved before removing the component.Opens the specialized Hotel Room Inventory under the one global projection choice.
StorageOptionalSelf-Storage unit fields.Selectable component typeNot applicableThe Rent Roll by Component selection persists with the Mixed-Use configuration; a component with saved rows cannot be deselected until those records are addressed.Opens Storage unit inventory with its selected detail layout under the one global projection choice.

Required means the field is needed to complete or support this workflow. Some screens allow a draft to save before every required item is complete. The steps and troubleshooting call out controls the product actively blocks.

One projection choice

The Mixed-Use rent roll uses one global Cash Flow or Pro Forma selection for all active components. Non-hotel components then choose Unit-by-Unit or Unit Mix.

Complete the Mixed-Use workflow

Mixed-Use steps

  1. 1

    Select Mixed-Use

    Create New, Select Property Type

    Choose Mixed-Use for one integrated multi-use subject.

    Expected result: Rent Roll by Component becomes the financial label.

    If this does not happen: Use Multiple Properties instead if each asset needs its own address and property record.

  2. 2

    Enter the shared address

    Property Details

    Enter the subject street address.

    Expected result: The Mixed-Use document has one shared subject location.

    If this does not happen: Use Multiple Properties instead if the components require separate addresses.

  3. 3

    Enter the shared area

    Property Data

    Enter the subject building or land area.

    Expected result: The shared size appears in property metrics.

    If this does not happen: Use the unit shown beside the field and do not add component areas twice.

  4. 4

    Enter the shared asking price

    Property Data

    Enter the subject asking price when the engagement uses one.

    Expected result: The document can calculate shared price metrics.

    If this does not happen: Leave the field empty when the engagement intentionally does not publish a price.

  5. 5

    Write the shared description

    Property Overview

    Write the property-level description.

    Expected result: The narrative describes the integrated subject rather than one component.

    If this does not happen: Move component-specific economics to the financial sections.

  6. 6

    Write the shared highlights

    Property Highlights

    Enter the property-level highlights.

    Expected result: The highlights summarize benefits that apply to the integrated subject.

    If this does not happen: Remove duplicate or component-only claims before continuing.

  7. 7

    Build the shared map

    Maps

    Configure the subject map.

    Expected result: The map represents the one integrated property location.

    If this does not happen: Use a multi-property document if separate subject markers are required.

  8. 8

    Choose the global projection

    Rent Roll by Component

    Select Cash Flow or Pro Forma once.

    Expected result: Every component uses the selected projection model.

    If this does not happen: Resolve any model-change warning before editing component records.

  9. 9

    Activate a component

    Rent Roll by Component

    Select one component checkbox.

    Expected result: The selected component has an editor.

    If this does not happen: Repeat this step for each real component. A component with saved data cannot be deselected until its records are addressed.

  10. 10

    Choose the component layout

    Active component tab > detail layout

    Select the detail layout that matches the source when the choice is offered.

    Expected result: The component displays the intended row structure.

    If this does not happen: Return to the layout choice before entering rows if the structure is wrong.

  11. 11

    Enter component inventory

    Active component tabs

    Enter the component-specific rows.

    Expected result: Each component subtotal reconciles.

    If this does not happen: Resolve unassigned legacy rows and verify specialized Hotel data persists.

  12. 12

    Complete combined statement

    Income & Expenses

    Enter property-level additional income and operating expenses without duplicating component revenue.

    Expected result: Combined EGI and NOI reconcile.

    If this does not happen: Trace duplicated or missing income by component first.

  13. 13

    Review combined output

    Review & Customize

    Inspect component headings, subtotals, combined totals, terminology, and page flow.

    Expected result: The final document presents one coherent Mixed-Use asset.

    If this does not happen: Return to Rent Roll by Component for incorrect tags or totals.

Resolve Mixed-Use classification issues

The property needs separate addresses

Likely cause: It may be a portfolio rather than one Mixed-Use subject.

  1. Use Multiple Properties.
  2. Create one building record per address.
  3. Assign each building its own type.
A component cannot be removed

Likely cause: It owns saved rows.

  1. Review that component.
  2. Move or remove its data intentionally.
  3. Then deselect it.
A component needs a different projection

Likely cause: Mixed-Use allows one global projection.

  1. Choose the model that best fits the document.
  2. Explain any component-specific limitation in notes.
  • One integrated subject confirmed
  • All real components active
  • One projection selected
  • Component subtotals reconcile
  • No relevant unassigned rows
  • Combined output reviewed

Was this guide helpful?