We make mistakes. Pricing changes, features ship, and occasionally a reviewer misremembers a detail or misreads a documentation page. When that happens, we want to know and we want to fix it fast.
How to request a correction
Email corrections@topickz.com with:
- The URL of the page containing the error
- The specific factual claim you believe is wrong
- A source for the correct information (vendor documentation, a dated screenshot, a public filing)
We aim to respond within 72 hours. We investigate every correction request, including ones from vendors with an obvious interest in the outcome. A request from a vendor is not automatically suspicious, pricing pages change and they sometimes catch our errors before anyone else does.
What always gets corrected
- Pricing that has changed since our last verified date
- Feature descriptions that no longer match the current product
- Company names, personnel, or contact details that are wrong
- Broken links or outdated screenshots
- Factual errors we can verify independently
When we make a correction, we add a correction note at the top of the post with the date of the correction and what changed. We do not delete the original text and quietly replace it, you can always see what changed and when.
What won’t change based on a correction request
Our editorial rankings and opinions are not subject to correction through this process. If you think we ranked your tool too low, the answer is not to email corrections@, it is to wait for the next annual re-test and perform better on our documented workflow. We will not change a ranking because a vendor disagrees with our assessment or because a higher-commission affiliate deal is available.
If you believe we made a factual error in our scoring criteria (for example, that we scored your enterprise tier as not including a specific feature when it does), that is a legitimate correction request. We will re-test the disputed feature and update the score if warranted.
Update mechanics
Minor updates (broken links, pricing refreshes) are made silently with the lastmod date updated. Significant updates (feature re-tests, score changes, major pricing revisions) get an explicit note at the top of the post. The last_tested and last_pricing_verified dates in the front matter are updated each time.
Every review shows its last-tested date and last-pricing-verified date at the top of the review methodology box. If those dates are more than 12 months old, treat the review with appropriate skepticism and check the current vendor site before making a purchase decision.