Engagement Command Center
All clients · All projects
Last refresh
Today, 5:12 AM
Today, 5:12 AM
Overall budget burn
—
—
Budget hours
—
Across selected engagements
Actual hours
—
BigTime, through yesterday
Remaining budget
—
Budget less actual
Tasks over budget
—
—
Budget health
Click any tier to open the matching tasks in Task ExplorerBurn gauge
Actual ÷ BudgetTask count by burn tier
—Budget to actual by phase
Phases with zero budget on the selected engagement are suppressed| Phase | Budget | Actual | Remaining | Burn | Burn % | Status |
|---|
Engagement roll-up
Drill path: engagement → phase → task → hours by employee| Client | Project | Budget | Actual | Remaining | Burn | Status | Tasks |
|---|
Insights
What this view is telling you
Auto-generatedOpen tasks
—
Uncompleted in Karbon
Past due
—
Past the Karbon due date
Stuck > 7 days
—
No status change in a week
Waiting for client
—
Blocked outside the firm
Escalated
—
Flagged for partner attention
Workflow health status
Task counts by Karbon status — drillable to phase and taskTasks by status
Shaded by agingEngagement issues
Karbon tagsDependency: days-in-status requires Karbon to expose status-change history through Snowflake. Current status alone cannot produce an aging metric.
Aging detail
Due-date and days-in-status bands per the specificationTasks needing attention
On track Watch Late Critical| Task | Client | Assignee | Status | Days in status | Due in / overdue | Tag |
|---|
Insights
What this view is telling you
Auto-generatedEfficiency index
—
Budget ÷ (actual + forecast)
Forecast remaining
—
Latest staff submissions
Projected total
—
Actual plus forecast
Projected variance
—
Against budget
Percent complete
—
Actual ÷ projected total
Projected outcome by engagement
Bar shows actual and forecast against the budget marker · click ✎ Edit to override a project's forecast
Actual hours
Forecast remaining
Budget
No sign-in yet — anyone can edit. Future release will scope edits to the signed-in user or a manager.
Forecast submission compliance
Thursday request, Friday 3:00 PM reminder, Friday end-of-day deadlineThis week
Week of Mon 13 JulStaff forecast detail
Latest submission per person| Staff | Role | Open tasks | Forecast hrs | Submitted | Status |
|---|
Insights
What this view is telling you
Auto-generatedCapacity assumptions
What-if parameters — every figure below recalculates live
Target deadline —
Only projects due on or before this date count
Weekday chargeable hours 9.0
Range 5 – 12, default 9
Weekend chargeable hours 4.0
Range to confirm with the firm
Working-day rules
—
Forecasted hours to deadline
—
—
Available capacity hours
—
—
Net bandwidth hours
—
—
Required daily chargeable
—
—
Project countdown & risk buckets
Risk is set by velocity gates against days until due · filter by assignee to focus one person
Assignee filter
Showing every engagement
| Client | Project | Due | Days out | % complete | Gate | Forecast hrs | Efficiency | Risk |
|---|
Staff capacity — review & edit
Pick an employee to edit their capacity, forecast, and risk · leave on “All staff” for the general review| Staff | Role | Forecast remaining | Available capacity | Net bandwidth | Required hrs / day | Load | Status |
|---|
Insights
What this view is telling you
Auto-generatedFilters
Filters stack — every control narrows the result set below—
Click any column heading to sort| Task ▲ | Client ▲ | Project ▲ | Phase ▲ | Assignee ▲ | Budget ▲ | Actual ▲ | Forecast ▲ | Proj. remaining ▲ | Burn % ▲ | Efficiency ▲ | Status ▲ | Due ▲ | Flags |
|---|
Insights
What the current filter set shows
Auto-generated
Why this page exists. Every threshold and formula below is taken from the functional specification.
Anything marked needs confirmation is an open decision that changes how the model is built — these
are the items to settle on the discovery call.
Core budget measures
Budget burn % — how much of the budget has been consumed by time already charged.
Budget Burn % = Actual Hours ÷ Budget Hours
Remaining budget — Phase 1 uses actual only; Phase 2 switches to a projected basis.
Remaining Budget = Budget − Actual
Projected Remaining = Budget − (Actual + Forecast)
Percent complete — driven by staff forecasts, not by calendar or task counts.
% Complete = Actual ÷ (Actual + Forecast Remaining)
BigTimePfx budget CSVForecast app
Efficiency index
Compares the budget against where the engagement is now projected to land. Above 1.00 is favourable.
Efficiency Index = Budget Hours ÷ (Actual + Forecast Remaining)
| Index | Reading | Band |
|---|---|---|
| 1.00 and above | Projected at or under budget | Green |
| 0.95 – 0.99 | Slightly over budget | Yellow |
| 0.85 – 0.94 | Moderately over budget | Orange |
| Below 0.85 | Significantly over budget | Red |
Needs confirmation. The specification flags digest exceptions where the index is
greater than 1 — but under this formula a value above 1 is the healthy case. The rule most likely
needs to be below 1, or a tighter band such as below 0.95.
Budget burn thresholds
| Burn % | Status | Applies to |
|---|---|---|
| 75% or less | Green | Gauge, tier counts, phase matrix, task rows |
| 76% – 85% | Yellow | Same |
| 86% – 100% | Orange | Same |
| Over 100% | Red | Same |
The remaining-budget column uses the same bands so a single colour language runs through the whole report.
Aging bands
Due date
| Condition | Status |
|---|---|
| More than 3 days until due | Green |
| Due within 3 days through 6 days overdue | Yellow |
| 7 – 14 days overdue | Orange |
| More than 14 days overdue | Red |
Days in current status
| Days | Status |
|---|---|
| 0 – 3 | Green |
| 4 – 7 | Yellow |
| 8 – 14 | Orange |
| More than 14 | Red |
Project risk velocity gates
A project is At Risk when percent complete falls below the gate for its remaining days.
| Days until due | On-track gate | Below gate |
|---|---|---|
| More than 60 | Not yet evaluated | |
| 31 – 60 | 40% complete | At risk |
| 16 – 30 | 75% complete | At risk |
| 0 – 15 | 90% complete | At risk |
| Past due | Must be complete | At risk |
Needs confirmation. When a project carries an extended
date, does that replace the original due date in the countdown and in these gates?
Capacity engine
Forecasted Hours = forecast remaining on projects
due on or before the target date
Available Capacity = working days × daily chargeable assumption
Net Bandwidth = Available Capacity − Forecasted Hours
Required Daily Hrs = Forecasted Hours ÷ working days
Working days respect the weekend and firm-holiday toggles. Both are excluded by default.
Needs confirmation. PTO, part-time schedules, and role-based differences in the
daily chargeable assumption are not yet in this calculation. Each one changes whether staff-level
bandwidth is believable.
Data lineage & matching keys
| Field | Source | Notes |
|---|---|---|
| Actual hours, staff, work code | BigTime | Via Standup Analytics semantic model |
| Status, assignee, due dates, tags | Karbon | Via Snowflake |
| Budget hours, budgeted assignee, phase | Pfx Engagement | VBA export → CSV → gateway |
| Remaining-hours forecast | Power App | Append-only, latest row wins |
The three keys everything depends on: client number, project name, task code. If these do not match across all three systems, no measure on any page can be trusted.
Needs confirmation. Is user + work code unique for forecasts, or can the
same work code appear on several projects? If it can, the forecast grain must include project.
Five engagement phases
Phase comes from the budget template, not from Karbon or BigTime.
| Phase | Covers |
|---|---|
| Pre-fieldwork / Planning | Scoping, risk assessment, planning memos |
| Interim | Controls testing and interim procedures |
| Year-end | Substantive fieldwork |
| Wrap-Up | Review, reporting, delivery |
| Shared | Tasks crossing phases — supervision, review |
Any phase with zero budget on the selected engagement is hidden by a DAX filter rule.
Needs confirmation. Do tax engagements use these same five phases and the same
risk thresholds as audit engagements?