Tracking time without reading the report is like writing a journal you never re-read. The hours pile up, the entries get neat, and nothing changes about how the next week looks. The statistics view is where the data starts paying you back.
This post walks through the charts that matter, the questions each one answers, and a 15-minute Friday ritual that turns the report into actual decisions.
All on the free Basic plan.
Where the Statistics Live
Mobile
- Open Timesheet
- Tap the Statistics tab
- Pick a date range
- Switch between chart types
Web
- Sign in at my.timesheet.io (Pro plan, 30-day trial)
- Click Statistics in the navigation
- Use the filters in the top bar to narrow the view
- Hover or tap charts for details
The Charts and What They Answer
Daily Working Hours
A bar per day for the chosen range.
Read for:
- Consistent daily hours: routine is holding
- Spikes: deadline pressure, or a long meeting marathon
- Dips: interruptions, sick day, off day
- Weekday pattern: Monday-warmup, Friday-fade
Decide: if you're consistently overrunning a planned day, the planning is the problem, not the day.
Day-of-Week Averages
Average hours per weekday across the chosen range.
Typical reads:
- Tuesday-Thursday peak, Friday slows
- Monday catches up on email, doesn't produce much else
- Weekend hours: either deliberate or a warning sign
Decide: schedule the demanding work for the days that statistically already produce. Don't fight your own rhythm.
Project Distribution
Pie or donut, time per project for the range.
Read for:
- Planned vs. actual time split across clients
- A project taking more than its share
- A neglected project that needs attention or honest deprioritization
- Billable vs. non-billable ratio
Decide: if a low-priority project dominates, ask why. Scope creep, slow communication, or simply a misjudged estimate?
Tag-Based Analysis
Time grouped by tag, cutting across projects.
Common patterns:
- 40% meetings, 30% deep work, 20% admin, 10% communication
- Meeting-heavy weeks correlate with less shipping
- Admin tag growing month over month is the slow leak
Decide: if meetings exceed a third of your time without that being your job, the calendar needs a different default.
Cumulative Hours Trend
A line showing total hours stacking up across the range.
Read for:
- Steady slope: consistent week
- Flat sections: holiday, sickness, deliberate slow week
- Sharp climb: crunch period
- Compare slope month over month for capacity planning
Decide: a project whose cumulative slope is flatter than expected is a project that's drifting. Catch it now.
Earnings Over Time
A line of earnings (hours × rate × factor + extra/h) across the range.
Read for:
- Are earnings growing alongside hours, or are you doing more low-rate work?
- Monthly and quarterly rhythms
- The effect of a rate change, visible after a few invoicing cycles
Decide: earnings flat while hours rise means your effective rate is dropping. Time for a pricing conversation or a different mix of work.
Picking the Right Date Range
Daily
Useful for "where did today go?" Less useful for trends.
Weekly
The sweet spot for most reviews. Detail without noise. Compare week-over-week.
Monthly
Smooths over individual day variation. Best for capacity planning and pricing decisions.
Quarterly or Yearly
Strategic. Seasonal patterns appear. Multi-month trends are reliable enough to act on.
Custom
Specific project, client billing cycle, comparison between Q1 and Q2. Useful when answering a specific question.
Filtering
By Project
How much did a single project actually consume? When did the work happen? Hours against the quote?
By Tag
All meetings across all clients. All admin time. All "deep work" sessions, regardless of project.
By Billable Status
Billable vs. non-billable percentage. Watch the ratio over weeks. The number you want depends on the role; the trend matters more than the absolute.
By Team Member (Pro)
For teams on the Pro plan, individual statistics, team rollups, workload comparisons.
Exporting Charts
Charts can be exported for reports, client decks, or your own quarterly review.
- Open the chart
- Find the export or share option
- Pick PNG (or an image format)
- Save or share
Common use cases:
- Client reports showing how time was spent on their project
- Team presentations on productivity or capacity
- Personal quarterly reviews
- Internal dashboards
The Friday 15
Statistics are most valuable as a habit. A 15-minute Friday ritual that turns data into decisions:
1. Open Statistics, range: current week.
2. Total hours. How does it compare to your target? More? Less? Why?
3. Project distribution. Did priority projects get priority time, or did urgent-but-not-important work crowd them out?
4. Daily pattern. Which day produced the most? Which the least? What made the productive day different?
5. Tag breakdown. Meetings as a share of total. Deep work as a share. Admin growing or stable?
6. Plan next week. Block protected time for the work the report says is underrepresented. Cap meetings if they ran high.
That's it. Same 15 minutes every week, the report keeps the planning honest.
Patterns That Show Up
"I work more than I thought"
The most common discovery. The report justifies a rate increase, supports a work-life conversation, and helps you set boundaries that aren't just feelings.
"Meetings dominate my time"
If meetings consume more than a third of your time and that isn't your job, the calendar needs a stricter default. Meeting-free days, shorter blocks, clearer criteria for what gets a meeting at all.
"One client gets all my hours"
Possibly fine, often a warning. Concentration risk, scope creep, or simply the next client never quite started.
"My productive days are X"
A consistent weekly rhythm. Schedule demanding work there, low-energy work elsewhere. Stop fighting it.
"Admin is eating the week"
Tag-based view shows admin growing month over month. Automate, batch, or delegate. The leak compounds.
Goals That Use the Data
Utilization
"Move billable hours from 25 to 30 per week over the next two months."
- Track weekly
- Identify the non-billable time that's eating the gap
- Decide what to cut, batch, or delegate
Balance
"Keep meetings under 8 hours per week."
- Tag-based weekly view
- Calendar limits informed by the report
- Friday check
Efficiency
"Reduce similar projects by 10% in total time."
- Compare completed projects of the same type
- Identify the phases that ran long
- Target one improvement at a time
Summary
The model:
- Track hours is the input
- Read the report weekly is the work
- Decide next week's plan from the report is the payoff
Without the third step, the first two are just bookkeeping. With it, the system pays for itself in the second or third week.
Where to Go Next
- Organize work with projects and tags so reports can cut cleanly across clients
- Export to Excel or CSV for deeper analysis or hand-off to your accountant
- Generate PDF invoices that show clients where the budget went