Editorial policy and method
How AI in Plain decides what to cover, how pages are researched, and what we will never do.
How a guide is built
We start from the question a reader actually asks, write the short answer first, then the steps in order. Steps are checked against the vendor's official documentation and help centre, and each guide carries the date it was last checked. Where a guide describes a principle rather than a specific screen, it says so, because an interface we have not seen is not one we will describe.
When a step breaks
Readers report, we re-check and fix the page. A guide that cannot be re-verified is marked as such rather than left to mislead.
What we never do
- Sell a ranking, a score, a placement or a positive sentence.
- Claim personal testing we did not perform.
- Publish numbers without a source and a date.
- Let a commission rate decide coverage.
- Use invented reviewers, invented testimonials or stock "customer" quotes.
Frequently asked
Do you personally use every product you cover?
No, and we will not pretend otherwise. Where a page is based on first-hand use it says so, with the plan and the dates. Otherwise it is built from documentation, pricing history and verified user reports, and it says that too.
Can a vendor pay to be included or to improve a score?
No. Vendors can send corrections with sources, which we check like any other evidence.
How often are pages updated?
Prices and features are re-checked on a schedule and each page shows its last-checked date. Readers’ corrections are handled as they arrive.