Monthly executive rollup of pipeline state for the residential_multifamily
subsystem. Aggregates Dealpath (deal pipeline), Procore (active development
pipeline), and Intacct (capex commitment exposure) into a board-ready or
IC-ready summary. Designed for the executive and IC audiences with
per-metric confidence bands.
Scope: dollars committed at each pipeline stage, expected close by month,
IC docket forward 90 days, capex commitment exposure forward 12 months,
debt market context band, capital deployment pace vs target, declined deal
hit-rate, top-of-funnel sourcing health, JV partner concentration,
geographic concentration, segment concentration. Every metric declares a
confidence band.
Decision severity `gated`: the pack is board-ready. Any final-marked
external submission (board packet, IC advance read) is gated. The workflow
never sends autonomously; composition of the formal submission bundle lives
in `workflows/executive_operating_summary_generation`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Deal pipeline stage semantics, IC calendar, capital-deployment-pace targets,
JV-partner concentration thresholds, geographic and segment concentration
thresholds, debt market context, and board-packet templates live in overlays
and drift. Dealpath stage-to-canonical mapping is the Dealpath adapter
contract. Procore project-state semantics evolve with the construction-platform
release cycle. Intacct capex commitment exposure is period-sensitive and
supersedes prior loads once the period closes. Declined-deal resurrection
probability is an overlay construct; confidence bands on every metric are
explicit and sample overlays must be replaced before any output is treated as
a board-ready commitment.
Monthly executive rollup of pipeline state for the residential_multifamily
subsystem. Aggregates Dealpath (deal pipeline), Procore (active development
pipeline), and Intacct (capex commitment exposure) into a board-ready or
IC-ready summary. Designed for the executive and IC audiences with
per-metric confidence bands.
Scope: dollars committed at each pipeline stage, expected close by month,
IC docket forward 90 days, capex commitment exposure forward 12 months,
debt market context band, capital deployment pace vs target, declined deal
hit-rate, top-of-funnel sourcing health, JV partner concentration,
geographic concentration, segment concentration. Every metric declares a
confidence band.
Decision severity `gated`: the pack is board-ready. Any final-marked
external submission (board packet, IC advance read) is gated. The workflow
never sends autonomously; composition of the formal submission bundle lives
in `workflows/executive_operating_summary_generation`.
Executive Pipeline Summary
Workflow purpose
Produce the monthly executive-grade pipeline summary: the document that leaves
the investments and development teams and goes to the executive and to the IC.
The pack is a cross-system rollup, synthesizing deal-pipeline posture
(Dealpath), active development pipeline posture (Procore), and posted capex
commitment exposure (Intacct) into a narrative-first board-ready or IC-ready
document.
The pack composes the pipeline layer of the executive story. It sits alongside
workflows/executive_operating_summary_generation (operating posture) and
workflows/quarterly_portfolio_review (portfolio trend). Together these three
packs cover the three executive narrative arcs: operating, portfolio, pipeline.
This pack is gated. Any final-marked external submission (board packet, IC
advance read, capital-partner memo) requires row 16 (board) or row 17 (IC
advance read, if the overlay requires IC gating) before transmission. The
formal submission bundle composition lives in
workflows/executive_operating_summary_generation; this pack stops at the
narrative + dashboard and an opened approval request.
reference as_of_date + status + sample-tag surfacing
Output contract
Final-marked output MUST follow _core/executive_output_contract.md:
verdict-first block (recommendation, 3-bullet rationale, confidence,
materiality, next action), source-class labels on every numeric cell
([operator] / [derived] / [benchmark] / [overlay] /
[placeholder]), and refusal-artifact shape when a required reference
is absent. Any [placeholder]-tagged cell blocks board / IC approval
request assembly (rows 16 / 17).
Required context
Asset_class, segment (one or many), audience (board, ic, internal_executive),
org_id, period (month). Audience governs template and approval row. Fund_id is
required if the pack reports capital-deployment pace at fund grain. Board
calendar date is required if audience is board. IC calendar date is required
if audience is ic.
Process
Step 1. Audience resolution and period anchor
Resolve audience (board, ic, internal_executive). Load the corresponding
template and approval row:
board: row 16, board packet template.
ic: row 17 (if overlay requires IC gating; else advisory), IC advance-read
template.
Anchor the period (typically prior-month close). Every forward-looking metric
is computed relative to the anchor.
Step 2. Pipeline stage rollup
Pull the Dealpath deal register (per dealpath_deal_pipeline/normalized_contract.yaml
— Dealpath is primary for deal and asset through close per
source_of_truth_matrix.md). Bucket deals by stage:
sourced
loi_signed
psa_signed
ic_approved
debt_term_sheet
close
funded
declined
on_hold
Compute pipeline_stage_committed_dollars (proposed) per bucket: sum of
deal.deal_size (or whatever canonical field carries dollar commitment,
resolved via the Dealpath adapter contract). Counts + dollars.
If any deal fails the Dealpath DQ check (dp_completeness_ic_record,
dp_handoff_lag, other), surface as a blocker line in the reconciliation
posture section. Do not silently exclude.
Step 3. Expected close by month
For every deal with deal.expected_close_date populated, bucket by
forward month. Compute expected_close_by_month (proposed): forward 12
months, counts + dollars. Annotate any deal whose expected_close_date is in
the past and whose stage is not close / funded / declined —
stage-mapping inconsistency routes to development/investments data hygiene.
Step 4. IC docket forward 90 days
Pull deal_milestone.ic_scheduled_date across open deals within the next 90
days. Compute ic_docket_forward_90d (proposed): per-deal row with deal_size,
stage, jv_partner, market, segment, and ic_scheduled_date. Sort by
ic_scheduled_date.
For each deal on the docket, annotate readiness state (per overlay: diligence
complete, debt term sheet status, committee materials ready). Readiness drift
is advisory here; IC-prep orchestration lives in
workflows/pre_close_deal_tracking and related packs.
Pull the Procore commitment register per the active development pipeline.
Compute capex_commitment_forward_exposure_dollars (proposed): sum of
open_commitment.remaining forward 12 months across all active projects. This
metric is inherited from workflows/development_pipeline_tracking; reuse the
computed value rather than recomputing unless the development pipeline tracker
has not run within the overlay-defined freshness window.
For each commitment, check pc_recon_commitment_overdrawn. Any overdrawn
commitment is surfaced here as a material blocker in the pipeline-to-posted-spend
reconciliation — route to Procore runbook commitment_overdrawn. Do not
propose capex reallocation here; that is
workflows/cost_to_complete_review + capex capital overlay.
Read debt_market_context_band (proposed) from debt-market overlay. This is
a categorical band (tight, neutral, loose), cited not computed. The
overlay carries the update cadence and the reasoning for the current band;
the pack surfaces both.
Forward implications: any band shift changes the close-certainty commentary on
deals in debt_term_sheet stage. Annotate the linkage; do not re-underwrite
deals here.
Step 7. Capital deployment pace vs target
Read fund capital-deployment plan. Compute capital_deployment_pace_vs_target
(proposed): (capital_deployed_ytd / capital_deployment_target_ytd) per fund
overlay. capital_deployed_ytd is the sum of equity-call deployments ytd per
the fund's capital overlay; capital_deployment_target_ytd is the fund's ytd
deployment plan frozen at fund start or at the most recent approved plan
amendment.
Flag any fund where capital_deployment_pace_vs_target (proposed) is below
the overlay band (typically 0.85 floor) — escalate to cfo_finance_leader +
investments_lead. Do not propose a re-calibration here; that is fund-level
capital overlay.
Step 8. Declined deal hit rate
Pull declined-deal register for the trailing 12 months. For each declined
deal, check whether the same asset (via asset_crosswalk) or substantially
similar asset transacted elsewhere within 12 months. Compute
declined_deal_hit_rate (proposed): (declined_deals_that_transacted_elsewhere /
total_declined_deals_in_period).
Attribution categories: priced-out (competitor paid above our underwriting),
diligence-findings (we declined for a discoverable risk), market-timing
(declined pre-market-move), stale-pipeline (declined and not transacted).
Cohort the hit rate by attribution category.
This metric backtests IC decision discipline. Not a proxy for
"should we have bought it" in isolation — overlay commentary governs
interpretation.
Step 9. Top-of-funnel sourcing health
Compute top_of_funnel_sourcing_health (proposed): composite of
(new_deals_added_T30, broker_sourced_share, repeat_broker_share,
direct_sourced_share) from the sourcing funnel log. Compare to sourcing
overlay targets.
Low direct-sourced share or rising share from a small number of repeat
brokers is a concentration signal — route to development_lead for sourcing
coverage review.
Step 10. JV partner concentration
Compute jv_partner_concentration (proposed): per-partner dollar exposure
across pipeline + owned. Compare to portfolio_concentration_targets.csv
(partner thresholds) and to the owned-asset JV mix.
Flag any partner whose combined pipeline + owned exposure crosses overlay
threshold — escalate to portfolio_manager + investments_lead.
Step 11. Geographic and segment concentration
Compute:
geographic_concentration_pipeline (proposed): market share of
pipeline_stage_committed_dollars (proposed).
segment_concentration_pipeline (proposed): segment share of
pipeline_stage_committed_dollars (proposed).
Compare to portfolio_concentration_targets.csv and to owned-asset
concentration from portfolio_concentration_market (canonical). The narrative
covers both pipeline and owned, so concentration movement across the
pipeline-to-owned bridge surfaces.
Flag any crossing of overlay threshold — escalate to portfolio_manager +
investments_lead.
Step 12. Confidence bands per metric
For every metric surfaced, compute confidence_band_per_metric (proposed):
categorical (low, medium, high) derived from:
The pack composes the draft and opens the approval request; it does not send.
Step 16. Approval routing
Row 16 (board final) for board audience.
Row 17 (IC advance-read) for IC audience if overlay requires IC gating.
Internal executive: advisory; overlay governs whether gated. Usually
draft_for_review.
The workflow never releases a submission marked final without an approved
row. Transmission composition lives in
workflows/executive_operating_summary_generation.
Step 17. Confidence banner
Every reference surfaced with as_of_date and status. Proposed metrics
flagged. Cross-system posture summary: Dealpath primary for deal pipeline;
Procore primary for active development + commitments; Intacct primary for
posted capex spend + capital deployment (where applicable). Per-metric
confidence bands are surfaced prominently; the board-ready output carries a
dedicated confidence section.
Row 16 (board final submission) for board-audience finals.
Row 17 (IC advance-read) for IC-audience finals where overlay requires
IC gating.
Internal executive summaries are advisory; overlay governs. Default is
draft_for_review.
No autonomous release of any final-marked external document. Transmission
pathway composition lives in workflows/executive_operating_summary_generation.
Failure modes
Reporting pipeline dollars without confidence bands. Fix: every metric
carries a confidence_band_per_metric (proposed); board-ready output
surfaces the band.
Silently excluding deals failing Dealpath DQ. Fix: DQ blockers are cited
as a blocker line; affected metrics are not silently reduced.
Recomputing capex commitment forward exposure. Fix: inherit from
workflows/development_pipeline_tracking; only recompute if the tracker
has not run within freshness window.
Authoring pricing or re-underwriting language in the debt market context
section. Fix: debt market context is a cited categorical band; individual
deal re-underwriting lives in deal-level packs.
Proposing capital deployment pace corrections. Fix: fund-level capital
overlay governs; this pack reports posture only.
Proposing a JV partner / market / segment concentration cap change. Fix:
portfolio_concentration_targets.csv is overlay-driven; this pack reports
breach and escalates.
Treating declined_deal_hit_rate as "should we have bought it". Fix:
overlay commentary governs interpretation; cohort attribution is required.
Sending the board packet. Fix: transmission is gated at row 16.
Missing IC docket readiness drift because IC-prep orchestration is
downstream. Fix: surface readiness drift as advisory; do not attempt to
orchestrate IC prep here.
Sample overlay used as authoritative debt market context. Fix: debt
market context band carries its own as_of_date + status; sample is
surfaced explicitly.
Letting a Procore commitment-overdrawn finding silently pass into the
capex commitment exposure metric. Fix: pc_recon_commitment_overdrawn
downgrades the metric to low confidence and appears in the
reconciliation memo.
Edge cases
Declined deal resurrection. A previously-declined deal re-enters the
pipeline (new sponsor group, re-offering, recapitalization). The pack
flags the resurrection with an audit trail citation to the original
decline and attribution category. Any re-engagement requires an explicit
executive decision — do not default to pipeline inclusion without
investments_lead confirmation.
Multi-asset closing in same period. Two or more closings land in the
same month; pipeline_stage_committed_dollars (proposed) swings
materially between close and funded. Narrative distinguishes between
scheduled close and actual funded to avoid double-counting. Forward
capex commitment exposure steps up once Procore projects execute —
dp_handoff_dev_lag watch begins immediately for each new closing.
Board-meeting freeze. Board-calendar freeze window bans in-flight
changes to the pipeline narrative. Pack behavior: if invoked during
freeze, produce the narrative + dashboard but defer approval_request
row 16 opening until freeze lifts; annotate the freeze in the output.
IC docket shift mid-month. An IC meeting moves forward or back
within the 90-day window. Recompute ic_docket_forward_90d (proposed)
at each invocation — do not cache across invocations.
JV partner with multiple deal vehicles. A single partner holds
positions across multiple fund vehicles. Aggregate per-partner exposure
across vehicles for jv_partner_concentration (proposed); annotate the
cross-fund concentration per overlay.
Fund mid-close. A fund closes mid-period; capital_deployment_target_ytd
shifts. Use the most recently approved plan as the denominator; annotate
the amendment date.
Debt market overlay stale. Debt market context band not updated
within overlay freshness window. Surface the stale as explicit; the
metric drops to low confidence; narrative does not assert market
direction.
Declined pool concentration on a single attribution category. If the
share of declines attributed to a single category exceeds the
declined_pool_attribution_concentration_band from
reference/normalized/schemas/reconciliation_tolerance_band.yaml, the
narrative surfaces the concentration as a sourcing / underwriting signal
— escalate to investments_lead for discipline review.
Pre-close deal with no expected_close_date. Deal lacks
deal.expected_close_date in Dealpath. Annotate as a Dealpath DQ gap;
do not impute. Affects expected_close_by_month (proposed) confidence.
Pipeline asset crosswalk ambiguity.asset_crosswalk.yaml does not
resolve the pipeline asset to a single canonical asset_id (duplicate
match or no match). Flag; do not collapse. Declined-deal hit rate
computation excludes the ambiguous row until resolved.
Example invocations
"Build the monthly executive pipeline summary for April 2026; audience board."
"IC docket forward 90 days; include readiness drift annotations."
"Capital deployment pace vs target for the core fund this month."
"Concentration check — pipeline + owned — by market and JV partner."
"Declined deal hit rate for Q1 2026 with attribution cohorts."
Audience. Board. Row 16 approval will open on final.
Pipeline stage rollup.
Stage
Count
Dollars
Confidence
sourced
18
$485M
medium
loi_signed
6
$210M
medium
psa_signed
4
$165M
high
ic_approved
2
$92M
high
debt_term_sheet
3
$118M
medium
close
1
$48M
high
funded
2 (April)
$86M
high
declined (T30)
7
$305M
high
on_hold
3
$110M
medium
pipeline_stage_committed_dollars (proposed) aggregated above. Two deals
funded April; three deals in debt_term_sheet stage are exposed to
debt_market_context_band (proposed) = neutral per overlay.
Expected close by month.expected_close_by_month (proposed):
Month
Count
Dollars
May
1
$48M
June
2
$88M
July
1
$45M
Aug
0
$0
Sep
1
$35M
Oct-Mar
6
$240M
IC docket forward 90 days.ic_docket_forward_90d (proposed):
IC date
Deal
Deal size
Stage
JV partner
Market
Readiness
2026-05-12
Highland Mill
$48M
psa_signed
None
Charlotte
ready
2026-05-12
Glenwood Flats
$52M
loi_signed
Partner_B
Nashville
diligence_gap
2026-06-09
Ridge Park
$40M
loi_signed
None
Dallas
ready
2026-07-14
Brookline
$38M
psa_signed
Partner_A
Atlanta
debt_term_sheet_pending
Capex commitment forward 12 months.capex_commitment_forward_exposure_dollars (proposed) = $312M across 11 active
construction projects. Inherited from workflows/development_pipeline_tracking
run 2026-04-10 (within freshness window). Two commitments overdrawn on
Riverbend (cite pc_recon_commitment_overdrawn); metric confidence band =
medium until resolved.
Debt market context.debt_market_context_band (proposed) = neutral
per debt_market overlay as-of 2026-03-31 (sample). Overlay staleness within
tolerance; confidence = medium.
Capital deployment pace. Core fund:
capital_deployment_pace_vs_target (proposed) = 0.94 ytd. Within band (0.85
floor). Confidence = high.
Confidence bands summary. Per-metric confidence ranges from medium
(pipeline stage dollars at sourced / loi_signed, debt market context,
commitment exposure due to Riverbend recon blocker) to high (closed /
funded dollars, declined hit rate, concentration rollups). No low
confidence metric surfaced without explicit narrative treatment.
Reconciliation posture. Two Procore commitments overdrawn on Riverbend
(pc_recon_commitment_overdrawn blocker) — runbook pointer surfaced;
capex commitment exposure confidence = medium until resolved. One Dealpath
DQ warning (dp_handoff_lag) on a Q1 closed deal — development_lead
notified. No Intacct posting-lag blockers.
Top-3 pipeline watch items.
Riverbend commitment overdrawn — construction + asset_mgmt priority;
capex commitment exposure confidence = medium until resolved.
Repeat-broker share above overlay — route to development_lead for
broker-coverage review; no sourcing blocker yet but trending.
Partner_A JV concentration at 14.2% vs 15% cap — watch-item; next
month's board update if Partner_A's May deal closes.
Draft board packet section. Composed per overlay template; cited
metrics; confidence bands per metric surfaced prominently; reconciliation
memo included as appendix.
Approval request.approval_request row 16 opened; pending board final
submission. Transmission pathway through
workflows/executive_operating_summary_generation.
