Corrections

Every material correction to a page on this site is logged here with the date, the page, what was wrong, and what it now says. Entries are never removed, edited or reordered.

A published corrections log is a small thing that does a lot of work. It shows a reader that the site has a memory, that mistakes are treated as events rather than embarrassments, and that a page read six months ago can be checked against what it says today.

The log

28 September 2026. Gratefully pricing, on 19 pages. We
described Gratefully’s entry price as $4,800 a year for five seats. Two things
were wrong. The five seat tier is $4,788 a year, not $4,800, and it is not the
entry price: there is a free plan for one person, which we did not mention
anywhere. Several pages used the figure to tell organizations under about $1m
that the product was out of reach, so the error could have changed a reader’s
decision, not only a number. We also described the free trial as four weeks
with a seven day grace period, on the review page and the Dataro comparison; it
is 14 days of the top plan, with no card, after which the account moves to the
free plan rather than lapsing. All pages now carry the corrected prices and the
free tier, and the review page carries the full four tier table.

28 September 2026. Gratefully integrations, on four pages.
We listed Blackbaud Raiser’s Edge NXT and Google Workspace as integrations.
Neither is a connector. The vendor’s product page lists live CRM connectors
for Salesforce for Nonprofits, both Nonprofit Cloud and NPSP, plus Bloomerang
and Little Green Light, with Mailchimp, Constant Contact and HubSpot supplying
email engagement, and everything else arriving by CSV import or document
upload. A Blackbaud shop could have read our pages and expected a connector
that does not exist. The four pages now name the real list, and the review
says plainly that the route in for Raiser’s Edge is the CSV import. Found
while checking the vendor’s site after the pricing correction below.

Both corrections were prompted by Gratefully, which is a client of ours,
and both were verified against gratefully.io the same day.

What gets logged

The test is whether a reader could have acted differently based on what we previously said.

• Any change to a figure, threshold, deadline, fee or rule.
• Any change that alters a recommendation or conclusion.
• Any misattribution or incorrect description of an organization.
• Any source that turns out not to support the claim made from it.

Typography, formatting, broken links and rephrasing that changes nothing are fixed without a log entry. Clarifications, where something was accurate but open to misreading, are noted on the page itself where the misreading could have mattered.

What an entry contains

Each one records the date the correction was made, the page affected, a description of what was wrong, what it now says, and who reported it unless they asked otherwise.

The original claim is described rather than erased. Silently editing a page and leaving no trace is the practice this log exists to avoid, and it is unfortunately common.

Reporting an error

Send it to the contact page. Tell us the page and what is wrong, and include the source showing the correct position if you have it.

Corrections are credited to whoever reported them unless you prefer otherwise. You do not need to be certain, and you do not need to be polite about it. A reader who takes the time to tell us we are wrong is doing us a favour.

If we disagree

You get the reasoning, not silence. If we believe the page is correct we will explain why, cite what we relied on, and you are free to publish that exchange.

Where the disagreement is about judgement rather than fact, we may publish your response alongside the page instead of changing it.