How does Alpine Letter handle a claim it cannot source?

Alpine Letter is the paid weekly newsletter. It is the business in the ten where I am the product, the editor and the fact-checker, which is exactly why it needs a written process for being wrong. Last week it was wrong, and a reader noticed first.

What did the issue get wrong?

Last week's paid issue said that every cabin booking includes flexible early arrival. It was a passing line in a piece about planning a trip, and it reads as generous. It is also not true, and I should know, because I own the cabins.

Ridgeline Stays' own rule is that standard check-in begins at 4pm and an early arrival is an exception that depends on the cabin being ready and the owner approving it. A reader who had read both the newsletter and the booking terms wrote to ask which one was right.

Where did the claim come from?

That is the question the source note answers. Every Alpine Letter issue has a source note: the material each claim rests on. The editorial source review found no evidence for the claim that every booking includes flexible early arrival. The underlying source only discussed the possibility of an exception when a property is ready and the host approves it. Somewhere between the source and the sentence, "possible, with approval" became "every booking includes". That is an overbroad claim, and it is mine.

Why not just edit the published issue?

Because a silent edit tells readers that what they read may not be what is there now. A paid newsletter is a promise that the text is the text. The rule in the source note is explicit: the issue should carry a correction rather than silently replacing its published text.

So the original stays as it was sent, and the correction is a separate, dated piece of writing that points at it. Anyone who read the original can find out it was wrong. Anyone who reads it later sees the correction attached.

What does a correction contain?

Four things, in order. It quotes the original claim, word for word. It states what the source actually supports: that early arrival is a possible exception when a property is ready and the host approves it, not a universal entitlement. It acknowledges the error to readers plainly, without explaining it away. And it points readers to the original source, so they can read what I read and judge the gap for themselves.

What does the correction not do?

It does not share a guest's booking data. The reader's question could be answered with a specific example from the Ridgeline calendar, and that would make the correction more vivid. It would also mean putting a guest's stay in front of subscribers who have no business seeing it. The newsletter and the cabins are different businesses. One does not get to use the other's records to make a point, even when the owner of both is the one writing.

Who checks the correction before it goes out?

A reader checked the issue, which is a humbling order of operations. The correction is checked against the source note before it runs, and the draft reply to the reader who flagged it says what the correction will say: the source note does not support the wording in the issue, and a correction will be published in the next edition. At the time of writing that is where things stand. The correction is drafted. The next edition has not gone out.

How does the review log work?

The review log keeps both the issue and the source note, side by side, unaltered. The point is that an editor, later, can trace the decision: what was claimed, what the source said, what the correction said, and when. If I change the source note after the fact to make the claim look supported, the log is worthless. So nothing in it is edited; things are only added.

This is a small newsletter. The log is not a system; it is a folder. The discipline is the same as it would be at any size.

What changes in the next issue?

The claim about cabins will be corrected, with the four parts above. The planning piece it sat in will not be rewritten. And the source note for the next issue will be read one more time before sending, with the specific question in mind: does the source say this, or does it say something narrower that I have rounded up.

Q&A

Questions subscribers have asked since the reader's note arrived.

Last updated 30 September 2026.