Time on Projects
Preview a sample report
See what an exported report looks like, using sample data:
Appears in the web app as [L3] Time Report (in this article, Project Time Report)
Available on: Basic plans and above
Who can use it: All roles, including Admins, Managers and Members
Where to find it: Reporting › Project And Tasks › [L3] Time Report
Time on Projects shows how much time each person spends on each project, and what that time costs and is priced at. Use it to see whether effort is going into the work that matters most, and to trace it day by day, and down to the app or window.
What problem does this report solve?
A person usually spends a month across several projects, and each project has several people logging time on it. This report lists every person's time against every project, with the hours, price and cost for each pairing, so you can see how effort is spread across people and projects.
Use it to:
- See how each person's time and cost is divided across projects, and whether they are focused or spread thin
- Compare billable and non-billable time for each person on each project
- Trace effort and cost day by day, and down to the app or window, to spot shifts, spikes and weekend work
Understanding L1, L2 and L3
Flowace organises work in a three-level hierarchy that your organisation names. This report works at the L3 level. In this article we use this example:
Level | Example name | Example value |
|---|---|---|
L1 | Group | Digital Services |
L2 | Client | Northwind Retail |
L3 | Project | E-commerce Website Revamp |
Your workspace may use different names, such as Department › Customer › Matter. The report's column headings use your names, so an exported file may say "Matter" where this article says "Project".
Choose a report type
The report comes in three types. Pick one under Type on the export screen.
Type | What you get | Best for |
|---|---|---|
Cumulative Data | One row per person per project for the whole date range, with total Duration, Price and Cost. | Seeing how each person's time and cost is split across projects. |
Day-Wise Breakup | The same rows broken down by day: one row per person per project per day, with a Date column added. | Tracing effort day by day, and spotting shifts in focus and spikes. |
Day-Wise and Event-Wise Breakup | One row per event: each stretch of time in one app or window, or idle, with the date and time it began, the app, the window title and the web address. A Summary View table follows the rows. | Seeing which apps and windows a person's project time went into. |
How to generate the report

