AFL readiness
Audit afl-2025-11-04 · run 2025-11-04T14:22:00Z · 730-day window. Imported scores are shown exactly as the audit produced them.
Overall readiness score
84.8
Not safe for executive distribution yet. Enough critical fields are unpopulated that headline metrics will understate or misstate performance.
Critical issues
14
Tier 1 — blocking for reporting
High issues
17
Tier 2 — core reporting fields
Warnings
9
Tier 3 and 4 — enhancing fields
Records audited
2,968,967
17 source objects
Rows with gaps
1,657,477
1,311,490 clean rows
Gap rate
55.83%
Share of audited rows with at least one gap
Status
At Risk
4 modules scored
Overall readiness
Weighted T1 40 / T2 30 / T3 20 / T4 10.
Readiness by module
Authoritative module scores from the audit export.
Authorizations
Mostly Ready88.2
241,884 of 486,210 rows have gaps · 3 critical
Clinical Productivity
Mostly Ready91.4
612,449 of 1,204,338 rows have gaps · 2 critical
Capacity and HR
At Risk82.7
366,212 of 611,402 rows have gaps · 4 critical
Financial
At Risk76.9
436,932 of 667,017 rows have gaps · 6 critical
Top 5 findings
Highest-severity gaps by affected records.
| Severity | Module | Field | Issue | Records affected |
|---|---|---|---|---|
| T1 · Critical | Capacity and HR | insights.StaffSchedule.ScheduledHours | A share of schedule rows resolve to Unknown scheduled hours, which makes utilization, fill rate and capacity forecasting unreliable. | 118,224 |
| T1 · Critical | Capacity and HR | insights.StaffSchedule.WorkedHours | A share of delivered sessions resolve to Unknown worked hours, so productivity cannot be compared against schedule. | 96,508 |
| T1 · Critical | Authorizations | dw2.FactAuthorization.AuthEndDate | 12.6% of authorizations have no end date, so they never enter the expiring-authorization window. | 61,262 |
| T1 · Critical | Financial | dw2.FactPayment.PaymentPostedDate | 31.8% of payments have no posted date, so collections aging and cash velocity are unreliable. | 59,912 |
| T1 · Critical | Authorizations | dw2.FactAuthorization.AuthManager | Some authorizations have no Auth Manager assigned, so nobody owns the renewal follow-up and expiring approvals surface late. | 48,310 |
Dashboard readiness summary
Which reporting use cases are safe to publish today.
Executive Reporting
9 critical · 12 high
85.4Mostly ReadyAuthorization Utilization
5 critical · 4 high
88.9Mostly ReadyAuthorization Renewal
5 critical · 3 high
88.1Mostly Ready97153 Productivity
1 critical · 2 high
87.8Mostly Ready97155 Supervision and Compliance
1 critical · 3 high
81.8At RiskScheduling and Attendance
4 critical · 2 high
73.2At Risk
Most important fixes
Where to work first inside CentralReach.
ScheduledHours
Correct schedule templates and appointment durations in Scheduling so every row resolves to real hours.
Fix in: Scheduling
WorkedHours
Ensure sessions are converted and timed correctly in Clinical > Sessions before period close.
Fix in: Scheduling
AuthEndDate
Backfill AuthEndDate from the payor approval letter and make the field required at authorization entry in CentralReach.
Fix in: Billing > Authorizations
PaymentPostedDate
Repost the affected payments with their remittance dates and automate posting-date capture from the 835.
Fix in: Payor / Funding Source setup
AuthManager
Assign an Auth Manager to every active authorization in Billing > Authorizations and default it from the client's primary BCBA.
Fix in: Billing > Authorizations
6 dashboard areas are currently blocked or at risk for AFL.