Consumer

How to document missing, covered, ambiguous, or contradictory road signs

Have you ever followed a sign... only to discover another saying the exact opposite five metres later? Or none at all, just when needed. When road signs create confusion, the difference lies in documenting it well and safely. Here is how to do it practically.

1. How it usually happens

The scene is familiar: roadworks, makeshift detours, signs covered by trees or turned by the wind. Or a creative combination of temporary and permanent signs telling different stories.

Sometimes the problem is the total absence of directions. Other times it is an excess: too much information, perhaps contradictory. The result is the same: drivers have to interpret, often in seconds.

From the road manager's perspective, signs should be clear and consistent. From the driver's perspective, reality can be much more confusing, especially in traffic, darkness, or rain.

A classic anecdote: "no entry" on one side and "car park open" right after. Someone who documented both things at the same time manages to turn a confusing tale into a concrete situation.

2. What you need to prove

The central point is showing that the signage, in that spot and at that moment, was missing, barely visible, or inconsistent.

You need to make clear:

  • presence or absence of signs at the critical point
  • actual visibility (covered, tilted, damaged, hidden)
  • any contradictions between multiple signs
  • road context (junction, curve, entrance, car park)
  • conditions affecting perception (light, traffic, obstacles)

Basically: "this is how the situation looked to the driver".

3. What to collect

Here it is crucial to narrate the scene, not just the sign.

  • photos and videos of the signage (or lack thereof)
  • wide shots showing road and context
  • visual sequence of approach (where the driver comes from)
  • details of covered, turned, or deteriorated signs
  • presence of elements obstructing the view (trees, vehicles, construction sites)
  • any conflicting signs
  • lighting conditions (day, night, rain)
  • GPS position or map screenshot
  • any available official reports or communications

A little trick: taking a short "moving" video at walking pace simulates actual perception better than an isolated photo.

4. How to proceed

The procedure always starts with safety. Stopping in the wrong spot to take a photo can cause more problems than it solves.

If you can stop safely:

  • park in a suitable spot
  • walk back to the area
  • document general context first, then details

If stopping immediately is not possible:

  • proceed to a safe point
  • mentally note position and dynamics
  • return to the spot under calmer conditions, if possible

Then:

  • create a logical sequence (arrival → critical point → consequence)
  • include both what is there and what is missing
  • keep original files without modifications
  • organise everything systematically

After gathering the material, you can timestamp the main files to secure the observed conditions in time.

The goal is to make whoever looks at the images understand what a driver actually saw at that moment.

5. Mistakes to avoid

Some mistakes make documentation ineffective:

  • photographing only a sign without context
  • ignoring the driver's point of view
  • not documenting any contradictions
  • stopping in dangerous spots
  • taking blurry or unreadable images
  • modifying or compressing files

A practical tip: always think "where is the driver coming from". If that isn't clear, the images lose strength.

Having free, pre-organised, and timestamped documentation allows you to show a concrete situation without having to explain it only in words.

6. After documenting

With the material ready, you can act more clearly.

  • report the situation to the authority responsible for the road
  • attach organised and understandable evidence
  • keep any replies or references
  • if the situation caused a problem, consider available assistance or protection channels

If disputes arise, having a clear visual sequence helps shift the discussion from "maybe" to "this is how it was".