- Open the report. Go to Reporting › Project And Tasks › PROJECT Time Report. The last item of the path uses your L3 name.
- Choose your scope.
- Member and Teams – use the icons to choose people individually or by Team, then pick them from the list, or keep All Members Selected.
- Filter By – choose the level to filter on: your L1, L2 or L3 (shown as Department, Client or Project in the screenshot, which uses one workspace's names). Then use Search to pick the items to include.
- Date – pick the start and end dates.
- Attribute Filter – click Open Attribute Filter to filter by custom attributes or custom fields.
- Choose the Type: Cumulative Data, Day-Wise Breakup or Day-Wise and Event-Wise Breakup.
- Set the display options.
- Billable Type – Billable, Non Billable or Both. In the exported file these appear as BILLABLE and NON_BILLABLE, depending on whether the L3 is billable/non-billable.
- Time – Time in Decimal or Time in HH:MM:SS. The samples use Time in Decimal.
- Sync With Shift – tick it to include only the time that falls within each person's shift.
- Get the report. Keep Download Report in CSV ticked and click Generate Report to get the report as a CSV file.
The top of the exported file repeats the report type and sub type (Cumulative, Day wise breakup or Day Wise and Event Wise Breakup), the Start Date and End Date, and Generated At. It also lists the formulas used for Price and Cost.
How the numbers are calculated
PRICE
Duration (in hours) × Hourly Price
Each employee's hourly price is set on the employee form when the employee is created. If no hourly price is set, Price is 0.
COST
Duration (in hours) × Hourly Cost
Each employee's hourly cost is set by an Admin when the employee is created. If no hourly cost is set, Cost is 0.
TOTAL FOR A PERSON ON A PROJECT (DAY-WISE BREAKUP)
Σ of that person's daily rows for the project
Add a person's daily Duration, Price and Cost for one project and you get the figures in their Cumulative Data row, give or take rounding.
Cumulative Data
One row per person per project for the whole date range. Duration, Price and Cost are totals for the range. The sample covers 1–30 September 2026.
What each column means
Column | What it shows |
|---|---|
The person's email address. | |
Name | The person's name. |
Team | The Team or Teams the person belongs to, separated by semicolons. Shows NA when no Team is assigned. |
Prefix Name | Holds the names of any extra levels your workspace adds above L1. Blank when none are set. |
GROUP Name / CLIENT Name / PROJECT Name | Where the project sits in your hierarchy. The headings use your own L1 / L2 / L3 names, in capitals. |
Billable Type | BILLABLE or NON_BILLABLE. This belongs to the project: every row for a project shows the same Billable Type as projects are marked as billable or non-billable. |
Duration(Hrs in decimal) | BILLABLE or NON_BILLABLE. This belongs to the project: every row for a project shows the same Billable Type. |
Duration(Hrs in decimal) | Total time the person tracked on the project, in hours. For example, 10.50 is 10 hours 30 minutes. |
Price | Duration × the person's Hourly Price. 0 when no Hourly Price is set. |
Cost | Duration × the person's Hourly Cost. 0 when no Hourly Cost is set |
Worked example
Carlos Ramirez (Team: Development) works on E-commerce Website Revamp (Group: Digital Services, Client: Northwind Retail). His hourly cost is ₹2,000 and his hourly price is ₹3,500. He logs billable time on three days:
Date | Hours Logged | Price (₹3,500/h) | Cost (₹2,000/h) |
|---|---|---|---|
1 Sept | 4.00 | ₹14,000 | ₹8,000 |
2 Sept | 3.50 | ₹12,250 | ₹7,000 |
3 Sept | 2.50 | ₹8,750 | ₹5,000 |
Total | 10.00 | ₹35,000 | ₹20,000 |
Price = 10.00 × ₹3,500 = ₹35,000. Cost = 10.00 × ₹2,000 = ₹20,000.
In Cumulative Data, this appears as one row (Email, Team and Prefix Name not shown):
Name | GROUP Name | CLIENT Name | PROJECT Name | Billable Type | Duration | Price | Cost |
|---|---|---|---|---|---|---|---|
Carlos Ramirez | Digital Services | Northwind Retail | E-commerce Website Revamp | BILLABLE | 10.00 | 35000.00 | 20000.00 |
Day-Wise Breakup
One row per person per project per day, with that day's Duration, Price and Cost. It has the same columns as Cumulative Data, with a Date column added at the start. A day on which a person tracked no time on a project has no row. The sample covers 1–30 September 2026.
What each column means
Column | What it shows |
|---|---|
Date | The day the time was tracked, in YYYY-MM-DD format. |
Name | The same columns as in Cumulative Data (Email, Name, Team, Prefix Name, GROUP Name, CLIENT Name, PROJECT Name, Billable Type, Duration, Price and Cost), showing that day's figures only. |
Worked example
Carlos Ramirez's time on E-commerce Website Revamp from the example above appears as three rows, one for each day he tracked time (Email, Team and Prefix Name not shown):
Date | Name | CLIENT Name | PROJECT Name | Billable Type | Duration | Price | Cost |
|---|---|---|---|---|---|---|---|
2026-09-01 | Carlos Ramirez | Northwind Retail | E-commerce Website Revamp | BILLABLE | 4.00 | 14000.00 | 8000.00 |
2026-09-02 | Carlos Ramirez | Northwind Retail | E-commerce Website Revamp | BILLABLE | 3.50 | 12250.00 | 7000.00 |
2026-09-03 | Carlos Ramirez | Northwind Retail | E-commerce Website Revamp | BILLABLE | 2.50 | 8750.00 | 5000.00 |
Adding the three rows gives 10.00 hours, ₹35,000 price and ₹20,000 cost, the figures in his Cumulative Data row.
Day-Wise and Event-Wise Breakup
One row per event: each stretch of time a person spends in one app or window, or idle, with the date and time it began. It has the same people, hierarchy and billable columns as Day-Wise Breakup, and adds the app, window title and web address behind each row. Every row also shows the hourly rates used, and a Summary View table below the rows adds up the time, price and cost for each project. The sample covers 1–3 September 2026.
What each column means
Column | What it shows |
|---|---|
Date | The date and time the event started, in YYYY-MM-DD HH:MM:SS format. An event lasts until the next one starts. |
Email, Name, Team, Prefix Name | The same as in Cumulative Data. |
GROUP Name / CLIENT Name / PROJECT Name | Where the project sits in your hierarchy. Idle rows show ~ because idle time is not linked to a project. |
App Name | The app the person was using, such as EXCEL.exe or chrome.exe. Idle rows show where the idle time came from: FlowaceApplicationTimer, Idle Duration or LockApp.exe (the lock screen). |
App Title | The title of the window or document, for example Budget Tracker.xlsx - Excel. |
Url | The web address of the page when the event is in a browser. Shows ~ when there is none, and is blank on Idle Duration rows. |
Type | PLUGIN: active time on system. PLUGIN_IDLE: idle time. |
Duration(Hrs in decimal) | How long the event lasted, in hours, rounded to two decimal places. You can also decide other time format before extracting the report |
Hourly Price / Hourly Cost | The person's hourly price and hourly cost, set on the employee form. |
Total Price | Duration × Hourly Price. Always 0 on idle rows. |
Total Cost | Duration × Hourly Cost. Always 0 on idle rows. |
Time is priced and costed only when it is tracked against a project. Idle time is never priced or costed.
Summary View
Below the event rows, the file has a second table called Summary View. It has one row per project, with these columns: Prefix Name, GROUP Name, CLIENT Name, PROJECT Name, Duration(Hrs in decimal), Total Price and Total Cost. All idle time is added up in one row with ~ in the GROUP, CLIENT and PROJECT columns.
Use the Summary View for totals rather than adding up the event rows. Each event's Duration is rounded to two decimal places and many events last only seconds, so the rows add up to slightly less than the true total. The Summary View adds up the exact time.
Worked example
On Tuesday 1 September 2026 at 09:37:25, Carlos Ramirez (Team: Development) starts work on E-commerce Website Revamp. His hourly cost is ₹2,000 and his hourly price is ₹3,500. His first four events on the project are:
Date | App Name | App Title | Duration | Total Price | Total Cost |
|---|---|---|---|---|---|
2026-09-01 09:37:25 | Code.exe | main.py - Visual Studio Code | 0.17 | 583.33 | 333.33 |
2026-09-01 09:47:25 | chrome.exe | Documentation - Google Chrome | 0.01 | 11.67 | 6.67 |
2026-09-01 09:47:37 | explorer.exe | File Explorer | 0.02 | 8.75 | 5.00 |
2026-09-01 09:47:46 | ms-teams.exe | Daily Stand-up | Microsoft Teams | 0.33 | 1166.67 | 666.67 |
Each event lasts until the next one starts. The first event runs for 600 seconds from 09:37:25, so the second starts at 09:47:25.
Event 1 lasts 600 seconds, which is 600 ÷ 3,600 = 0.1667 hours. Duration shows 0.17. Total Price = 600 ÷ 3,600 × ₹3,500 = ₹583.33 and Total Cost = 600 ÷ 3,600 × ₹2,000 = ₹333.33.
Event 2 lasts 12 seconds (12 ÷ 3,600 hours), so Duration shows 0.00, yet Total Cost = 12 ÷ 3,600 × ₹2,000 = ₹6.67.
The four events last 1,821 seconds (0.5058 hours) in total. Their rows show Durations adding up to 0.50, while the exact time is 0.51 hours. Price and cost are worked out from the exact time, so they add up correctly: ₹1,770.42 and ₹1,011.67.
Carlos has 57 events on this project that day. Their rows show Durations adding up to 3.94 hours, while the exact time is the 4.00 hours in his Day-Wise Breakup row.
Reading the results: common scenarios
What you see | What it means | What to do |
|---|---|---|
Every row for a project says NON_BILLABLE (for example, Finance Process Upgrade: Priya Nair 4.69 hours and Oliver Bennett 6.36 hours) | Billable Type belongs to the project, not to the person or the day. This project is non-billable, so all time tracked on it is NON_BILLABLE, whoever logged it. | Nothing needed. Use the Billable Type filter to include or leave out such projects. |
Duration is above 0 but Price or Cost is 0 (for example, Thabo Nkosi's 14.10 hours show Price 0 and Cost 0; Oliver Bennett's hours show Price 0) | No Hourly Price (Price 0) or no Hourly Cost (Cost 0) is set for that person. | Ask an Admin to set the missing rate on the employee. |
A Day-Wise row with far more hours than the person's usual day, or with a date that falls on a Saturday or Sunday (for example, Hiroshi Tanaka: 10.30 hours on 2026-09-24 against an average of 5.6 hours on other days, and 3.20 hours on Saturday 2026-09-12) | The person tracked more time than usual that day, or worked at a weekend. | Check whether the extra time was planned or agreed with the person. |
Team shows NA, or two Teams separated by a semicolon (for example, Aisha Bello shows NA; Elena Petrova shows Consulting;Management) | NA means no Team is assigned to the person. A semicolon separates Teams when the person belongs to more than one. | Assign a Team if you want to filter the report by Team. |
An event row with Type PLUGIN_IDLE and ~ in the GROUP, CLIENT and PROJECT columns (for example, Carlos Ramirez, 2026-09-01 11:09:28, SessionLock, 0.97 hours) | Idle time, such as a locked screen or no activity. It is not linked to a project and is never priced or costed, so Total Price and Total Cost are 0. | Nothing needed. |
The Summary View total is higher than the event Durations added up (for example, E-commerce Website Revamp: Summary View 10.00 hours, event rows add up to 9.87) | Each event's Duration is rounded to two decimal places and short events round down to 0.00. The Summary View adds up the exact time. | Use the Summary View for totals |
FAQs
- Which report type should I choose?
Choose Team & Individual Summary for totals per person, Daily Breakdown to check individual days or compare with your HRIS, and Monthly Active Hours for a calendar view of one type of hours.
- Why can't I choose columns for Monthly Active Hours?
This type shows one type of hours per date. Choose it under Hours To Show instead.
- Why is Logged Hours always included?
Logged Hours is the base for the other measures, such as Idle Hours and Activity %, so Total Logged Hours (or Logged Hours in Daily Breakdown) can't be removed in Edit Columns.
- Should I use Total or Average columns?
Use Total columns to compare people over the same period, such as for payroll. Use Average columns to see a typical working day, especially when people worked a different number of days.
- Why does someone have 0 Expected Working Days?
With Exclude Time Off Days, leave days, holidays and weekly offs are left out. If every day in the period was time off, the row shows zeros.
- Where do the HRIS columns come from?
They come from your connected HRIS tool and show what it records. Flowace shows them alongside its own tracked times without changing them. HRIS columns are available in Team & Individual Summary and Daily Breakdown, on Standard plans and above.
- What decides whether time is productive, unproductive or neutral?
For active time, the rating of the app or website in use. For away time, the rating of the activity type the person selects in the pop-up when they return. Both are set in your workspace's productivity settings. Ask your Workspace Admin if an app or website looks wrongly rated.
- Why don't Productive, Unproductive and Neutral Hours add up to Logged Hours?
They split Active Hours and Away Hours. Idle time has no rating, so it stays in Idle Hours.
- How is Project Cost worked out?
Project Hours, converted to decimal hours, is multiplied by the person's hourly rate. If no rate is set, Project Cost shows 0.00.
Related Articles:
Need more help? Reach out to support@flowace.ai and our team will be happy to assist.
© Flowace Technologies Pvt Ltd | flowace.ai
Updated on: 30/10/2026
Thank you!