Effort Booking
Effort Booking is a standalone, optional module. Use it to record effort (a duration with a description) and link it to any number of entities — for example a project and an OKR at the same time.
This page covers the actuals only: what was really worked. What is needed — capacity, activities, competences, time span — is described by the demand: Demand & Resource Planning. The two sides meet in the report cards on the shared reference object (project, OKR, value stream), where demand, plan and actuals sit side by side.
This is deliberately not a legal time-tracking system, but effort booking for reporting.
Quick capture
Section titled “Quick capture”Capture is built for minimal friction — only the duration is required:
- Type a duration. Accepted:
2h,1.5h,90m,1:30or plain minutes (45). Or click a preset (0.5h / 1h / 2h / 4h / 8h). - Optionally add a description.
- Link one or more entities — fastest via the suggestion chips (one click). Suggestions come from:
- your planned allocations for the current period (highest priority),
- recently booked entities,
- projects/roles assigned to you.
- Press Enter or Book — done. The date defaults to today but can be changed via the slim date field — by calendar or direct input (e.g. to log effort after the fact).
Live timer
Section titled “Live timer”Instead of typing a duration you can start a timer and stop it later. On stop, the measured duration is booked as effort. The timer is stored server-side and survives a page reload. At most one timer runs at a time.
Book straight from an entity
Section titled “Book straight from an entity”On the detail page of a project, OKR, etc. the header row — next to “Watch” — carries a “Book” action. It opens quick capture with the entity pre-filled, so you neither have to search for the entity nor leave the page.
The action only appears when effort booking is available for the tenant — and that means two conditions: the service must be running, and the tenant must have subscribed to it. If either is missing, the button is simply absent. When the service item is removed in the Platform Admin, it disappears within about a minute plus a page reload.
Dashboard modules
Section titled “Dashboard modules”Effort booking ships two dashboard tiles you can add via “Add module” in edit mode. They appear automatically once effort booking is running and subscribed for the tenant:
- Book Effort — quick capture as a tile: type a duration, pick an entity from the suggestions, book.
- Effort Report — your weekly total plus the entities you booked on the most.
Where planning went
Section titled “Where planning went”Up to version 1.x this page had a “Planning” and a “Forecast” tab, plus a “Plan Effort”
tile and the timetracker:plan permission. All of it is gone — not dropped, but replaced:
| Before | Today |
|---|---|
| “Planning” tab: entity + quarter + hours | Demand with time span, activity, competence and amount → Demand & Resource Planning |
| “Forecast” tab: plan against actuals per quarter | Report card “Demand / plan / actuals” on the project, OKR or value stream → Demand planning reports |
| “Plan Effort” tile | Resource-planning tiles → Resource planning |
timetracker:plan permission | demand:plan |
The reason: a single number per quarter said neither what it was needed for, nor who could deliver it, nor whether anyone has time at all. Those three questions are exactly what a demand answers. Two planning concepts side by side would be worse than one — hence the replacement rather than a second path.
The foot of the effort booking page links to resource planning, so the way there does not have
to be searched for. timetracker:report is unchanged: it still gates the actuals reports.
Existing role definitions carrying timetracker:plan are rewritten to demand:plan by a migration
script; until it has run, a role carries a permission that no longer exists — harmless, but visible
in role administration.
Multiple tenants
Section titled “Multiple tenants”If you belong to several tenants, effort is scoped strictly per active tenant. Switching the tenant at the top shows the effort of the newly selected tenant.
Reporting
Section titled “Reporting”Effort data is exposed through read-only report endpoints for analysis (e.g. totals per entity, per user, per period). These can also be consumed by other systems.
Related
Section titled “Related”- Demand & Resource Planning — demand, plan and coverage: the target side
- Demand planning reports — which card appears where, including “demand / plan / actuals”
- Resource planning — backlog, utilization, at risk
AI assistant
Section titled “AI assistant”The AI assistant can record and query effort by natural language — e.g. “log 2 hours on project X” or “how much effort is in OKR Y?”.