A stormwater study is engineering from the first page to the signature. But most of the week behind it goes to the same disciplined execution of standard methods: reading in the catchment, running the runoff and detention calculations, running them again when the plan moves. Where the hours actually go, and why the work costs what it does.
The work
A stormwater study answers a drainage question with standard methods, and doing it well is engineering at every step. The engineer reads in the site and the plan, delineates the catchment and classifies its surfaces, and assigns each one a runoff coefficient from Svenskt Vatten's guidance. Design rainfall comes next: an intensity for the chosen return period, raised by a climate factor for the decades the system has to last. Then the calculations: pre- and post-development flows by the rational method, a detention volume sized to hold the difference and throttle the outflow to what the recipient can take, the pipes and the magazine dimensioned to Svenskt Vatten P110, and the pollutant load checked in StormTac against the recipient's environmental quality standards. A drawing set, and the whole thing written up as a PM the municipality can base a decision on.
None of that is filler, and none of it is beneath the profession. But look at where the hours sit. Choosing the return period, judging how sensitive the recipient really is, deciding the drainage strategy: that is the irreducible engineering judgment, and it is a small share of the clock. The rest of the week is the disciplined execution of those methods: locating the right inputs across a dozen sources, running the standard tools, and writing the result into the form the reviewer and the authority expect. Skilled work, all of it, and most of it follows a method.
The cost
The reason the week runs long is rarely the first pass; it is the revisions. A development in planning is a moving target: a building footprint grows, a green surface shrinks, a parking deck is added. Each change is small on its own, and each one re-runs the chain, because in a stormwater study nothing stands alone: more hardened surface means a higher runoff coefficient, which means larger design flows, a bigger detention volume, re-dimensioned pipes, new drawings, new quantities, a revised recipient assessment, and another review. The methods are the same; it is running them again, by hand, that takes the days.
How that lands depends on the contract, because not every study is sold the same way. On a fixed fee, the extra rounds are not billed onward; they are absorbed, by the firm and by the engineers' evenings. On a running account, the client pays for each loop, which spares the margin but slows the project and turns every revision into a cost the client can see. Either way, the expensive part of a stormwater study is not producing it once. It is producing it again, and again, at human speed.
What it reveals
That is the shape worth noticing. The week is mostly the disciplined execution of standard methods, real engineering done to a standard, but rule-governed and repeatable, wrapped around the judgment that decides what the study should conclude. The two are different kinds of work, and they scale differently: the judgment is irreducible, and a person makes it and signs it; the execution follows a method, and work that follows a method need not be carried by re-running it by hand each time.
Which is the real question under the hours. Not whether the engineering is hard, because it is skilled work from end to end, but which parts a method already governs, and what a week would look like if running and re-running them stopped costing days. We follow that thread in a century of writing the methods down.
Sources
Yesper is the AI civil engineer for construction and infrastructure. AFRY, COWI, NRC Group and other Nordic firms use it to halve the time on a study, rerun calculations in minutes, and catch errors that would otherwise slip through. Get in touch if you'd like to see what it can do for you.
Book demo
