Project constraint sheet template — Civil Engineering

A civil engineering project carries constraints of very different kinds that the team needs on hand and up to date at all times: zoning, geotechnical, hydrological and hydraulic, and environmental constraints, plus the applicable reference regulation. Having them scattered across the geotechnical study, the flood risk report and the environmental file is the fastest way for one of them to go unreviewed.

The sheet brings it all together in a single Excel file: project identification and the responsible authority; zoning constraints such as land classification, current planning and easements; geotechnical constraints such as soil type, estimated water table or presence of fill material; hydrological and hydraulic constraints such as the riverbank buffer zone, the design return period or the competent river basin authority; environmental constraints such as the required assessment or affected protected areas; and the applicable reference regulation, from structural codes to accessibility.

It also includes a block for up to four pending data points, each with its source and owner: the geotechnical study that hasn't arrived yet, the river basin authority's response still in process. It's the part of the sheet that changes most week to week, and the one that shows what's left to close before moving forward with confidence.

An Excel sheet says what data is missing on the day it's filled in, but it doesn't alert you on its own when the pending answer finally arrives. In Bloqbase, constraints and project documentation live in the same place as the report and progress reports, so when the pending data finally comes in, it gets updated where the rest of the team is already looking, not just in the Excel copy of whoever requested it.

Download the template free with your email, or get in touch if you want those constraints already living inside the project in Bloqbase, alongside the report and progress reports.

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.