Last updated: September 12, 2026
Software changes weekly. Pricing changes without notice. Features get removed. This page explains how we keep what we publish accurate, and what we do when it isn’t.
Our Source Hierarchy
We verify claims in this order of preference:
- Direct hands-on testing – we used the feature ourselves and saw the result
- Official vendor documentation – help centres, API docs, changelogs, release notes
- Official pricing pages – checked at time of writing, never quoted from another blog
- Vendor announcements – official blog posts and release communications
- Aggregated user reports – clearly identified as such when used
We do not treat another website’s article as a source. If we can’t verify something at one of the levels above, we either leave it out or state plainly that it is unverified.
What Gets Checked Before Publication
- Pricing – every figure verified against the vendor’s live pricing page, and the verification date stated in the article
- Feature claims – confirmed as available on the plan the article says it’s available on
- Limits and quotas – task counts, row limits, API rate limits, seat limits checked against official documentation
- Step-by-step instructions – walked through in the actual product
- Configurations and templates – run before publication to confirm they work
- Screenshots – taken from the current version of the product
- External links – checked as live and pointing where they claim to
Second-Person Review
Technical instructions and workflow configurations are verified by a second member of the team before publication. The person who wrote the steps is not the only person who has run them. Roles are set out in our Editorial Policy.
Dated Pricing
Every review and comparison that mentions price carries a line stating when that pricing was verified:
Pricing verified: September 12, 2026. Software pricing changes frequently – confirm current rates on the vendor’s website.
This is deliberate. A price with no date is a price you cannot trust.
Review Cycle
- Comparisons and pricing-heavy articles – reviewed roughly every 6 months
- Step-by-step tutorials – reviewed when the platform ships a significant interface change
- Any article – reviewed immediately when a reader reports an error
Articles revised substantively carry a visible “Updated” date.
When We Get It Wrong
We will. Software moves faster than any publisher. What matters is what happens next, and that’s covered in our Corrections Policy.
Report an error: contact@nodecurio.com with “Correction” in the subject line. Include the URL and what’s wrong. We investigate within 48 hours.