Backlog Math: What an Unpublished Trip Actually Costs You

Somewhere on your phone or in a notes app, there is a trip you have not written about. Maybe two. For a lot of people reading this, it is more like six or eight.

Nobody sits down and decides to let a trip go unpublished. It just accumulates — the way a backlog always does — one deferred weekend at a time. But it is not free. It has a cost, and the cost is more concrete than "I feel a bit guilty about it."

Let us do the actual arithmetic.

---

The cost of writing it, the old way

From the workflow breakdown in an earlier post: a typical 1500-word travel post takes 5-7 hours from raw notes to published, spread across multiple sessions. That number was not invented for effect — it is the honest total of finding your notes, staring at a blank page, drafting, editing, adding links and metadata, and fixing formatting in the CMS.

Five to seven hours does not sound catastrophic for one post. The problem is the multiplier.

Trips sitting in your backlog	Hours to clear, old workflow	That is roughly
3	15-21 hours	Two long weekends
6	30-42 hours	A full work week
12	60-84 hours	Two work weeks

Most people with a real travel habit are somewhere in that 6-12 range, quietly, without having counted it. That is the visible cost — the hours you would need to sit down and spend, all at once, to catch up.

---

The invisible cost: what a trip loses by sitting

The hours are the smaller problem. The bigger one is what happens to a trip while it waits.

Memory decays on a curve, not a cliff. You do not forget a trip all at once — you forget the specific, useful details first: the name of the guesthouse that was actually good, the exact reason a place felt different from what you expected, the small logistical thing that would have saved someone else a headache. The broad strokes survive. The texture does not.

That texture is the entire value of a first-person post. A generic AI-written guide to a place already exists — several of them, mediocre, interchangeable. What a reader cannot get anywhere else is your specific experience, and that is precisely the part your memory is deleting first while the trip sits in the backlog.

So a trip that sits for a year is not the same trip anymore, from a writing standpoint. It has been quietly devalued. Not to zero — a photo timeline and a rough itinerary usually survive — but the thing that made it worth reading is going, and going faster than most people expect.

---

The compounding cost: what unpublished content never earns

There is a third cost that is easy to miss because it never shows up as a loss — it shows up as an absence. A post that does not exist earns nothing: no search traffic, no internal links to other posts, no compounding SEO value, no chance of being the page someone finds two years from now while planning their own trip.

None of this is dramatic in any single month. It is dramatic in aggregate, the way compound interest is dramatic in aggregate. Six posts that could have been published eighteen months ago and were not represent eighteen months of search traffic, links, and discoverability that simply never accrued. That is not a one-time loss. It is an ongoing one, for as long as the post stays unwritten.

---

So what is a backlog actually worth clearing?

Put the three costs together — the hours it will eventually cost you anyway, the texture your memory is deleting on a clock, and the traffic that never compounds — and "I will get to it eventually" turns out to be a more expensive plan than it feels like in the moment.

This is the exact gap the Roami pipeline was built to close: capture the texture on the road before it decays, and cut the desk time from 5-7 hours to 20-45 minutes of editing. It does not make the backlog free to clear. It makes clearing it fast enough that you actually will.