Weekly site planning template

Planning the week by hand usually ends up as a different spreadsheet every time, with no easy way to see at a glance whether a crew has been assigned more tasks than it can cover on the same day.

This template fixes that: one row per task with front, crew, workers, predecessor and the days of the week marked, plus a summary that automatically adds up how many workers each crew has committed each day.

What it doesn't solve — we say so in the template itself — is chaining predecessors automatically (the check is visual, you do it) or real site lead times, like concrete curing: it's still your judgment call on whether the sequence is executable.

Bloqbase chains the real predecessor relationships between tasks and knows each crew's availability, flagging when a change throws off whatever depends on it, without you re-checking the whole sheet every week. Get in touch if you want to see it with your real schedule.

How to use it with judgment: start with one real, well-defined case, enter only data you can verify, and keep the reviewed version. The goal is not to fill in another document for its own sake, but to turn a project decision into a record that someone else can understand and review later.

Before making it part of your process, check three things: the inputs come from an identifiable source, the calculations or wording match the actual project, and it is clear who must approve the result. If one is missing, treat it as working material rather than final project documentation.

How to put it to work on a real project

The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.