Starting point
The consultancy records its working time in Jira with Tempo, project by project and ticket by ticket. The data was there; the answers were not. How busy is each person, measured against what is planned for their level of seniority? How high is the billable share per person and per project? On which working day is a booking missing, which day is overbooked, and which week went mostly on internal work?
Then there was the question that matters before every invoice: in which worklog does the billable time differ so far from the logged time that someone should take a look? All of this could only be answered with exports and spreadsheets, and holidays, sick leave and public holidays lived in another system.
Solution
The first stage was a lean service without a user interface of its own, placed where the team already works. Every 30 minutes it read the month's Tempo worklogs and the Jira users and their groups, calculated per person the logged and billable hours, the billable hours above the target derived from working days, and each person's share of the company's billable hours. It wrote the figures back as KPI tickets into a dedicated Jira project, per month and per day. Holidays and public holidays lowered the target.
When the questions outgrew what Jira fields can show, a web application of its own followed, with its own data store. Every night it takes over all Tempo worklogs with logged and billable time, ticket and text, along with the Jira projects and people. It shows working hours per project and per person with the billable share, expandable from the project through the ticket down to the single worklog. A switch per Jira project decides what counts as internal; individual internal tickets can be named as well.
For booking quality, the application checks every past working day per person against configurable rules: less than the daily minimum, more than the daily maximum, which applies at weekends too, and more than a set share of the week on internal projects. Holidays, sick leave and public holidays come from the HR system's absence calendar and lower the minimum; half a day of leave lowers it by half. People who work part-time on a few days, such as working students, are checked per week instead of per day, and there an absent day takes off one working day's hours, not a fifth of the week. A click on a day shows its worklogs.
For billing, it reports single worklogs whose billable time differs from the logged time by more than a configurable threshold, in both directions and grouped by person, with ticket and text. Very short worklogs are left out by a minimum duration. A different threshold can be tried out in the view without changing the saved default.
The utilisation view shows billable hours per person against the annual target for their level of seniority, pro-rated in the current year to the working days that have passed. On Mondays a summary of the previous week goes to the administrators, even when nothing stands out, and every person receives their own hours for the week as a PDF, with the same checks. Every delivery is logged with its PDF and deleted after six months. Every view can be downloaded as a PDF on the consultancy's letterhead and as an Excel file.
- First stage: figures per person written back into Jira as tickets every 30 minutes, including the share of the company's billable hours
- Logged and billable per project and person, expandable to the single Tempo worklog with its text
- Daily checks against daily minimum, daily maximum and internal share; part-time staff are checked per week
- Absences from the HR system lower the target, half a day by half
- Billing deviations per worklog in both directions, with a configurable threshold and minimum duration
- Billable hours against the annual target for the level of seniority, pro-rated to the reference date
- A Monday summary for the administrators and a weekly report for every person; every view as PDF and Excel
A look inside the product
Illustrative sample data; an anonymised product example that deliberately does not show the real product.
Result
The first stage ran in production against the consultancy's Jira and Tempo from November 2025 to March 2026; four days passed between the first commit and the first run. The web application is being rolled out. Its first version was built in May 2026; daily checks, absences, billing deviations, reports and exports followed between August and October 2026 in short steps, each driven by concrete feedback from daily practice.
It is designed so that a missing booking or a wrongly set billable time shows up on the next working day rather than at month-end, so that the monthly report is a download, and so that every person sees their own hours on Monday without having to ask.
Two decisions carried this: starting with the smallest step inside Jira and building an application of its own only when the questions called for it, and making the rules configurable instead of hard-wiring them, so that part-time work, absence and internal work count the way the consultancy actually works.
- First stage in production from November 2025 to March 2026
- Four days from first commit to the first run against Jira and Tempo
- Web application being rolled out
- Checks, absences, reports and exports added from August to October 2026 in short steps