Forecasting

Reacting vs. Planning

Most agencies operate in reaction mode. A project lands, you scramble to find available people. Someone quits, you realize three projects are now understaffed. A client asks for a February start and you say "probably fine" because you haven't actually checked. Forecasting is the discipline of looking forward — using data you already have — so you stop getting blindsided by problems that were entirely predictable.

Three Types That Matter

Capacity forecast — Based on your resource pool and known time off, how many hours does your team actually have available over the next 8-12 weeks? If you've got 6 designers at 160h/month but two are on holiday in August, your real design capacity that month is 640h, not 960h. This is the foundation everything else builds on.

Demand forecast — What's coming in? Confirmed projects, likely deals in the pipeline, recurring client retainers. Map these against capacity and you'll see the gap: are you going to be short 120 developer hours in April, or sitting on 200 hours of bench time?

Financial forecast — The money version. Multiply planned allocations by hourly rates, subtract costs, and you get a profitability forecast. WrkSched's profitability dashboard does exactly this — projecting revenue, cost, and margin based on current scheduling data.

Building the Habit

Forecasting isn't a quarterly exercise. The teams that benefit most do a quick 15-minute review weekly: check utilization trends, scan for overallocation in the next two weeks, flag capacity gaps before they become emergencies. A timeline view makes this fast — you're looking at the picture, not assembling it from scratch each time.