Granskning, explained

In design, granskning is a defined process, not a glance

In everyday Swedish, granskning is any close examination: Riksrevisionen granskar the state's finances, a municipality granskar building-permit applications. In infrastructure design the word means one specific thing: the formal review of a design deliverable, a handling, before the client accepts it. A drawing, a calculation report or a technical description on a Trafikverket project is not finished when the engineer delivers it. It is finished when it has been through granskning and the comments are closed.

The review sits inside a fixed sequence of design stages. A project moves from systemhandling, where the disciplines show that the design works as one system, to bygghandling, the construction documents a contractor prices and builds from; the full chain is described in How infrastructure actually gets built. Every stage ends with a delivery, and every delivery is reviewed. The bygghandling review is the strictest of them, because it is the last check before errors become concrete.

Review is measured against requirements, not taste

Not against taste. A review comment carries weight because it points to a requirement, and the requirements come from known places. The first is the assignment itself: the client's task description and the project's PM documents say what the deliverable must contain. The second is the client's technical rulebook. Trafikverket publishes its requirements as governing documents in the TDOK series, with krav (requirements) and råd (advice) per technical area. Road and street geometry is governed by VGU, Vägars och gators utformning, binding for state roads. Technical descriptions follow the AMA Anläggning conventions, so every contractor reads them the same way. Structures are calculated to the Eurocodes with Swedish national choices. Even the documents themselves are regulated: TDOK 2012:35, Digital projekthantering, sets rules for how project documents are structured, named and delivered.

The third source is the project itself. Deliverables must agree with each other: the bridge drawing with the road's plan and profile, the drainage design with the geotechnical report, the bill of quantities with the drawings it measures. Much of what a granskning finds is exactly this, disagreement between documents rather than a broken rule. A good review comment states what is wrong, where, and which requirement or document it conflicts with. Comments that cannot point to a source tend to die in the response round.

A review round runs from egenkontroll to approval

Review begins before anything is delivered. The engineer who produced the deliverable checks it against a checklist and signs the result: the egenkontroll, a documented self-check required by the consultancy's quality system. After that, most firms let a colleague who did not do the work review it; the name varies between firms (intern granskning, sidogranskning), the principle does not. On assignments with many disciplines there is also a tvärfacklig granskning, where the disciplines check each other's interfaces: the road designer's ditch against the drainage engineer's pipe, the bridge abutment against the geotechnical assumptions.

Then the formal round starts. The consultant delivers the documents with status granskningshandling, on Trafikverket projects normally through the client's document management environment. The client's specialists review their technical areas and write granskningskommentarer, collected in one comment list. The designer answers every comment in writing, the bemötande: accepted and corrected, or not accepted, with a reason. When the revised documents are delivered and the comment list is closed, the client approves, and the deliverable gets the status that ends the process: bygghandling.

How many rounds this takes varies with the project. One main round with a follow-up on the revisions is common; a large tender package can need more.

The title block records who produced, checked and approved it

Look at the title block of any construction drawing and you see the chain in miniature. One field for who produced it, one for who checked it (granskad av), one for who approved it (godkänd av). Three names, deliberately not the same person. The signed egenkontroll and the comment list are archived with the project: years later, when a question comes up on site, the record shows what was checked, what was remarked, and how the remark was answered.

Documents also carry their status openly. A förhandskopia is a working copy. A granskningshandling is issued for review, and anyone who prices or builds from it does so at their own risk. A bygghandling is approved for construction. The exact stamps and forms differ between projects and clients; the logic behind them does not.

In a totalentreprenad, the chain shifts

The skeleton above describes an utförandeentreprenad, where the client commissions the design, reviews it and hands approved construction documents to a contractor. In a totalentreprenad the contractor is responsible for detailed design, runs the review of its own designers, and the client checks more selectively against the contract requirements instead of approving each document. Municipalities and regions follow the same sequence with their own requirement documents on top of, or instead of, Trafikverket's.

What does not vary is the reason the process exists. A design error caught in granskning costs a written answer and a revised drawing. The same error caught in production costs an ÄTA, a change order on a running construction site, with machines and crews waiting while it is resolved. Seen from outside, the comment lists and status stamps can look like bureaucracy. Seen from inside, they are the cheapest insurance infrastructure has.