Why Rollover Exists
CharleOS uses a two-layer planning system:| Planning Layer | Uses | Purpose |
|---|---|---|
| PM Budget Planning | Average estimates | Determines what fits in the client’s monthly hours |
| Team Scheduling | Max or score-adjusted estimates | Ensures realistic capacity for delivery |
Clients aren’t charged extra—they just use future allocation when work runs over in a given month.
How It Works
At the end of each billing period:- Positive rollover: Client used more than allocated → deduct from next month
- Zero or negative: Client used less than allocated → no rollover (agency absorbs unused time)
Example: Monthly Rollover
Scenario
Client: Acme Corp Monthly allocation: 100 hours Work planned: 10 tasks at average estimates (totalling 100 hours)What Happens
| Task | Average | Max | Actual | Billable |
|---|---|---|---|---|
| Task 1 | 8h | 12h | 10h | 10h |
| Task 2 | 6h | 8h | 5h | 6h |
| Task 3 | 12h | 16h | 14h | 14h |
| Task 4 | 10h | 14h | 12h | 12h |
| Task 5 | 8h | 12h | 9h | 9h |
| Task 6 | 12h | 16h | 15h | 15h |
| Task 7 | 10h | 14h | 11h | 11h |
| Task 8 | 14h | 20h | 18h | 18h |
| Task 9 | 10h | 14h | 8h | 10h |
| Task 10 | 10h | 14h | 13h | 13h |
| Total | 100h | 140h | 115h | 118h |
- Allocated: 100 hours
- Billable: 118 hours
- Rollover: 18 hours (deducted from next month)
Next Month
- Base allocation: 100 hours
- Rollover from last month: −18 hours
- Available hours: 82 hours
Why This Approach?
Fair to clients
Fair to clients
Clients pay for the hours used, just spread across months. They’re never surprised by a larger invoice—the work just comes off their future allocation.
Realistic scheduling
Realistic scheduling
Teams can schedule using max estimates (or score-adjusted) without worrying about artificial constraints. Work gets done properly rather than rushed to fit arbitrary monthly limits.
Encourages good estimation
Encourages good estimation
If rollover consistently eats into next month’s hours, it signals estimation issues. PMs learn to plan more conservatively or improve scoping.
Smooth workload
Smooth workload
Some months naturally have more work. Rollover lets the team focus on delivery quality rather than artificial monthly boundaries.
Two-Layer Planning in Practice
Layer 1: PM Budget Planning (Averages)
When deciding what work fits in a month, PMs use average estimates:- Client has 100 hours this month
- PM selects tasks totalling ~100 hours at average
- This is what the client “budgets for”
Layer 2: Team Scheduling (Max or Score-Adjusted)
When scheduling the actual work, use max estimates or score-adjusted estimates:- New clients (no history): Use max estimates
- Established clients: Use score-adjusted estimates based on their deliverability score
- New Client
- Established Client
No historical data available
- Use max estimates for scheduling
- Expect some rollover initially
- As tasks complete, scores build up
- Future months become more predictable
Rollover Scenarios
Scenario 1: Slight Overrun
Month 1:- Allocated: 80 hours
- Billable: 88 hours
- Rollover: 8 hours
- Available: 80 − 8 = 72 hours
- PM plans work for 72 hours
- Team delivers, uses exactly 72 hours
- No further rollover
Scenario 2: Consistent Overruns
Month 1: Rollover 10 hours Month 2: Rollover 12 hours (cumulative: 22 hours) Month 3: Rollover 8 hours (cumulative: 30 hours) Warning signs:- Estimates are consistently too low
- Scope creep is happening
- Client needs may have outgrown their plan
- Review estimation accuracy
- Discuss plan upgrade with client
- Tighten scope management
Scenario 3: Under-Delivery
Month 1:- Allocated: 100 hours
- Billable: 75 hours
- Rollover: 0 (not −25)
- Work was blocked waiting on client feedback
- Priorities shifted mid-month
- Estimates were too conservative
Under-delivery doesn’t give clients “banked hours” for next month. Each month resets to full allocation (minus any positive rollover).
Viewing Rollover
Client Detail Page
The client sidebar shows:- Current month allocation
- Rollover from previous month
- Effective available hours
Hours Summary
When viewing a client’s hours:- Allocated: Base plan hours
- Rollover: Carried from last month
- Available: Allocated − Rollover
- Used: Billable hours logged this month
- Remaining: Available − Used
Rollover Caps
To prevent excessive rollover accumulation, a cap may be configured:- Rollover limited to X hours maximum
- Excess beyond the cap is absorbed by the agency
- Protects against runaway rollover situations
Contact your admin to check if a rollover cap is configured for your clients.
Best Practices
Monitor monthly
Check rollover trends at month-end. Consistent positive rollover signals estimation or scope issues.
Plan conservatively
If a client has rollover, plan next month’s work 10-15% under to recover.
Use scoring data
Check client deliverability scores. A score of 1.2 means work takes 20% longer—factor this into planning.
Communicate early
If rollover is building up, discuss with the client before it becomes a problem.
Related
Billing Model
How the billing formula works
Client Intelligence
View client deliverability scores
Retainer Plans
How monthly allocations are set
T-Shirt Sizing
Understanding average and max estimates