Effort tracking without timesheets
Flowstate derives effort from the project tools and code activity your team already produces, normalized so every person's day sums to 100%. Leads review it in minutes, and the result is strong enough to carry a CapEx claim.
Timesheets are fiction, and finance builds on them anyway
Engineers backfill them from memory on the last day of the month. Leads approve them without reading. Then those numbers become the basis for capitalization, R&D claims and every cost-per-project figure the board sees.
The work already leaves a record. Tickets move, branches merge, reviews land. That record is better evidence than anyone's memory.
Read from the work, not asked of the worker
Status transitions in Jira, Azure DevOps and Linear say what moved and when. GitHub activity says who was in the code. Flowstate blends both into a per-person allocation where every day sums to 100%.
CapEx, OpEx, leave and unattributed time each get their own band, so the split finance needs falls out of the same data.
Review a team in minutes, not an afternoon
A spreadsheet-style grid built for the keyboard. Leads tab through people, type a few characters of a project name and move on. The CapEx, OpEx, leave and unattributed bands recompute live as they type.
Keyboard first
Arrow keys, tab, type, enter. Reviewing a squad of eight is a few minutes of typing, not a meeting.
Live recomputation
Every edit updates the bands instantly, so the lead watches the CapEx position change as they allocate.
Forgiving search
Project search tolerates typos. The point is speed, and speed dies on an exact-match dropdown.
Unattributed time is named, never hidden
Non-project time and unlinked project time are separate buckets, and neither is ever silently defaulted onto a project. Leads cannot submit while anything sits unattributed, so the gaps get resolved instead of buried.
Once approved, allocations lock for audit. That is what makes the same numbers safe to hand to your auditor and your tax advisor.
The leaderboard does the chasing
Standings show overdue against approved and CapEx against target per team. One overdue report drops a team off the leaderboard, which turns month-end chasing into a thing teams do to themselves.
How effort tracking works
Derived, not declared
Effort comes from status transitions in Jira, Azure DevOps and Linear, blended with GitHub code activity. Nobody fills in a form on Friday afternoon.
Every day sums to 100%
Allocations are normalized so each person's day always adds up. No double counting, no missing afternoons, no 130% weeks.
Locked once approved
Approved allocations lock for audit. The number your CapEx claim rests on in March is the number the lead approved in January.
Typo-tolerant search
Leads assign time to projects by typing. The search forgives misspellings, so "paymnets" still finds the payments refresh.
Retire the timesheet
Book a demo and see a month of effort reviewed, balanced to 100% and locked for audit in one sitting.