Author: AI Analysis of all Encore OS module specs
Executive Summary
After analyzing the HR onboarding orchestration gaps, this document examines all other Encore OS modules for similar opportunities where existing specs are comprehensive but lack orchestrated, guided processes that tie multiple features together into cohesive user journeys. The HR onboarding analysis found that individual specs were strong, but the “glue” between them was missing. The same pattern exists across the platform.Recommendation Priority Overview
Recommendation 1: Resident Intake-to-Discharge Journey (RH)
The Pattern (Same as HR Onboarding)
Recovery Housing has strong individual specs (RH-01 through RH-07), but a resident’s journey from intake to discharge to alumni follow-up touches ALL of them. There is no unified view for either the House Manager (admin side) or the Resident (if self-service were added).Specs Involved
Gap: No Unified “Resident Journey Dashboard”
For House Managers: No single screen showing a resident’s complete status across all modules:- Where are they in their program phases? (RH-02)
- Are they attending required activities? (RH-04)
- Any safety events or incidents? (RH-03)
- When does discharge planning need to start? (RH-05)
- What’s their UDS testing status? (RH-03)
- Overall compliance score?
- Who is at risk of discharge (attendance issues, safety events)?
- Who is approaching phase transitions?
- Who needs discharge planning initiated?
- What’s the overall program completion rate?
Recommendation
Create a Resident Journey Dashboard (similar concept to the HR Welcome Hub/Command Center):@/platform/resident-journeyintegration layeruseResidentJourneyStatus(residentId, episodeId)hook aggregating RH-01 through RH-07- House Manager view: unified resident status page
- Program Manager view: cohort progress dashboard
- Automated alerts: approaching phase transition, discharge planning due, follow-up overdue
Why This Is P1
Recovery Housing is the core business domain. A resident falling through the cracks due to fragmented tracking directly impacts outcomes and compliance. This is the RH equivalent of the HR onboarding problem.Recommendation 2: Month-End Close Orchestration (FA)
The Pattern
FA-19 (Financial Close Management) exists as a spec for managing close checklists, but the actual month-end close process touches nearly every FA module. Today, the close process requires a finance team member to navigate across GL, AP, AR, bank rec, and reporting screens.Specs Involved
Gap: No “Close Cockpit” Tying Steps Together
FA-19 provides checklist management but does NOT automatically:- Show status of AP/AR close from FA-03/FA-05
- Verify bank reconciliation is complete (FA-06)
- Confirm depreciation has been run (FA-11)
- Check that all journal entries are posted (FA-02)
- Validate budget vs actual is generated (FA-08)
Recommendation
Create a Financial Close Cockpit that orchestrates across FA modules:@/platform/financial-closeintegration layer (or enhancement to FA-19)useCloseReadinessStatus(periodId)hook that checks each module’s close status- Visual close progress tracker: each step shows green/yellow/red
- Blocking logic: cannot lock period until all prerequisite steps are complete
- Auto-generate close checklist tasks from module statuses
Why This Is P1
Month-end close is a recurring, high-stakes process. Missing a step leads to incorrect financials, audit findings, and compliance issues. This directly affects trust in the platform for finance teams.Recommendation 3: Employee Offboarding Orchestration (HR + IT)
The Pattern
HR-03 has offboarding templates and IT-08 has IT offboarding workflows, but the full offboarding process crosses HR, IT, FM (equipment/badge return), and FA (final paycheck, benefits termination).Specs Involved
Gap
Same problem as onboarding: HR must check multiple screens. IT doesn’t know if the final paycheck is done. FM doesn’t know if IT has collected the laptop. No unified “this person is fully offboarded” confirmation.Recommendation
Create an Offboarding Command Center (mirror of the Onboarding Command Center):useOffboardingStatus(employeeId)hook aggregating HR-03, IT-08, HR-07, HR-11- Unified checklist showing all module statuses
- Critical path: access revocation must happen within 2 hours (SLA tracking)
- “Fully Offboarded” confirmation only when all modules confirm completion
Why This Is P1
Security risk. A terminated employee retaining system access is a compliance and security failure. This process needs the most orchestration urgency.Recommendation 4: New Regulation Compliance Rollout (GR)
The Pattern
When a new regulation or policy requirement hits (e.g., new HIPAA rule, new state licensing requirement), GR needs to coordinate across multiple modules: update policies (GR-01), schedule training (GR-02), update compliance checklists (GR-03), update risk assessments (GR-05), and potentially update HR credentialing requirements (HR-02).Specs Involved
Gap
No guided workflow for “we need to comply with X by date Y.” The compliance officer must manually navigate each module to ensure all steps are covered.Recommendation
Create a Compliance Rollout Wizard or guided checklist:- Input: regulation name, effective date, affected areas
- Auto-generates: tasks across GR-01 through GR-05
- Dashboard: rollout progress with deadline tracking
- Integration with HR-02 if credential requirements change
Why This Is P2
Important but less frequent than P1 items. New regulations don’t happen daily, but when they do, a missed step has significant consequences.Recommendation 5: New Facility/Site Setup Process (FM + RH + PF)
The Pattern
When the organization opens a new residential facility or office location, multiple modules need configuration: PF site setup, RH residence and bed inventory, FM asset registration, IT equipment deployment, HR staff scheduling, and GR compliance setup.Specs Involved
Gap
No guided “open a new site” process. Each team does their setup independently, leading to things being missed (e.g., FM never sets up PM schedules, GR compliance requirements aren’t configured).Recommendation
Create a New Site Setup Wizard (using PF-41 Module Wizard framework):- Multi-step guided process covering all modules
- Assigns tasks to appropriate teams (FM, HR, IT, GR)
- Tracks completion across all modules
- “Site Ready” confirmation when all prerequisites met
Why This Is P2
Infrequent but high-impact. Opening a new site without proper setup leads to compliance gaps, safety risks, and operational issues.Recommendation 6: Quarterly Planning Cycle (LO)
The Pattern
The EOS Level 10 meeting cycle (LO-06) drives quarterly planning where Rocks are set (LO-03), scorecards updated (LO-05), issues resolved (LO-07), and to-dos created (LO-04). While each spec works independently, the quarterly transition (closing one quarter, opening the next) involves touching all of them.Specs Involved
Gap
No “Quarterly Transition” guided process. Leaders must manually close rocks, set new ones, update scorecards, and clean up issues across separate screens.Recommendation
Create a Quarterly Transition Wizard:- Guided 5-step process: Review Rocks → Set New Rocks → Update Scorecards → Resolve Issues → Confirm
- Auto-carries forward incomplete rocks with option to modify
- Archives previous quarter data
- Generates quarterly summary report
Why This Is P2
Happens 4x per year. Not urgent but directly impacts strategic execution quality. Low effort since it mostly orchestrates existing CRUD operations.Recommendation 7: New Grant Setup & Compliance (FA + HR + GR)
The Pattern
Healthcare organizations frequently receive grants (government, foundation). A new grant requires setup in FA (project accounting, budget, cost allocation), HR (staff cost allocation), and GR (compliance tracking, reporting requirements).Specs Involved
Recommendation
Create a New Grant Setup Wizard that walks through all required configuration across FA and GR modules. This is a natural fit for the PF-41 Module Wizard framework.Why This Is P3
Grants are important but vary significantly in requirements. A flexible wizard with optional steps would be most valuable. Lower frequency than P1/P2 items.Recommendation 8: New Staff Onboarding for Housing Operations (RH + HR + GR)
The Pattern
When a new staff member (house manager, housing tech) is hired for recovery housing operations, their onboarding extends beyond standard HR onboarding (HR-03) to include RH-specific training and GR compliance.Additional Steps Beyond HR-03
Recommendation
Extend the HR Onboarding Orchestration (already planned) with an RH-specific template preset that includes:- Recovery housing training tasks
- Site assignment task
- Clinical oversight setup (if applicable)
- RH-specific compliance orientation
Why This Is P3
Naturally extends the HR onboarding work already planned. Low incremental effort since it’s adding a template preset, not building new infrastructure.Summary: Common Pattern Across All Recommendations
Every recommendation follows the same architectural pattern:@/platform/ integration pattern can be applied to all other recommendations with decreasing effort (the architecture is proven).
Implementation Sequencing
Phase A: HR Onboarding (Already Planned, ~4.5 weeks)
- Establishes the pattern
- Proves the architecture
- Highest organizational impact (every employee goes through onboarding)
Phase B: P1 Items (~6-8 weeks)
- Employee Offboarding (~2 weeks) — mirrors onboarding pattern, security-critical
- Resident Journey Dashboard (~3-4 weeks) — core business domain
- Financial Close Cockpit (~2-3 weeks) — recurring high-stakes process
Phase C: P2 Items (~4-6 weeks)
- Compliance Rollout Wizard (~2 weeks)
- New Site Setup Wizard (~2 weeks)
- Quarterly Transition Wizard (~1-2 weeks)
Phase D: P3 Items (~2-3 weeks)
- Grant Setup Wizard (~1-2 weeks)
- RH Staff Onboarding Preset (~3-5 days, extends HR work)
References
- HR Onboarding Process Guide
- HR Onboarding Orchestration Plan
- RH Module README
- FA Module README
- FM Module README
- GR Module README
- LO Module README
- IT Module README
Last Updated: 2026-02-08