Section 20

§20 — Third-Party Asset / Property / Leasing Services (Pointer)

Status: [POINTER — content lives in privileged side memo]

20.1 Posture (master-doc-level only)

Assembly Atlanta engages third-party services for portions of the asset / property / leasing management workstream. The relationship is governed by contract, with reporting cadence integrated into the §18 reporting stack.

Where commentary on any specific third-party relationship belongs: in a privileged, officer-and-CEO-only side memo — not in this master document. This is a deliberate cleanliness decision.

20.2 What the master doc says, and does not say

Says:

  • Third-party services exist within a defined scope.
  • Reporting from third parties feeds the §18 stack on cadence.
  • Where a third-party reporting cadence drops, the §22 register tracks the gap (open item, dated, owner).

Does not say:

  • Names of individual relationship-holders.
  • Commercial terms.
  • Characterization of any specific firm's performance.

That detail lives in the corresponding side memo, addressed to the officer + CEO only.

20.3 Side memo reference

→ master_doc/side_memos/20_jll_side_memo.md (privileged; officer + CEO only).

The principle: a master operating document does not litigate vendor relationships. The side memo handles that work, structurally and calmly.