When Will the Backlog Clear? Forecasting Delivery for Agency Clients

"When will it be done?" Every client asks it. Most agencies answer with a number that sounds confident and is, in truth, a guess — "end of next week, probably" — and then spend the following fortnight quietly hoping the guess holds.

It usually doesn't. Not because the team is slow, but because the answer was never grounded in anything. The good news: you're already tracking everything you need to give a real answer instead.

Why Gut-Feel Forecasts Fail

The "end of next week, probably" estimate fails for predictable reasons:

It ignores everything else in the queue. You picture this client's work in isolation, forgetting the other twelve clients competing for the same week.
It assumes a perfect run. No interruptions, no new bugs, no scope creep. That fortnight never happens.
It's a single date. Real delivery has a spread. Promising one exact day means you're wrong the moment anything shifts — and you always look late, never early.

A guess feels faster than a forecast. It just costs more later, in chased deadlines and eroded trust.

What a Real Forecast Needs

Forecasting delivery isn't fortune-telling. It's arithmetic on two numbers you can actually measure:

The backlog. Everything still open for that client, sized. Not "a handful of bugs" — an actual total.
The pace. How much work your team genuinely clears for that client in a typical sprint, learned from what you've finished before, not what you hoped to finish.

Divide one by the other and you have a forecast. Backlog of 40 points, pace of 20 a sprint, you're looking at roughly two sprints. The maths is simple — the discipline is in sizing the work and measuring the real pace instead of the optimistic one.

Ranges Beat False Precision

Here's the part that separates a forecast you can defend from one that burns you: give a range, not a date.

"It'll be done on the 14th" is a hostage to fortune. "Likely the 14th, and by the 22nd even if scope grows" is honest, useful, and far harder to be wrong about. Clients don't actually need a single date — they need to plan around a realistic window. A range gives them that and protects you from being branded late over a two-day slip.

Real projects rarely land on the dot. A forecast that admits this is more trustworthy than one that pretends otherwise.

How Lantern Helps

Lantern turns the bugs and estimates you're already tracking into a delivery forecast — no spreadsheet, no manual maths.

Pace, measured for you. As each client's sprints complete, Lantern records what the team actually finished and keeps a rolling average. That's your real pace, not a hopeful one.

A clearance forecast with a range. For every client, you get how many sprints until the backlog clears and an estimated clear date shown as a window — an expected date and a later "if scope grows" date — so you can set expectations you'll actually meet.

Unsized work doesn't break it. Bugs you haven't estimated yet are filled with a sensible placeholder from similar past work and flagged, so the forecast stays usable while you sharpen it.

A health read at a glance. Each client carries a simple on-track / at-risk signal, so you can scan fifteen retainers in seconds and see which one needs attention today.

It's all in the estimation and forecasting guide.

Start your free trial →