Team

Who is carrying what

AMI Demo · Owner
1 over capacity

Billable percentage: 79% against target ~75%.

Timesheet completion: 77% against goal 95%+.
Employee retention: 88% against floor 75%.

What this team shipped

Nothing is dated as completed in the 7 days ending Oct 22.

See what shipped

Team signals

Team utilization

50%

Team utilizationHow this is worked outNo week-over-week history is on file for this signal yet.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026No verdict

50%

–

Members below targetHow this is worked outNo week-over-week history is on file for this signal yet.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026On target

–

At-risk projectsHow this is worked outNo week-over-week history is on file for this signal yet.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Project tracker · as of Oct 22, 2026Needs attention

–

Roster · 10 peoplePlatform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Team roster · as of Oct 22, 2026Team roster · as of Oct 22, 2026

Carry and capacity read from Team roster, grouped by team. Open a person for what they own and anything at risk. The money side lives on the reporting board.

Weekly, up to the latest week on file.

How it's counted: billable hours as a share of the team's available hours, billable roles only, each person counted only for the weeks they were on staff.

Your sign-in is not linked to anyone on the roster, so no row here is marked as yours. An admin can link it under Settings, People.

By team

Account Management · 2 · 54% utilization (time data covers 4% of the window)Creative · 2 · 95% utilization (time data covers 3% of the window)Finance · 1 · 0% utilization (time coverage not measured)Leadership · 1 · 0% utilization (time coverage not measured)Strategy · 1 · 68% utilization (time data covers 4% of the window)Technology · 1 · 69% utilization (time data covers 6% of the window)No department on file · 2 · 67% utilization (time coverage not measured)

No department on file: Available hours are not on file for anyone on this team, so this is the share of logged hours billed to clients, not a share of capacity. Over capacity cannot be reached on that basis.

Over capacity

Carrying more than their available hours. These are the people to move work off first.

Quinn AlvarezDesignerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 197% (billed hours against available hours). Partial window: hired Apr 6, 2025 (79 weeks of 106 weeks in this window). Utilization is measured against that period, not the full window.How this is worked out1 at risk: Utilization 197%, over available hoursPlatform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026over

197%

Not judged

Their capacity could not be measured, so nothing here says their load is fine. Each card says what is missing.

Colin ReyesDesignerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 69% (share of logged hours billed to clients). Partial window: left Feb 28, 2025 (22 weeks of 106 weeks in this window). Utilization is measured against that period, not the full window.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

69%

Dana WhitfieldCOOHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outNo time entries in window

Not availableNo time entries in window

Ivan KovacWeb DeveloperHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 69% (billed hours against available hours). Partial window: hired Feb 3, 2026 (36 weeks of 106 weeks in this window). Utilization is measured against that period, not the full window.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

69%

Marcus LeeAccount DirectorHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 61% (billed hours against available hours)Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

61%

Maren VossAccount ManagerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 66% (share of logged hours billed to clients). Partial window: employed Jan 1, 2025 to Dec 31, 2025 (52 weeks of 106 weeks in this window). Utilization is measured against that period, not the full window.Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

66%

Priya NairProject ManagerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 46% (billed hours against available hours)Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

46%

Rachel OseiFinance ControllerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outNo time entries in window

Not availableNo time entries in window

Sam BauerBrand StrategistHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 68% (billed hours against available hours)Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

68%

Theo SandovalSenior DesignerHow it is calculatedHow this is worked outNo utilization reading for this person, so their carry is what is shown.How this is worked outUtilization 72% (billed hours against available hours)Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Oct 9, 2026no target set

72%

Capacity

Utilization

50%

time data covers 3% of the window

Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Time tracking · as of Sep 30, 2024 to Oct 9, 2026Time tracking · as of Sep 30, 2024 to Oct 9, 2026

Timesheet completion

99 of 3754 weekdays on staff

Unassigned work

open and assigned to nobody

Platform ledgerA number this platform computed from your connected, synced data. It is not read out of a single outside tool; the tool-badged chips cite those records directly.Computed from: Tasks · as of Sep 30, 2024 to Oct 9, 2026Tasks · as of Sep 30, 2024 to Oct 9, 2026

Timesheets arrived on 99 of 3754 weekdays on staff in this window, which is 3%. Graded over 8 people; 2 more could not be graded because their employment record did not read, and they are in neither half of that fraction. 2 people logged time without a staff record and are counted apart rather than raising this figure.Population: 10 of 28 person entities on the roster (every person on record in this workspace, staff and contacts alike) entered this result; coverage PARTIAL: 18 of 28 roster entities never entered the population (unclassified 18).

Utilization by team

Account Management57%time data covers 4% of the windowfirm 50%

Creative69%time data covers 3% of the windowfirm 50%

Strategy70%time data covers 4% of the windowfirm 50%

Technology79%time data covers 6% of the windowfirm 50%

Utilization by resource type

account_executive61%time data covers 4% of the windowfirm 50%

delivery71%time data covers 4% of the windowfirm 50%

Utilization by person

Priya Nair47%time data covers 4% of the windowfirm 50%

Marcus Lee63%time data covers 4% of the windowfirm 50%

Quinn Alvarez63%time data covers 3% of the windowfirm 50%

Unnamed person66%time coverage not measuredfirm 50%

Unnamed person69%time coverage not measuredfirm 50%

Sam Bauer70%time data covers 4% of the windowfirm 50%

Theo Sandoval74%time data covers 4% of the windowfirm 50%

Ivan Kovac79%time data covers 6% of the windowfirm 50%

The next three months

Nov 20261,251 hAvailable hours0 committed engagementsNo roster changes scheduled

Dec 20261,293 hAvailable hours0 committed engagementsNo roster changes scheduled

Jan 20271,293 hAvailable hours0 committed engagementsNo roster changes scheduled

Available hours and committed engagements are shown side by side and are never divided into each other. Nothing in this workspace staffs a person onto an engagement for a number of hours, so a forward utilization percentage would be manufactured rather than measured.No grain in this workspace carries a forward booking, allocation or plan, so committed hours 1 to 3 months out are not knowable. Reported as unavailable rather than as zero: zero committed hours would render an idle team.canonical_engagements.auto_renew (migration 316) records renewal posture, and it is not in the served column set for this grain, so a term ending inside the horizon cannot be told apart from one that renews. Every term end below is a SCHEDULED TERM END and never a loss. Adding auto_renew to SERVING_SELECT_COLUMNS.engagementBilling is the one change that would resolve it.

What each team is carrying

Account Management6open across 2 people, 5 past dueheaviest team 6 openhas past-due work

Technology5open across 1 person, 4 past dueheaviest team 6 openhas past-due work

Creative4open across 2 people, 1 past dueheaviest team 6 openhas past-due work

Strategy4open across 1 person, 2 past dueheaviest team 6 openhas past-due work

Finance1open across 1 person, 1 past dueheaviest team 6 openhas past-due work

Leadership0open across 1 personheaviest team 6 open

unrecorded0open across 20 peopleheaviest team 6 open

Population: 44 of 44 task entities on the roster (every task on record in this workspace, assigned or not) entered this result; coverage FULL: every roster entity was reached.