Reports
Estimated vs actual hours
What each engagement line was estimated at against what has actually been logged.
The question it answers: are we estimating well? The report puts each engagement line's estimated hours beside the hours logged against it.
Before you start
- You need permission to see engagements.
- This report is part of plans with advanced reports. Without it, the page shows an upgrade prompt.
- Only lines with an estimate appear. Estimates are set per line on the engagement.
Steps at a glance
Read the report
Step 01
Open the report
Select Reports, then Estimated vs actual hours under Money and time.
1: Estimated vs actual hours on the Reports page. Step 02
Filter to what matters
The figures at the top count Lines estimated, how many have Started, and how many are Over estimate. Use All, Over estimate or Not started to filter, or search by engagement.
1: the Over estimate filter. In the demo business, 40 of 92 estimated lines are over. Step 03
Read the variance
Each row shows the engagement line, its Estimated hours, the hours Logged, and the Variance, marked over in red. The list opens on the largest overrun. Select Export to download it.
This compares hours, not money. A line can be under on hours and still unprofitable if senior people did the work.
How to read it
A consistent overrun on one service is a pricing problem, not a performance problem. A one-off overrun on one client is usually a scope problem: something was done that was not agreed.
Common questions
A line I expected is missing. It has no estimate, so there is nothing to compare. Add one on the engagement line.
What does computed under an estimate mean? The estimate is the one Orin OS worked out when the engagement was priced. When somebody agreed a different figure, that figure is used instead.