implementation-intake-and-leader-sign-off-builder

name	Implementation Intake And Leader Sign-Off Builder
slug	implementation_intake_signoff_builder
version	0.1.0
status	draft
category	residential_multifamily
subsystem	residential_multifamily
pack_type	workflow
targets	["claude_code"]
stale_data	This workflow stores interview state, evidence references, assumptions, blockers, and packet previews in a local session workspace. Those records become stale when source systems change, reporting calendars move, owners change, or new artifacts arrive. The workflow never treats assumptions as confirmed without explicit evidence.
applies_to	{"segment":["middle_market","affordable","luxury"],"form_factor":["garden","walk_up","wrap","suburban_mid_rise","urban_mid_rise","high_rise"],"lifecycle":["pre_acquisition","development","construction","lease_up","stabilized","renovation","recap_support","disposition"],"management_mode":["self_managed","third_party_managed","owner_oversight"],"role":["coo_operations_leader","cfo_finance_leader","director_of_operations","regional_manager","asset_manager","portfolio_manager","development_manager","construction_manager","reporting_finance_ops_lead","third_party_manager_oversight_lead"],"output_types":["memo","checklist","operating_review","dashboard"],"decision_severity_max":"action_requires_approval"}
references	{"reads":["workflows/implementation_intake_signoff_builder/question_bank.yaml","workflows/implementation_intake_signoff_builder/evidence_model.yaml","workflows/implementation_intake_signoff_builder/interview_modes.md","workflows/implementation_intake_signoff_builder/workflows.md","workflows/implementation_intake_signoff_builder/schemas/source_inventory_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/source_instance_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/export_field_inventory_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/credentials_model_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/crosswalk_rules_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/source_of_truth_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/reporting_calendar_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/blocker_log_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/assumptions_log_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/decision_log_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/evidence_item_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/signoff_packet_schema.yaml","workflows/implementation_intake_signoff_builder/schemas/action_queue_schema.yaml","workflows/implementation_intake_signoff_builder/templates/implementation_intake_packet_template.md","workflows/implementation_intake_signoff_builder/templates/signoff_packet_template.md","workflows/implementation_intake_signoff_builder/templates/action_queue_template.md","tailoring/AUDIENCE_MAP.md","tailoring/MISSING_DOC_MATRIX.md","reference/connectors/source_registry/source_registry.yaml","reference/connectors/source_registry/implementation_inventory.md","reference/connectors/_core/config_overlay_interaction.md","reference/connectors/_core/third_party_manager_oversight.md","reference/connectors/master_data/identity_resolution_framework.md","reference/connectors/master_data/survivorship_rules.md","reference/connectors/adapters/appfolio_pms/manifest.yaml","reference/connectors/adapters/sage_intacct_gl/manifest.yaml","reference/connectors/adapters/procore_construction/manifest.yaml","reference/connectors/adapters/dealpath_deal_pipeline/manifest.yaml","[Truncated]"],"writes":["workflows/implementation_intake_signoff_builder/sessions/{engagement_id}/{session_id}.yaml","workflows/implementation_intake_signoff_builder/sessions/{engagement_id}/{session_id}__preview.md","workflows/implementation_intake_signoff_builder/sessions/{engagement_id}/{session_id}__leader_signoff.md","workflows/implementation_intake_signoff_builder/sessions/{engagement_id}/{session_id}__action_queue.md"]}
metrics_used	[]
escalation_paths	[{"kind":"missing_load_bearing_evidence","to":"implementation_pm -> executive_sponsor"},{"kind":"conflicting_source_of_truth","to":"data_lead -> business_owner -> executive_sponsor"},{"kind":"blocked_access_or_approval","to":"system_owner -> implementation_sponsor"},{"kind":"secret_storage_attempt","to":"refuse and require metadata-only capture"}]
approvals_required	["implementation_scope_signoff","access_provisioning_signoff","crosswalk_approval","source_of_truth_approval","leader_signoff_packet_approval"]
description	Evidence-driven implementation intake workflow for residential multifamily and related CRE operating environments. Guides sponsors, implementation leads, data teams, operations leaders, and reporting owners through source inventory, access readiness, export evidence, field-level semantics, crosswalk ownership, reporting calendar, approvals, blockers, assumptions, and final leader sign-off. Produces implementation packets that are usable by both executives and build teams, while refusing silent assumption upgrades and refusing secret storage.

Implementation Intake And Leader Sign-Off Builder

Workflow purpose

Capture the real implementation facts required to move from architecture and planning into build execution. The workflow is evidence-led, progressive, resumable, and explicit about what is confirmed, what is only assumed, what is missing, what is blocked, who owns each unresolved item, and what leadership is being asked to approve.

This workflow is designed for mixed operating environments: direct-system access, file-only third-party manager submissions, legacy-system coexistence, construction and development stacks, benchmark workbooks, shared-drive reports, and emailed operating packs. It does not accept vague statements like "we use AppFolio" as implementation-ready.

Trigger conditions

• Explicit: "implementation intake", "implementation discovery", "sign-off memo", "sign-off packet", "systems and environments covered", "capture source inventory", "gather evidence for build readiness", "prepare leadership sign-off".
• Implicit: connector onboarding cannot proceed because source scope, environments, field layouts, approvals, or owners are still unclear.
• Recurring: resume sessions, missing-doc chase, and leadership-review refresh before a build phase or milestone gate.

Inputs (required / optional)

Input	Type	Required	Notes
Sponsor objective and implementation scope	narrative	required	plain-language objective, scope, and success definition
Source inventory	register	required	systems, modules, environments, owners, status
Evidence set	register	required	artifacts, screenshots, exports, report packs, mappings
Export and field inventory	register	required	actual files, tabs, columns, sample values, quirks
Access model	register	required	access path, provisioning flow, approvals, restrictions
Crosswalk and source-of-truth rules	register	required	entity keys, precedence, overrides, approval owner
Reporting calendar and SLA map	register	required	close, reviews, owner reporting, approvals
Missing-doc and blocker log