How the Rate Hierarchy Works in Budgeting
Introduction
Easy8 uses a rate hierarchy to calculate real income and expenses based on logged time. This article explains how the system selects which rate to use and why understanding this order matters for accurate budgeting.
Target Audience
User + Administrator
Understanding Rate Hierarchy
Definition
The rate hierarchy is the order in which Easy8 looks for a valid rate to use when calculating the value of logged time. The system checks these sources in this order:
- User rate – a rate set specifically for the user
- Activity rate – a rate based on the task activity (e.g. development, testing)
- Role rate – a rate based on the user’s role in the project (e.g. developer, manager)
- Global default rate – used if none of the above are set
The first available rate in this list is used.
How It Works
- Rates are applied when a user logs time on a task.
- The system checks if a user-specific rate exists. If not, it checks for an activity rate.
- If there’s no activity rate, it checks the user’s role in the project.
- If no rate is found at any level, it uses the global default rate (if defined).
Rates are usually set:
- In the Administration >> Budgets >> Rates section (globally)
- In the Budgets tab of a specific project (project-level overrides)
Example
- A user logs 5 hours of work.
- No user rate is defined.
- The activity (e.g. Testing) has a rate of 50 €.
- The system uses 50 € × 5 = 250 € as real income/expense.
If an activity rate were missing but the user had a role rate of 45 €, then that would be used instead.
Corner Situations
Conclusion
Understanding the rate hierarchy ensures that logged time is priced correctly. It helps keep your real income and expense values accurate.



