Freelancer Workload Forecast Template for Four Weeks

Download the blank four week workload forecast spreadsheet. No account is required. Save a copy before adding your project details.

Capacity planning determines how much work you can reasonably take on. A workload forecast places the existing commitments into specific future periods to identify overload before it happens. You can have enough hours in a month overall and still face an impossible second week.

Work must be scheduled in the sequence it can happen. Atlassian’s dependency guidance explains how prerequisites shape a project schedule; forecasts must account for client approvals that prevent later tasks.

The existing Noddis freelancer capacity guide covers the basic available-hours calculation. Use that as the input to this forecast rather than repeating it here.

Suppose a fictional freelance designer has 25 usable client-delivery hours per week, after accounting for non-billable obligations. The current commitments look like this:

The negative seven hours in week two are the warning. The freelancer should not accept another promise in that week without addressing the shortfall. The forecast does not claim that the fictional tasks can actually be moved; review dependencies and client commitments before rescheduling.

Start with accepted work, not speculative leads. For each deliverable, estimate the remaining production effort and the week when the work must occur. Include client review and revisions where your team must actively participate.

1. Set usable weekly capacity. Start from working hours and subtract recurring meetings, administration, leave, and a realistic interruption allowance.
2. List committed deliverables. Do not include optional or unapproved client requests in the committed baseline; track them as scenarios.
3. Distribute effort into weeks. Put work in the periods when it can actually happen, considering approvals and deadlines.
4. Add recurring obligations. Retainers, reporting, and routine QA consume capacity even when their tasks look small.
5. Calculate the gap. Available hours - committed hours = remaining capacity for each week.
6. Review the overloaded weeks. Decide whether to move work, reduce scope by agreement, obtain support, or defer new commitments.

Rank the work by contractual deadline, dependency, and realistic consequences. Ask which tasks can move without affecting a commitment and which require a client conversation. Do not secretly borrow hours from a later week if the dependent deliverable must be finished earlier.

For the example above, shifting seven hours from week two to week three would remove the shortfall only if the associated work permits it. If the Orbit Bikes campaign launches at the end of week two, moving its final QA into week three is not viable. You may need to renegotiate another deliverable or bring in qualified help.

A forecast is a decision tool. It should expose tradeoffs, not automatically dictate which client loses priority.

For work with significant uncertainty, record an expected estimate and a higher planning estimate. You can also hold a percentage of time as contingency. Choose the method based on your history; do not assume a particular buffer works for everyone.

For instance, a design revision expected to take four hours might have a planning range of four to six hours if the number of changes is unknown. The high case makes risk visible before that time is committed elsewhere. Record why the range exists so it can be improved after delivery.

Review it weekly, and update it sooner when a client changes a deadline, approves added work, or postpones feedback that affects later tasks. Compare estimates with actual time to calibrate future work.

Noddis is a project management app with Portfolio, Planner, and project-level tasks. Use those views to inspect upcoming commitments. Tasks and subtasks can store duration estimates, and Execute summarizes unfinished recorded estimates for the selected project against adjustable capacity hours. Maintain this four-week, cross-client forecast separately; the project summary does not calculate the table for you. The multiple-client project guide covers the cross-project review habit. Explore the live demo.

Build the next four weeks, not the whole year. Find the first negative-capacity week and resolve it before accepting more work.