Right now, Gorelo’s Labor Rates model is split into:
Billing Roles = the base hourly rate (ex: Remote Support = $X/hr, On-Site Support = $Y/hr, Travel = $Z/hr, etc.)
Work Types = the billing behavior (multiplier, minimum time, increment time, billable yes/no)
The issue is that Gorelo only lets a Work Type have one multiplier, so if we charge different rates based on when the work happens, we’re forced to create a separate Work Type card for every time condition.
That becomes unmanageable fast.
The problem (current workaround)
For any service that has a specific minimum and increment (ex: 2-hour minimum, 15-minute increments), we currently have to create multiple Work Types like:
Same service (Business Hours) → 1.0x
Same service (After-Hours Weekday) → 1.5x
Same service (Weekend) → 2.0x
Same service (Holiday) → 3.0x
All of these Work Types are identical except the multiplier. This explodes the Work Type list, creates confusion for techs/admins, and increases billing mistakes.
What I’m asking for (the improvement)
Add the ability for a single Work Type to have multiple multiplier rules based on day/time/holiday, while keeping one set of “core” billing behavior.
In other words: A Work Type should be able to say:
Minimum time = (example) 2 hours
Increment time = (example) 15 minutes
Billable = Yes
Multiplier Rules (time aware):
During business hours → 1.0x
Outside business hours on weekdays → 1.5x
Weekends → 2.0x
Holidays → 3.0x
This would eliminate the need to create duplicates of the same Work Type just to change the multiplier.
Key dependency: Holidays
Gorelo already understands Business Hours, but it does not currently understand Holidays, so this feature also needs a Holiday Calendar concept, such as:
A configurable holiday list (ideally by location/time zone)
Expected behavior (so it’s unambiguous)
When time is logged, Gorelo determines the multiplier automatically based on local time zone, business hours, weekday/weekend, and holiday calendar
If time crosses boundaries (ex: part business hours, part after-hours), either:
split automatically into segments with the correct multipliers or
apply a consistent rule (but it needs to be clearly defined)
Why this matters
This keeps Work Types clean and readable, reduces admin overhead, and prevents billing errors—because users aren’t forced to choose between multiple nearly-identical Work Types that only differ by “when.”
Log in to comment and vote
Comments1
Violet Watermelon
Right now, Gorelo’s Labor Rates model is split into:
Billing Roles = the base hourly rate (ex: Remote Support = $X/hr, On-Site Support = $Y/hr, Travel = $Z/hr, etc.)
Work Types = the billing behavior (multiplier, minimum time, increment time, billable yes/no)
The issue is that Gorelo only lets a Work Type have one multiplier, so if we charge different rates based on when the work happens, we’re forced to create a separate Work Type card for every time condition.
That becomes unmanageable fast.
The problem (current workaround)
For any service that has a specific minimum and increment (ex: 2-hour minimum, 15-minute increments), we currently have to create multiple Work Types like:
Same service (Business Hours) → 1.0x
Same service (After-Hours Weekday) → 1.5x
Same service (Weekend) → 2.0x
Same service (Holiday) → 3.0x
All of these Work Types are identical except the multiplier. This explodes the Work Type list, creates confusion for techs/admins, and increases billing mistakes.
What I’m asking for (the improvement)
Add the ability for a single Work Type to have multiple multiplier rules based on day/time/holiday, while keeping one set of “core” billing behavior.
In other words:
A Work Type should be able to say:
Minimum time = (example) 2 hours
Increment time = (example) 15 minutes
Billable = Yes
Multiplier Rules (time aware):
During business hours → 1.0x
Outside business hours on weekdays → 1.5x
Weekends → 2.0x
Holidays → 3.0x
This would eliminate the need to create duplicates of the same Work Type just to change the multiplier.
Key dependency: Holidays
Gorelo already understands Business Hours, but it does not currently understand Holidays, so this feature also needs a Holiday Calendar concept, such as:
A configurable holiday list (ideally by location/time zone)
Expected behavior (so it’s unambiguous)
When time is logged, Gorelo determines the multiplier automatically based on local time zone, business hours, weekday/weekend, and holiday calendar
If time crosses boundaries (ex: part business hours, part after-hours), either:
split automatically into segments with the correct multipliers or
apply a consistent rule (but it needs to be clearly defined)
Why this matters
This keeps Work Types clean and readable, reduces admin overhead, and prevents billing errors—because users aren’t forced to choose between multiple nearly-identical Work Types that only differ by “when.”