Overview
Effective dates decide when a rate can be used. They are important whenever client pricing, contractor pay, employee cost, or rate cards change over time.
A rate with the wrong dates can make past work use a new rate, current work use an old rate, or future work appear missing. Treat effective dates as part of the rate setup, not an afterthought.
How effective dates work
- Start date is the first date the rate should apply.
- End date is the last date the rate should apply, when an end date is set.
- Open-ended rates continue applying until they are ended or replaced by a more specific applicable rate.
- Work date matters. Time entries, budgets, and forecasts usually resolve rates based on the date of the work being evaluated.
Common date patterns
| Scenario | Recommended setup | Why |
|---|---|---|
| A rate increases on January 1. | End the old rate on December 31 and start the new rate on January 1. | Past work keeps the old rate while new work uses the new rate. |
| A client has a temporary discount. | Create a specific override with both start and end dates. | The discount stops automatically after the agreed period. |
| A contractor changes pay rate mid-project. | End the old contractor pay or cost rate and start the new one on the change date. | Margin reflects the cost that was true at the time. |
| A future project has special pricing. | Create a future-dated project rate card or override. | The project can be prepared without changing current work. |
Change a rate without rewriting history
- Find the current rate that should stop applying.
- Set its end date to the day before the new rate begins.
- Create the new rate with the correct start date.
- Keep the same scope unless the business rule is changing. For example, replace a project override with another project override if the exception continues at a new amount.
- Review a past date and a current date to confirm each resolves to the expected rate.
Troubleshooting
| Problem | Likely cause | How to fix it |
|---|---|---|
| Old time changed to the new rate. | The new rate may start too early, or the old rate may have been edited instead of ended. | Restore the old rate's historical period and create a separate new rate starting on the change date. |
| Current work still uses the old rate. | The old rate may not have an end date, or the new rate may start in the future. | End the old rate and confirm the new rate starts on or before the current work date. |
| A rate is missing for future work. | No active rate covers the future work date. | Create a future-dated rate or extend the current rate if it should continue. |
| Two rates seem to apply at once. | There may be overlapping effective dates at the same scope. | Adjust the dates so only one active rate covers each date for that scope, or keep the more specific override intentionally. |
Example
Acme Co's UX Designer rate changes from $150/hr to $165/hr on January 1. End the $150/hr rate on December 31 and create the $165/hr rate starting January 1. December time keeps the old rate, January time uses the new rate, and reporting can explain the change cleanly.