An RSA 21 traffic sign plan shows how a work zone in public traffic space is signed, closed off, and guided. The key is not only selecting a suitable standard plan, but adapting it to the exact location, construction phase, remaining lane widths, sidewalks, bike traffic, and responsibilities. Companies that structure recurring cases properly can reduce authority questions and make application work noticeably faster.
Why does an RSA 21 traffic sign plan matter for roadwork in Germany?
Whenever roadwork affects public traffic, an internal sketch is usually not enough. The traffic authority order defines which signs, barriers, detours, signals, construction phases, and restrictions apply. The traffic sign plan turns the planned work into something the authority can review, approve, and enforce.
RSA 21 is the central German technical framework for temporary traffic management at roadwork sites. It replaced the older RSA-95 and separates work zones by urban roads, rural roads, and highways, as well as by shorter and longer work durations. The FGSV describes RSA 21 as guidelines for traffic-law safety measures at work zones on and alongside roads; the document has 176 pages. (fgsv-verlag.de)
For mid-sized companies in traffic safety, civil engineering, utility work, fiber deployment, access protection, scaffolding, electrical work, HVAC, or maintenance services, this has a practical consequence. A good application is not the longest one. It is the one where the authority can quickly understand the location, the intended work, the standard plan used, and the local deviations that were considered.
How do I create a traffic sign plan according to RSA 21?
A good RSA 21 traffic sign plan does not start inside drawing software. It starts with the worksite itself. The first question is whether the work takes place on an urban road, a rural road, or a highway. The next questions concern construction time, phases, worksite length, affected lanes, remaining widths, sidewalks, bike lanes, entrances, bus stops, existing signs, and visibility.
RSA 21 requires traffic orders and traffic sign plans to include information such as location, affected road sections, worksite length, remaining widths, time frame, existing signs, and the people responsible for traffic safety during and outside working hours. These are precisely the details that often cause delays when they are missing or described too vaguely. (StVZO.de)
A practical workflow is simple in principle: document the location, check the standard plan, record deviations, place traffic signs and barriers, separate construction phases, add responsible persons, and submit the application with site plan, photos, or sketches where required. The important point is that the standard plan is usually the starting point, not automatically the final local plan.
Which RSA 21 standard plan fits my worksite?
The right standard plan depends on three questions: Where is the worksite located? How long will the work last? How deeply does it affect traffic?
In urban areas, the main issues are often sidewalks, bicycle traffic, parking lanes, entrances, intersections, short work zones, and a dense public environment. On rural roads, visibility, speed, road width, and half-road closures become more important. On highways, advance warning, lane guidance, night work, shorter-duration work zones, and higher safety requirements are central.
RSA 21 contains 33 standard plans for urban roads, 23 for rural roads, and 40 for highways. These figures already show why a generic selection is risky. A “small worksite” can trigger very different planning requirements depending on its road environment. (fgsv-verlag.de)
| Situation | Typical question | What needs special attention |
|---|---|---|
| Urban road | Are sidewalk, bike lane, parking lane, or carriageway affected? | Remaining widths, pedestrian routing, entrances, bus stops, visibility |
| Rural road | Is a half-road closure enough or is a signal system needed? | Speed, sight distance, road width, worksite length |
| Highway | Is it short-duration or long-duration work? | Advance warning, lane reduction, protection systems, night work |
| Recurring work | Can the case be standardized? | Templates, variants, phases, local authority expectations |
Urban road, rural road, or highway: which plan is right?
In urban areas, the right plan is rarely just about the carriageway. Many authority questions arise because sidewalks and bike lanes are considered too late. If a fence, vehicle, trench, container, crane, or material storage affects the side space, the plan must show how pedestrians and cyclists are safely guided. Existing no-parking zones, delivery areas, intersections, and entrances also matter.
On rural roads, the decision depends more strongly on width, speed, visibility, and worksite length. A half-road closure may look straightforward, but it is only plausible when traffic can safely pass the worksite. If curves, hillcrests, longer bottlenecks, or poor visibility are involved, the plan needs more detail.
On highways, planning becomes more demanding. The distinction between shorter and longer work duration, lane guidance, advance warning, traffic diversion, protective systems, and night work must be handled carefully. For many mid-sized companies, this is not an area for improvised drawings. It requires specialized planning and proper quality control.
Which software helps with a traffic sign plan?
Software is useful when it does more than produce neat drawings. A traffic sign plan must be reviewable, locally adapted, and understandable for authority processing. EDV Dr. Haller’s RSA Assistant, for example, states that it can automatically transfer RSA-based rules such as number of delineators, advance warning distances, worksite length, worksite width, and safety areas into scaled plans based on construction parameters. (EDV Dr. Haller)
Other tools focus on ease of use and reusable templates. Deichmann+Fuchs describes its Verkehrszeichen-Planer as software for traffic sign plans according to RSA 21, including orders and material lists for temporary traffic safety; it is browser-based and includes automatic updates for legal or technical changes. (Deichmann+Fuchs)
For smaller companies, an editable template kit can also be useful for recurring work in public traffic space. But the decisive question is not “Which tool draws fastest?” The better question is: “Which process helps us manage standard cases, local deviations, construction phases, responsibilities, and authority feedback reliably?”
How can I create recurring traffic sign plans faster?
Recurring traffic sign plans become faster when a company stops starting from a blank page each time. Typical recurring cases include utility connections, fiber work, maintenance operations, temporary no-parking zones, smaller excavations, scaffolding, crane placement, manhole work, or access protection installations. These cases often look similar, but the details still matter.
A useful system has three levels. First, the company needs reviewed templates for standard cases. Second, it needs a structured way to capture variable information: location, construction period, worksite length, remaining width, sidewalk, bike lane, bus stop, intersection, photos, and contact person. Third, every submitted plan should be documented by result: approved, returned, approved with conditions, or adjusted later.
Over time, this creates an internal knowledge base. The company learns which authority expects which details, which standard plans appear most often, and which special cases regularly cause rework. This is where AI can support the process: not as a replacement for professional competence, but as a structuring layer for data collection, pre-checks, text modules, plausibility reviews, and reuse of proven plan variants.
Which mistakes cause authorities to return the application?
Authorities usually do not return an application because one sign symbol looks slightly imperfect. More often, the overall case is unclear. The application does not show the exact work location, the duration, the affected traffic areas, or the safe routing of pedestrians and cyclists. Missing photos, vague site plans, mixed construction phases, and missing responsible persons also create delays.
Many municipalities explicitly state that work in public traffic space requires a traffic authority order and that supporting documents such as a traffic sign plan, site plan, photos, or sketches may be required depending on the measure. One municipal service page also notes that the approval process can take up to 2 months where extensive coordination is required. (waldenbuch.de)
Another frequent mistake is using a standard plan without checking the local situation. Moravia Akademie notes that RSA 21 standard plans serve as building blocks for standard situations, but they must be checked against the local and traffic-specific circumstances and adapted where necessary; they are not automatically legally binding on their own. (Moravia Akademie)
Why is a standard plan alone often not enough?
A standard plan shows a typical case. A real worksite is rarely typical in every detail. There may be a tree blocking sightlines, a bus stop near the work area, a bike lane ending at an awkward point, a driveway that must remain open, or a construction phase that moves into nighttime. In those cases, attaching a standard plan and leaving the details to the authority is not a reliable process.
For companies, the mindset is important. The standard plan provides the technical direction. The traffic sign plan translates that direction into the actual location. Authorities therefore do not only check whether an RSA plan number is mentioned. They check whether the concrete execution is understandable and safe. The better this translation is, the fewer follow-up questions arise.
How can AI support RSA 21 traffic sign planning in practice?
AI cannot replace a qualified traffic safety professional or the authority’s decision. It can, however, make the preparation calmer, more structured, and easier to repeat. An AI-supported workflow can organize photos, site details, older applications, authority comments, and text modules so that the specialist can make decisions faster.
Useful functions are often simple: checking mandatory fields, marking missing information, finding similar earlier cases, suggesting standard text, separating construction phases, generating checklists, and learning from completed applications. For mid-sized companies, this is relevant because the largest time loss is not always in drawing. It often sits in rework, authority questions, internal handovers, and searching for old project knowledge.
FAQ: How do I create a traffic sign plan according to RSA 21?
An RSA 21 traffic sign plan starts with a site survey, selection of a suitable standard plan, local adaptation, and a clear drawing. It should include location, work period, worksite length, remaining widths, affected traffic areas, existing signs, construction phases, and responsible persons. The plan must show how road users are guided safely through or around the work zone.
FAQ: Which RSA 21 standard plan fits my worksite?
The right standard plan depends on location, duration, and the level of impact on traffic. Urban roads, rural roads, and highways each have different planning priorities. Sidewalks, bike lanes, sight distances, lane widths, intersections, bus stops, traffic load, and construction phases should be checked before selecting or adapting a standard plan.
FAQ: Urban road, rural road, or highway: which traffic sign plan is right?
Urban roads require strong attention to pedestrians, cyclists, parking, driveways, and tight street space. Rural roads focus more on lane width, speed, visibility, and half-road closures. Highways require advance warning, lane guidance, protective systems, and clear distinction between short-duration and long-duration work. The road category should therefore be defined first.
FAQ: Which software helps with traffic sign plans?
Suitable software supports drawing, templates, material lists, authority orders, and recurring worksite cases. The most useful tools allow plans to be adapted to the real location rather than only producing schematic drawings. Companies should also check ease of use, RSA 21 update handling, export formats, version control, and reuse of previous projects.
FAQ: How can I create recurring traffic sign plans faster?
Recurring traffic sign plans become faster when typical cases are managed as templates. This includes standard work types, common RSA plans, checklists, text modules, photo requirements, and local authority preferences. After each application, the company should record whether the plan was approved, modified, returned, or approved with conditions.
FAQ: Which mistakes cause authorities to return the application?
Common mistakes include incomplete location data, missing remaining widths, unclear construction phases, ignored sidewalks or bike lanes, missing photos, wrong standard plan selection, missing responsible persons, and vague time periods. A standard plan that is not adapted to the local site can also trigger follow-up questions or rejection.
FAQ: Is an RSA 21 standard plan legally binding?
An RSA 21 standard plan is a technical basis for standard situations, but it is not automatically the complete solution for every individual case. The competent authority reviews the concrete situation and issues the traffic authority order. The standard plan must therefore be applied, adapted, and completed with the necessary local details.
FAQ: Do I need a separate traffic sign plan for every worksite?
Not always. For simple, short, and low-impact work, a suitable standard plan may be enough if the authority accepts it. However, once local constraints, multiple construction phases, greater traffic impact, pedestrian routing, bike traffic, or unclear guidance are involved, a concrete location-specific traffic sign plan is usually the better route.
FAQ: Who can create a traffic sign plan?
In practice, construction companies, traffic safety firms, planning offices, and specialized service providers create traffic sign plans. The decisive factor is not only drawing capability, but competent application of RSA 21, the German Road Traffic Regulations, administrative rules, and related technical guidelines. Responsibility and qualification requirements must also be observed.
FAQ: How long does approval of a traffic authority order take?
The timeline depends on the municipality, scope of work, coordination needs, completeness of documents, and other affected parties. Simple cases may move faster, while complex projects can take longer. Companies should apply early, especially when police, road authorities, public transport, residents, detours, or several construction phases are involved.
Sources for the figures used
- FGSV Verlag – RSA 21, 176 pages, 2021 edition, replacement of RSA-95:
https://www.fgsv-verlag.de/rsa-21-pdf - FGSV Verlag – Standard plans: 33 urban road plans, 23 rural road plans, 40 highway plans:
https://www.fgsv-verlag.de/rsa-21-pdf - German Federal Ministry of Transport – ARS No. 24/2021 dated November 8, 2021 on RSA 21:
https://www.bmv.de/SharedDocs/DE/Anlage/StB/ars-aktuell/allgemeines-rundschreiben-strassenbau-2021-24.html - City of Waldenbuch – approval process may take up to 2 months where extensive coordination is required:
https://www.waldenbuch.de/-/dienstleistungen/baustellen-auf-oeffentlichen-strassen—verkehrsrechtliche-anordnung-beantragen/vbid6010891
Further reading
- Federal Highway Research Institute / German Mobility Forum – RSA 21 overview
https://www.mobilitaetsforum.bund.de/DE/Themen/Wissenspool/Rechtsrahmen/FGSV_Baustellensicherung_RSA21.html - Moravia Akademie – Traffic authority order and traffic sign plan
https://www.moravia-akademie.de/aktuelles/neuigkeiten/verkehrsrechtliche-anordnung-und-verkehrszeichenplan - StVZO.de – RSA 21 Part A, content of orders and traffic sign plans
https://www.stvzo.de/rsa/teil-a/
