Why this journal exists

A trail journal is only worth reading if someone walked the ground first. That single idea shapes everything published here.

Orebic Trail Collective keeps notes on coastal and mountain routes in South Africa for walkers who plan their own days out. Nothing goes up on the strength of a map alone. A path is walked, checked and written up before it appears, and the write-up says what was actually found rather than what the route is supposed to offer.

The notes stay plain on purpose. Distance and elevation, where water shows up and where it does not, how exposed a ridge feels once the wind picks up, which months suit a traverse and which ones turn it into a different walk. Gear notes sit beside the route notes because footwear, packs and layering behave differently on wet coastal ground than on a dry mountain path.

Walked before written

Every route page starts on foot. If a section was not covered, the report says so instead of filling the gap with guesswork.

Conditions over promises

Overgrown stretches, faded markers and shortcuts that save time are recorded as they were met, so the next walker can judge the route for themselves.

Notes that stay open

Route notes from other walkers are read and folded in. A path changes between seasons, and the journal is meant to change with it.

The point is not to sell a route or dress up a hard day as an easy one. It is to hand over what a walker needs to plan honestly: the ground underfoot, the water available, the wind on the open sections and the season that suits the traverse. Read it, then go and check it yourself.

How the notes get kept

Between walks, the journal lives in notebooks, marked-up maps and a running log of trail conditions.

Field notes are written by hand on the path, then copied up with the date, the weather and the state of the ground. Nothing is published until it has been walked and checked.

Annotated maps

Water points, exposed ridge sections and places where markers have faded get marked straight onto the map, so the next walk starts with what the last one found.

A condition log

One list tracks paths that were overgrown and paths that were clear, so the same route can be compared across months instead of guessed at.

Gear notes kept with the route notes

Footwear, packs and layering sit in the same notebook as the route itself. What works on a wet coastal path is not the same as what works on a dry mountain traverse, and the notes are written that way.

How the notes are kept between walks

Nothing here is written up from memory at a desk. The material behind each published route page starts on the path, in handwriting, and only moves into the journal once the walk has been done and checked again.

  1. Step one

    Field notes on the path

    Handwritten entries taken while walking, not after. Date, weather, the state of the ground underfoot, and anything that slowed the group down.

  2. Step two

    Maps get marked up

    Water points, exposed ridge sections and stretches where the markers have faded are pencilled onto the map so the next reader can see them at a glance.

  3. Step three

    A running condition log

    One list tracks paths that were overgrown and paths that were clear, so the same route can be compared across months instead of judged on a single visit.

  4. Step four

    Gear notes sit alongside

    Footwear, packs and layering are logged next to the route notes, because what works on a wet coastal path is not what works on a dry mountain traverse.

Nothing is published until it has been walked and checked. If a report is not yet confirmed on foot, it stays in the notebook.