FS Garage Utilisation - Project Overview
FS Garage Utilisation is the weekly team capacity and delivery scorecard for Fleet Studio. It joins Garage planned allocations with Timesheet actual hours, computes leave-adjusted and billable metrics on the backend, and shows a CEO / C-suite scorecard in the Garage UI.
This page is the project-level Knowledge Transfer entry (FE + BE together). Repo setup details stay in the FE/BE folders; all metric formulas live in Metrics and Calculations.
What Utilisation does
- Ops / leads publish weekly allocations (planned hours per person x project).
- Leadership clicks Run Now.
- Backend pulls Timesheet actuals, classifies streams, applies derived metrics, and stores a snapshot.
- Frontend renders that snapshot (KPI row, stream mix, projects, employees, leave, key actions) without redoing business math.
| Field | Value |
|---|---|
| Category | Core / Utilisation |
| Frontend | base-fs-garage-fe |
| Backend | fs-garage-base |
| UI route | /utilization |
| PocketBase | typically http://127.0.0.1:8091 |
Metric calculation is owned by the backend (pb_hooks/utilisation_derived.js + run pipeline). The FE can enrich older snapshots for display only. See Metrics and Calculations.
Repositories
| Role | Repo | Responsibility |
|---|---|---|
| FE | base-fs-garage-fe | /utilization UI, allocations panel, display of BE snapshots |
| BE | fs-garage-base | PocketBase collections, allocation publish, Timesheet pull, snapshot + derived metrics |
Product surfaces (UI)
| Surface | What it shows |
|---|---|
| KPI row | Team capacity (allocated), utilisation / logged signals, deltas |
| Derived insights | Extra KPIs (billable util, conversion, plan accuracy, etc.) |
| Stream mix | Billable, FS Labs, HR/Ops, Overhead attainment + mix drift |
| Project variance | Per-project plan vs actual, delivery state, materiality |
| Employee utilisation | Leave-adjusted util %, on/below/above plan badges |
| Leave | Absence rate, planned vs unplanned, concentration |
| Key Actions | Rule-engine recommendations by hours at risk |
Data inputs
| Source | Data |
|---|---|
Garage allocations (published) | Planned hours per user-project-week |
| Timesheet API | Actual hours, leave, project classification |
| Bridge IDs | users.timesheet_user_id, projects.timesheet_project_id |
Project-wise segregation (summary)
Every hour is attributed to a person x project segment, then rolled into a stream:
- Canon Timesheet names onto Garage project names.
- Assign stream: billable, fslabs, hrops, or overhead (explicit project maps first, then name rules).
- Roll up to KPI cards, stream mix, employee bars, and project analysis.
Full maps, rules, and every KPI/employee/project formula: Metrics and Calculations.
Constants (product defaults)
| Constant | Value | Meaning |
|---|---|---|
| Standard week hours | 40 | Capacity per person |
| On-plan band | +/- 10% | Leave-adjusted util badge band |
| Materiality | 8 hours (one person-day) | Noise filter: only flag/act when a gap is at least one day of work. See What is materiality? |
| Derived snapshot version | 3 | Written after Run Now |
How to refresh numbers
- Publish allocations for the week.
- Run Now (ceo / c-suite) - writes
derived.version = 3. - Open
/utilizationand review Derived insights, streams, employees, actions.
Related docs in this site
- Metrics and Calculations - full formula catalog
- FE overview - frontend repo KT
- BE overview - backend repo KT