Corrections: how to tell us we are wrong, and what we do about it

What we need from you

You do not need to be polite, formal, or right. A one-line email is fine. The four things that make a correction fast:

1. The URL of the page, and the sentence or table row in question.
2. What you think is wrong — a wrong number, an out-of-date spec, a

   misattributed source, a claim the source does not actually support, a broken link.

3. A source, if you have one. A link to the page that shows the correct value

   is the single most useful thing you can send. We will check it ourselves before changing anything.

4. How to reach you, if you want to know what we did. Anonymous reports are

   welcome and get the same treatment; we just cannot write back.

What happens next

1. We acknowledge it. Target: two business days.
2. We re-check the source ourselves. Not your summary of it, and not our old

   note about it: the live page. If the source moved, we look for the current version and record the new URL and the date we checked it.

3. We decide, and we write down which of these it was:
   • Correction — we were wrong. The text changes.
   • Update — we were right when we checked, and the world moved. The text

     changes and the checked date moves with it.

   • Clarification — the text was defensible but easy to misread. It gets

     rewritten.

   • No change — the source supports what we wrote. We say why, and we link the

     source. If you still disagree, tell us; see "when we disagree" below.

4. We publish the fix with a dated note, and we update last_reviewed on the

   page.

5. We look for the same mistake elsewhere. A wrong number usually appears on

   more than one page, so a correction triggers a search across the site for the same figure, the same source and the same phrasing.

Target for the whole loop: ten business days. Legal and health pages can take longer, because the fix goes back through the reviewer who signed the page off.

How a correction is marked

• In the text. The wrong sentence is replaced, not annotated in place.
• At the foot of the page. A dated line: what the page used to say, what it

  says now, and why. Corrections stay on the page permanently; they are part of the record, not clutter to clear later.

• At the top, when it mattered. If the error changed the meaning of the page —

  a wrong statistic, a wrong statement about the law, a wrong vendor attribute in a comparison — the note goes above the article as well, so a returning reader sees it without scrolling.

• On the dates. last_reviewed moves. published never does. A corrected

  page is not a new page.

• When the whole page was wrong, we unpublish it, leave a short note at its

  URL explaining that it was withdrawn and when, and do not quietly delete it.

Directory and vendor listings

Listings have their own rules because the subjects of those pages are our competitors.

• Any vendor may correct an attribute about their own product by sending the

  page on their own site that shows the correct value. We verify it, change the row, and record the new source URL, checked date and product version.

• No vendor may have an accurate, sourced attribute removed. If your product

  has a microphone and your product page says so, that stays in the row.

• "Not publicly stated" is fixed by publishing it. If a listing says your

  product's hosting country is not publicly stated, the fix is a public page that states it. We will not take the answer by email alone, because a reader cannot check an email.

• Nothing about a listing is for sale. Not the placement, not the wording, not

  the removal. There is no price, and there is no arrangement under which a listing changes for money, hardware, hosting or access.

• Quoted claims stay as quoted. We reproduce a fall-detection claim in the

  vendor's own words. If the wording on your site changes, send it and we will update the quote and the checked date. We will not paraphrase a claim into something stronger or weaker than what you published.

• Removal requests. A vendor can ask to be removed from the directory

  entirely. We will say on the category page that the listing was removed at the vendor's request, and when.

When we disagree

Sometimes the source supports what we wrote and you still think the page is wrong. Two things happen:

• We publish the disagreement next to the claim: what we wrote, what the

  challenger says, and the sources for each. A reader can then judge it.

• If the evidence is genuinely unsettled, the page says it is unsettled. That is a

  legitimate answer, and it is more useful than picking a side we cannot defend.

We do not treat a disputed claim as settled just because nobody escalated it again.

Where to go instead

This is the route for factual errors, out-of-date specifications and sourcing problems on WalledCare Learn. Three things go elsewhere.

• Product support, faults or account questions for a WalledCare sensor go

  through the product contact route on the main site, not here.

• Emergencies. Nothing on this site is a substitute for emergency services. If

  someone is hurt, call 911.

• Medical or legal advice. Our health pages are reviewed by a named clinician

  and our law pages by a named privacy reviewer, and they are still general information about a category, not advice about a person or an organisation.

Contact

info@walledcare.com — subject "Correction". Moneli Automation, Kitchener, Ontario, Canada.

How we source and check everything in the first place is set out in our editorial policy and its methodology section.