Temporary detour signage: Connecting RUB, M TU and the traffic control plan digitally

Temporary detour signage can be planned digitally when the detour route, traffic signs, construction phases, and regulatory order are maintained as connected project data. Germany’s RUB provide the framework for detour signing, while M TU addresses the special requirements of temporary installations. The traffic control plan translates those requirements into the actual road environment and work zone operation.

Why should detour planning begin with the traffic problem rather than the first sign?

A full road closure often looks straightforward when viewed from the project office. Define the closed section, select another route, place temporary signs, submit the plan, and install the traffic control.

The difficult part lies between those steps.

A detour route has to do more than connect two points on a map. It needs to accommodate the traffic expected to use it, reconnect drivers to the original corridor, and provide sufficient guidance at every relevant decision point. A geographically short route can still be unsuitable because of vehicle restrictions, roadway dimensions, local access rules, another work zone, transit operations, bridge limitations, pedestrian activity, bicycle traffic, or existing directional signing.

For a German traffic safety contractor, there is also a regulatory process behind the drawing. Section 45(6) of the German Road Traffic Regulations, StVO, requires contractors to obtain an order from the responsible authority before beginning work that affects road traffic. Construction contractors generally submit a traffic control plan, and the order addresses how the work zone is closed and marked, how traffic is restricted or directed, and how road closures and detours are signed.

A digital planning system should therefore avoid treating the map as the primary source of truth.

A better sequence starts by modeling the transportation problem: Which road movement becomes unavailable? Which road users have to be redirected? Where should they leave the original route? Which road segments form the intended detour? Where are the decision points? Which traffic sign functions are required at those points?

Only after those relationships exist does the traffic control drawing become an output.

This distinction matters because an image can show where signs are located, but structured project data can also explain why each sign exists, which route it belongs to, during which construction phase it applies, and what has to happen to it when the route changes.

What different roles do RUB, M TU, RSA 21 and the traffic control plan play?

The German rule set can look complicated to companies approaching work zone planning from a software perspective. RUB, M TU and RSA 21 are related, but they do not address the same planning question.

