The Expected hours factor is a field on a user's profile that determines whether Legalsense applies a factor to that user's expected billable hours. Use it to scale down the hours a user is expected to be billable, for example during a period of illness or leave.
The expected hours factor input field on the edit user form.
Where it's applied
- User profile: You set the expected hours factor on the user, alongside their other core details such as employee number and function. For the full procedure, see the article ↪ User management.
- Expected billable hours: The factor scales down the number of hours Legalsense expects the user to be billable over a period, based on that user's presence roster (roster hours minus any registered absence), multiplied by the factor. For example, a user on a full-time roster with a factor of 0.5 during a period of partial leave is expected to be billable for half their normal roster-based hours over that period.
In reporting
The expected hours factor feeds into two places:
- Performance Report: the report shows the user's Expected hours factor as its own column, alongside an Expected hours column that shows the resulting adjusted figure: the user's presence-roster hours for the period, minus any absence, multiplied by the factor. Use this to see, at a glance, whether someone's reduced expectation (illness, leave, part-time arrangement) is being reflected correctly, and to compare actual billed hours against that adjusted expectation rather than their full roster figure.
- Missing-hours notifications: the weekly email that warns a user when they haven't logged enough billable time uses the same calculation: presence-roster hours minus absence, times the expected hours factor. A reduced factor therefore also reduces how many hours that user needs to log before triggering a warning.
You can also filter and export the user list by Expected hours factor (a minimum/maximum range filter is available wherever users are listed), which is a quick way to find everyone currently running below full expectation. This is useful as a periodic check that temporary reductions have actually been reset.
Good to know
Use the expected hours factor for temporary situations, such as illness or leave, where a user is expected to be billable for fewer hours than usual during a given period.
The expected hours factor has no begin or end date of its own. Unlike a Target or a rate, it doesn't automatically apply only for a set period and then revert. It's a single, always-current value that stays in effect until someone changes it back. If you set it for a temporary situation, make sure to reset it to 1.000 yourself once that situation ends; nothing in Legalsense does this for you.
The expected hours factor is separate from ↪ presence rosters and from ↪ Targets, but in a narrower sense than a full separation:
- It doesn't touch a user's presence roster itself, or the Target record you configure under Targets. Those keep working exactly as configured, independent of the factor.
- It's only consumed by the Performance Report's Expected hours calculation and the missing-hours notification email, both of which take the user's presence-roster hours as their starting point and then scale that figure down by the factor. It does not affect the dashboards, the Hours report, work in progress (WIP) reports, or budget calculations.
Comments
0 comments
Please sign in to leave a comment.