Demo tenantFabricated data only. No reveal control exists for masked or relay values, for any role.

Reports

Everything here is derived from the append-only transition ledger and the access register. Dwell time is attributed to the party the item was actually waiting on.

3.9d
Median cycle time
22 items completed end to end
5.0d
90th percentile
8.0d
Worst completed
425
Open items
20.1d
Oldest open item
since its last transition
45,709h
Tracked dwell
across every ladder rung

Party attribution — where the time actually goes

The answer to “why did it take 25 days”. Each interval between two ledger events is charged to the party the item was waiting on.

Us (CAM)ClientEmployee
PartyOpenMean wait> 2 days
Us (CAM)15323.1h2
Client406d 00h34
Employee1864d 18h155

Of 45,709 tracked hours, 18% sat with the client and 51% with the employee. CAM held 31% and has 2 item(s) older than two days.

PartyRungs handledMean handling
Us (CAM)3531d 07h
Client731d 08h
Employee661d 07h

Dwell hours by party, per client and work queue

Commercial Advantage
Northgate Health · 206 items
24,878h
Government Programs
Northgate Health · 78 items
8,706h
Denials Management
Northgate Health · 66 items
7,424h
Managed Care Review
Meridian Care · 51 items
4,700h

Stage cycle-time medians — portal ladder

After a rung is submitted, how long the item then sits with the party that owns the next rung.

Rung 1 → waiting on Client
43 segment(s) · p90 6d 08h
1d 18h
Rung 2 → waiting on Us (CAM)
34 segment(s) · p90 2d 08h
1d 08h
Rung 3 → waiting on Us (CAM)
2 segment(s) · p90 20.6h
20.2h
Rung 3 → waiting on Employee
24 segment(s) · p90 5d 18h
3d 20h
Rung 4 → waiting on Us (CAM)
4 segment(s) · p90 18.7h
16.5h

Launched vs completed, by week

Volume in, volume out, and the median end-to-end cycle time of what came out.

05811617423214 Sept: 3 launched14 Sept: 0 completed14 Sept21 Sept: 2 launched21 Sept: 4 completed21 Sept28 Sept: 0 launched28 Sept: 1 completed28 Sept5 Oct: 3 launched5 Oct: 0 completed5 Oct12 Oct: 14 launched12 Oct: 6 completed12 Oct19 Oct: 57 launched19 Oct: 7 completed19 Oct26 Oct: 232 launched26 Oct: 3 completed26 Oct2 Nov: 136 launched2 Nov: 1 completed2 Nov21 Sept: median 4.0d to complete28 Sept: median 4.6d to complete12 Oct: median 3.4d to complete19 Oct: median 3.9d to complete26 Oct: median 4.5d to complete2 Nov: median 2.9d to complete5d
Launched Completed Median cycle time (right axis)

Project coverage

People assigned to a work queue, people actually launched, and people holding the complete mandatory set.

0 of 31 people fully provisioned · 4% of mandatory items complete
Work queueClientAssignedLaunchedComplete set
Commercial AdvantageNorthgate Health11150
Government ProgramsNorthgate Health360
Denials ManagementNorthgate Health350
Managed Care ReviewMeridian Care350

Mandatory items complete

Commercial AdvantageNorthgate Health
6 / 204 · 3%
Government ProgramsNorthgate Health
2 / 72 · 3%
Denials ManagementNorthgate Health
4 / 60 · 7%
Managed Care ReviewMeridian Care
5 / 50 · 10%

Where the mandatory set is sitting

Commercial Advantage
204 mandatory items
6 done
Government Programs
72 mandatory items
2 done
Denials Management
60 mandatory items
4 done
Managed Care Review
50 mandatory items
5 done
CompleteWith CAMWith clientWith employeeBlockedNot started

Identifiers per employee

The question the spreadsheet cannot answer: how many sign-ins does one person hold, and across how many client accounts.

Mandated buckets

Identifiers heldEmployees
10
20
30
4+20

Every employee in this estate sits in the 4+ bucket, so the mandated split collapses into one row. The band on the right keeps the real distribution visible.

Distribution

7–9 identifiers
2 people
10–12 identifiers
9 people
13–15 identifiers
5 people
16+ identifiers
4 people
12
Median per employee
19
Most held by one person
2
Most client accounts

Active vs inactive, per client account

Inactive means dormant, expired or revoked — the credentials nobody has confirmed.

ActivePendingDormantExpiredRevoked
Northgate Health
69 active · 169 inactive
245
Meridian Care
5 active · 16 inactive
21

Active vs inactive, per portal

Top portals by identifier count.

ActivePendingDormantExpiredRevoked
Northgate Appeals Workbench
Northgate Health · 8 active · 12 inactive
20
Northgate Prior Authorization Desk
Northgate Health · 4 active · 15 inactive
20
Northgate Reporting Studio
Northgate Health · 4 active · 15 inactive
19
Northgate Document Exchange
Northgate Health · 2 active · 16 inactive
18
Northgate Eligibility Gateway
Northgate Health · 6 active · 12 inactive
18
Northgate Member Lookup
Northgate Health · 3 active · 14 inactive
18
Northgate Remittance Viewer
Northgate Health · 5 active · 13 inactive
18
Northgate Contract Rate Lookup
Northgate Health · 11 active · 6 inactive
17
Northgate Credentialing Registry
Northgate Health · 11 active · 3 inactive
17
Northgate Provider Portal - Commercial
Northgate Health · 2 active · 13 inactive
17
Northgate Claims Status Console
Northgate Health · 3 active · 13 inactive
16
Northgate Denials Analytics
Northgate Health · 5 active · 11 inactive
16
Northgate Secure File Transfer
Northgate Health · 2 active · 14 inactive
16
Northgate Payment Posting Hub
Northgate Health · 3 active · 12 inactive
15

Not measured here

Metrics that need a feed Conduit does not have. Shown as gaps rather than invented.

Productivity leakage
Not instrumented — no production feed

Hours lost while an employee waits on access cannot be derived from this ledger: Conduit knows when a rung was submitted, not whether the person was idle or redeployed.

Needs: A production time or utilisation feed joined on employee and date.

Client-side provisioning SLA
Not instrumented — no production feed

Dwell on a CLIENT_FACING rung is measured from our own submission, so it includes time the client had not yet received the request.

Needs: Per-client request receipt timestamps from the client's own ticketing system.

Cost per onboarded employee
Not instrumented — no production feed

There is no rate card or effort capture in Conduit; handling time per rung is elapsed time, not worked time.

Needs: Effort capture on panel submission, or a rate card per party.