The Richtlinien für Umleitungsbeschilderungen, or RUB, published by Forschungsgesellschaft für Straßen- und Verkehrswesen e. V., FGSV (https://www.fgsv.de/), provide the basic system for detour signing. The currently published edition is the 2021 version. FGSV’s 2026 publication catalog continues to list FGSV 327 with 48 pages. Part A addresses detours outside motorways, Part B addresses motorway emergency or alternative detours, and Part C covers design and execution requirements.

The Merkblatt für den Einsatz von temporärer Umleitungsbeschilderung, M TU, also issued by FGSV (https://www.fgsv.de/), addresses practical requirements that arise when the signing is temporary rather than permanently installed. Its 2022 edition contains 52 pages. Topics include installation, sign dimensions, typography, photometric requirements, different road environments, motorway applications, and pedestrian and bicycle detours. Its catalog also covers numerous variants related to sign family 455 and sign 458.

The RSA 21 address traffic control and safety at work zones themselves. They distinguish urban streets, rural roads, and motorways, as well as longer-duration and shorter-duration work zones. FGSV Verlag (https://www.fgsv-verlag.de/) currently provides access to a total of 96 standard plans across the applicable road categories. Germany’s Bundesministerium für Verkehr, BMV (https://www.bmv.de/), introduced the RSA 21 for federal-road application through General Circular Road Construction 24/2021.

The traffic control plan, by contrast, is project-specific. It represents the actual road geometry, closure, temporary signs, traffic control devices, and other measures for the individual job and is used within the regulatory-order process under Section 45 StVO.

For digital planning, the important point is not to merge these documents into one rulebook. The value comes from representing their relationships in one project model.

How does a road closure become an end-to-end detour route?

The closed road segment is only the beginning of the problem.

A detour normally needs a diversion point where traffic leaves its original corridor and a return point where it rejoins that corridor. Between them lies a sequence of intersections, roundabouts, roadway segments, and other decision points. At some locations drivers must turn. At others they must continue straight even though another destination on the permanent directional signs may appear more attractive.

This is where route-based digital planning becomes much more useful than placing isolated traffic-sign icons.

The detour can be modeled as a connected sequence of road segments. Each relevant node can then carry a function: advance information, diversion, confirmation, continuation, directional decision, or return to the original corridor.

The signs become dependent objects associated with those nodes.

If a municipality later requires the route to use a different intersection, the system can identify which existing sign objects no longer belong to the revised route. It can also identify new intersections at which a directional decision is required.

A conventional drawing cannot perform that relationship check by itself. The planner has to recognize the consequences manually.

Germany’s StVO provides, among other options, signs 455.1 and 457.1 for temporary detour information, and the announcement may also use sign 458 as a diagrammatic route representation. M TU systematically addresses temporary variants involving sign family 455 and sign 458.

The result is an important architectural principle: the route should be treated as a primary data object, while individual traffic signs are linked operational objects.

Why does temporary detour signage need M TU in addition to RUB?

Permanent directional signing and a detour that exists for several days may perform a similar navigation function, but they operate under very different field conditions.

Temporary signs have to be delivered, installed, inspected, sometimes relocated, and eventually removed. They frequently share limited roadside space with permanent direction signs, regulatory signs, commercial signs, vegetation, parked vehicles, and other temporary traffic control.

The installation therefore becomes part of the planning problem.

FGSV (https://www.fgsv.de/) describes M TU as an addition to the RUB because temporary deployment creates implementation requirements that are not fully addressed by the stationary provisions. The document includes requirements involving sign design and installation as well as a standardized catalog for sign 458 and announcements under the RUB, together with dimensional representations for sign family 455.

For software design, that suggests that a temporary detour sign should not be stored merely as a graphic symbol.

A structured object can contain the sign family, selected variant, directional arrow, destination relationship, symbol or pictogram, intended dimensions, installation method, geographic position, facing direction, validity, route assignment, and project phase.

The visual representation on a PDF or map can then be generated from those properties.

That approach also makes templates reusable without pretending that every site is identical. Standard variants can accelerate the routine part of the work while the project-specific route and field conditions remain editable.

How can RUB, M TU and the traffic control plan share one digital model?

A practical model can be thought of as several connected layers.

The first layer describes the work zone itself. It contains the construction limits, affected roadway, sidewalks or bicycle facilities, planned duration, access points, and individual construction phases.

The next layer describes the traffic impact. A shoulder closure, lane closure, one-way alternating operation, and full road closure are fundamentally different events. A full closure may also have exceptions for residents, buses, emergency vehicles, construction access, bicycles, or pedestrians.

The third layer represents the detour route as an actual network path rather than a text note.

The fourth contains traffic sign objects. Every sign receives a geographic position, orientation, sign type, route relationship, and construction-phase relationship.

A fifth layer records the regulatory and revision status. A proposed route is not necessarily the route later approved by the authority. The project therefore needs to distinguish planning revisions from the configuration that was eventually ordered.

This relationship model changes the role of the traffic control plan.

The plan remains an important project document for review and implementation, but it is no longer the only place where the underlying information exists. The same project data can also generate a material list, installation list, field inspection route, change report, or mobile work package.

If a construction phase moves by several days, the associated detour signing can inherit the revised validity period. If the authority changes one leg of the route, the application can identify the signs associated with that leg.

A drawing-centric process usually cannot propagate those dependencies automatically.

What information belongs in a digital detour-signage record?

Location is important, but longitude and latitude alone do not describe a traffic sign sufficiently for field deployment.

Useful attributes can include the road, direction of travel, facing direction, intersection or route node, stationing or network reference where available, sign type, sign variant, installation configuration, construction phase, validity period, and link to an existing sign or inventory record.

The detour route itself should also carry operational properties.

A passenger-car route cannot automatically be treated as suitable for heavy trucks. Transit may require a separate route. A selected street might already carry a weight restriction or have a geometric condition that needs field verification. Bicycle and pedestrian operations can require a different treatment again.

Existing signs deserve their own layer.

This makes it possible to identify where temporary guidance interacts with permanent destination signing or regulatory restrictions. If an existing sign has to be covered, supplemented, or temporarily treated differently under the approved plan, the temporary action can reference the existing inventory object.

A planner then has more than an image of the final condition. The system retains the relationship between the proposed action, the physical asset, and the project reason for the action.

That is valuable later when the route is modified or when the site must be returned to its original condition after the work zone is removed.

Why should the PDF traffic control plan not become the project’s primary database?

Many work zone organizations still create the plan in CAD, GIS, or specialized traffic-sign software and distribute the final result as a PDF.

That is effective for viewing and approval, but it becomes inefficient when every department has to extract its own operational information from the document.

Dispatch reads the PDF to determine what has to be installed. The warehouse derives the sign quantity. A crew uses the PDF to find locations. The project manager tracks revisions separately. An inspector later needs to determine which installed object corresponds to which symbol on the plan.

When the authority requests a route change, the drawing changes, the material list changes, the crew information changes, and frequently several files have to be revised independently.

A data-first workflow reverses that relationship.

The traffic sign exists once as a structured object. The traffic control plan displays it. The material list counts it. The field application shows its installation location. The inspection workflow uses the same identifier. The removal task later refers to the same object again.

The PDF remains valuable because humans need a readable plan.

It simply stops being forced to perform the job of a database.

This becomes especially significant for detours because the signing can extend well beyond the immediate construction site and involve many individual locations distributed across a larger road network.

What mistakes commonly appear in temporary detour planning?

One of the most common problems is focusing on turns while ignoring continuation.

A planner naturally concentrates on the point where traffic leaves the closed road and on intersections where the route turns. Yet long detours can contain intersections where drivers are expected to continue straight despite competing local destinations. If the overall signing concept does not support that decision, drivers unfamiliar with the area may leave the intended detour.

Roundabouts can create similar issues because the correct continuation is not necessarily obvious from the permanent signing alone.

Another problem arises when temporary detour information competes with permanent destination guidance. Each individual temporary sign may be correctly designed, while the combined information seen by a driver still encourages two different decisions.

Construction phases add another layer of complexity.

During the first phase, one movement may remain possible. In the next phase it may be closed. A single static drawing containing signs for both phases makes installation errors much more likely unless every object has a precise phase assignment.

Changes outside the project can also undermine a previously suitable route. Another contractor may establish a work zone on the detour. A municipality can schedule an event. A bridge restriction may change. This is one reason route validation should be repeated when the project approaches implementation rather than assuming the original network condition remains unchanged.

M TU also includes pedestrian and bicycle detours, which matters because a motor-vehicle closure does not automatically imply the same restriction for every road user.

A digital system can make these dependencies visible as planning checks instead of leaving them scattered across notes and project memory.

How would a typical full-closure project be planned digitally?

Consider a rural state road that passes through a small town. A utility project requires a full closure through part of the built-up area for several days.

Traffic will leave the state road before entering the town, follow a county road through two neighboring communities, and return to the original route beyond the work zone.

The digital workflow begins with the closure geometry.

The system records where the closed section starts and ends and which movements remain available. The proposed detour is then stored as a connected route through the road network.

Each relevant intersection is evaluated.

Does traffic turn? Does it continue straight? Is there permanent directional signing pointing toward the closed route? Is a roundabout involved? Does heavy traffic need additional evaluation? Does the detour affect a bus line, school access, bicycle route, or another work zone?

Sign objects are created only after those route decisions have been made.

At the diversion point, advance and directional information may be required. Along the route, continuation signs support the intended path. A diagrammatic sign 458 may be suitable for more complex situations when incorporated into the project-specific order. Sign variants are selected using the applicable RUB and M TU framework.

The traffic control drawing and material list then come from the same objects.

Suppose the authority asks the contractor to move the route to another street at the second intersection. The route receives a new revision. The application identifies the signs affected by the revised segment and generates an updated plan and material requirement.

Once the plan is authorized, that revision becomes the operational baseline.

A crew can later open each location on a mobile device, verify the intended sign and orientation, record installation, and attach a field photograph. The inspection process can use the same locations after the detour goes live.

The result is a continuous project chain rather than a drawing that must be interpreted again by every downstream role.

Why is revision management more important than another drawing feature?

Detour plans frequently change during coordination.

A road authority may request a different diversion point. A municipality may identify a conflict with local traffic. A transit operator may need access through one section. An intended route may prove unsuitable for a particular vehicle category.

None of these changes are unusual.

The operational risk appears when several revisions continue circulating at the same time.

A digital planning system should therefore understand project states rather than merely storing file names. A revision may be a draft, submitted for review, returned with comments, revised, authorized, scheduled for installation, active, or withdrawn.

Signs and route segments should belong to a specific revision.

An earlier version remains available for audit history but should not accidentally appear as the current crew instruction. The authorized configuration should be distinguishable from an experimental planning alternative.

This is consistent with the regulatory process. Under Section 45(6) StVO, contractors are required to follow the authority’s orders for the work zone and associated traffic control.

In operational terms, controlled versioning often prevents more mistakes than an additional library of drawing symbols.

How can installation and inspection be generated directly from the plan?

Structured traffic-sign objects allow the design to flow directly into field operations.

Instead of giving the crew only a large drawing, the system can provide an ordered sequence of installation locations. Each location can contain the intended sign variant, orientation, construction phase, map position, and an extract from the authorized plan.

The crew records completion against the same object.

A photo can document the installed state. If the location is inaccessible or the planned installation cannot be implemented as expected, the issue can be returned to the project team with its exact location and sign identifier.

The inspection process can then reuse the same records.

The inspector does not need to create another independent list. The system already knows every sign that should currently be active, which route it belongs to, and which construction phase requires it.

The same principle helps with removal.

When the work zone ends, the application can generate the list of temporary signs to be collected and any permanent signs or devices that must be restored to their normal condition.

For long detours this can save substantial coordination effort because the installation may extend across many intersections, roads, and municipal boundaries even though the physical work zone itself is relatively short.

Can software determine whether a detour has enough signs?

Certain aspects are well suited to automated checking.

If a route changes direction at an intersection but no relevant sign object exists there, a rule engine can flag the node for review. The system can detect a sign assigned to a construction phase that has already expired, duplicate active plan revisions, or a route segment that intersects another closure contained in the available data.

Network data can provide additional checks when reliable sources are available.

Known one-way restrictions, vehicle restrictions, bridge limitations, or prohibited turns can be compared with the proposed route. This does not automatically prove that the route is suitable, but it helps the planner identify issues earlier.

Field conditions remain a separate matter.

Vegetation, sight distance, temporary parking, available installation space, existing sign clutter, driveway access, and construction access can require site inspection. Some information may also be outdated or missing from digital road data.

Software is therefore strongest when it acts as a structured checking and coordination environment rather than claiming to replace professional site assessment.

How can AI support temporary detour signage without taking over the regulatory decision?

AI can be useful in the parts of the workflow where information has to be extracted, compared, and checked.

A system could read a project description or regulatory document and propose structured fields for closure type, validity, traffic categories, or named roads. It could compare two plan revisions and summarize which route segments or signs changed.

It can also assist with consistency checks.

For example, a planning assistant could identify that a material list contains a sign that no longer appears in the current plan, that a sign is still assigned to a previous construction phase, or that a route node appears to require a directional decision without a corresponding sign object.

Geospatial and rule-based logic remain important alongside AI.

Whether a truck can actually use a bridge, whether a turn is permitted, or which sign must be authorized cannot safely depend on a language model interpreting a map image. These questions need authoritative source data, deterministic checks where possible, professional assessment, and the responsible authority’s order.

The legal responsibilities under Section 45 StVO are not transferred to an AI system simply because software assisted with the design.

A useful product therefore behaves more like a planning copilot than an autonomous traffic authority.

Why does this matter particularly for mid-sized German traffic safety contractors?

A PDF-centric workflow can remain workable for a long time in a small organization.

The limits become visible when many projects run in parallel and the same information has to be used by planning, dispatch, warehouse operations, field crews, project management, inspection, documentation, and billing.

Detour signing exposes this duplication particularly well.

The planner may specify dozens of temporary signs distributed across a route. Dispatch needs the required equipment. The warehouse needs the quantities and variants. The installation crew needs the locations and sequence. The project manager needs the authorized revision. Inspection staff need the active inventory. The same signs later have to be removed and returned.

If each department derives its own working list from the drawing, the organization repeatedly reconstructs information that already existed during planning.

A structured approach turns one planning object into several operational views.

The sign shown on the plan is also the warehouse item requirement, installation task, inspection location, and removal task. The detour route is simultaneously a planning geometry and the organizing structure for field locations.

This does not require every contractor to build a full CAD replacement.

In fact, a practical architecture can keep established traffic-control drawing software while maintaining route, project, status, material, and field-operation data in a separate operational platform. The important requirement is that the interfaces preserve object identities instead of repeatedly exporting anonymous graphics.

That architecture allows digital planning to deliver value even before advanced AI functions are introduced.

Why should new software treat RUB and M TU rules as versioned configuration?

Technical rules change over time, and current industry work already illustrates why hard-coding one edition into a product is risky.

FGSV’s (https://www.fgsv.de/) 2026 publication catalog still lists RUB 2021 and M TU 2022 as the published documents. At the same time, FGSV lists Working Group 3.5.3 under the heading “Überarbeitung der RUB,” indicating ongoing work on the subject. The Industrieverband Straßenausstattung e. V., IVSt (https://www.ivst.de/), also describes work intended to incorporate experience from the temporary-signing area into a revised framework.

Software should therefore store the rule-set version used for each project.

Sign templates, validation rules, dimensional parameters, plan references, and workflow requirements should be configurable rather than buried permanently in source code. When a new publication becomes applicable, the software can introduce another rule-set version while preserving the historic configuration of older projects.

That approach also helps companies with long-running contracts.

A new project created under a future edition may use updated rules, while archived projects and their documentation still need to show the basis that applied when they were designed and authorized.

In that sense, digital detour planning is not simply digitized drawing. It is rule-aware lifecycle management for a temporary traffic configuration.

Sources for the statistics used

FGSV – RUB: 48 pages, 2021 edition
https://www.fgsv-verlag.de/rub

FGSV – M TU: 52 pages, 2022 edition
https://www.fgsv-verlag.de/m-tu

FGSV – RSA 21: 96 published standard plans across urban streets, rural roads and motorways
https://www.fgsv-verlag.de/rsa-21-pdf

Further reading

German Federal Ministry of Transport – General Circular Road Construction 24/2021 introducing RSA 21
https://www.bmv.de/SharedDocs/DE/Anlage/StB/ars-aktuell/allgemeines-rundschreiben-strassenbau-2021-24.html

German Federal Ministry of Justice – Section 45 StVO covering traffic signs, work zones and detours
https://www.gesetze-im-internet.de/stvo_2013/__45.html

FGSV – Working Group 3.5.3 on the revision of RUB
https://www.fgsv.de/netzwerk/gremien/ag-3-verkehrsmanagement/35-verkehrszeichen-verkehrseinrichtungen/353-merkblatt-fuer-den-einsatz-von-temporaerer-umleitungsbeschilderung

What do the RUB regulate for a temporary detour?

RUB provide the basic system for detour signing, including detours outside motorways and designated motorway diversion routes. They do not replace project-specific engineering or the regulatory order for an individual work zone. Instead, they provide the framework for the structure, design, and deployment of detour signing from which the individual project arrangement can be developed.

Why is M TU needed in addition to RUB?

M TU addresses implementation issues that arise specifically when detour signs are installed temporarily and are not fully covered by RUB. Topics include sign design, installation, dimensions, photometric requirements, different road environments, and pedestrian and bicycle traffic. It also contains extensive standardized variants involving sign family 455 and diagrammatic sign 458.

What role does the traffic control plan play in a detour?

The traffic control plan translates the general rules into the actual project location. It represents the closure, traffic movements, temporary signs, and relevant positions. Under Section 45(6) StVO, construction contractors generally submit a traffic control plan when obtaining the required authority order for work affecting road traffic. The authorized revision subsequently becomes the operational basis for implementation.

Are RUB and RSA 21 the same set of rules?

No. RUB focus on detour signing, while RSA 21 address traffic control and safety for work zones on public roads. Both can become relevant to the same full-closure project. RSA 21 may govern the arrangement around the work area, while RUB and M TU address the temporary detour signing needed to guide traffic around that closure.

Can software calculate the correct detour automatically from a map?

Software can calculate candidate routes, but the shortest route is not automatically a suitable detour. Vehicle restrictions, roadway geometry, other closures, transit operations, local access conditions, bicycle facilities, and field constraints can change the result. A planning system can rank alternatives and flag known restrictions, while professional review remains necessary before the route becomes part of the submitted traffic-control concept.

Which data should be stored for every temporary detour sign?

Useful attributes include sign type, variant, geographic position, direction of travel, facing direction, route assignment, construction phase, and validity. Installation method, inventory relationship, material identifier, inspection state, and photographs can also be stored. Using one persistent object allows planning, warehouse preparation, installation, inspection, modification, and eventual removal to operate on the same underlying project information.

How are sign 455 and sign 458 used for temporary detours?

Sign family 455 supports announcement or continuation of a detour, while sign 458 provides a diagrammatic representation of the route situation. The appropriate configuration depends on the road layout and the authority’s project-specific order. M TU provides standardized temporary variants and dimensional information that can be incorporated into digital sign libraries and planning applications.

Should bicycle and pedestrian traffic also be included in detour planning?

Yes, whenever the work zone or the resulting traffic arrangement affects those road users. M TU specifically addresses temporary detour signing for pedestrian and bicycle traffic. A motor-vehicle closure should therefore not be treated as the entire transportation problem. Separate routes, additional signs, or changes to existing pedestrian and bicycle movements may be required depending on local conditions.

How should changes to an authority-reviewed detour be managed digitally?

The route, sign objects, and traffic control plan should be revision-controlled together. A change creates a new project revision while the previous version remains available for historical documentation. Installation and inspection workflows should reference only the applicable authorized revision. This prevents field crews, dispatchers, and project managers from unintentionally working with different versions of the same detour arrangement.

Can AI create a complete RUB and M TU traffic control plan automatically?

AI can assist with document extraction, comparison of route alternatives, consistency checks, and identification of missing or conflicting project information. It does not eliminate professional assessment or regulatory authorization. Route suitability, field visibility, installation feasibility, road restrictions, and project-specific conditions require dependable source data and responsible review. The authority responsibilities established by Section 45 StVO remain unchanged.