Editorial standards
The rules every page on this site follows. Reviewers are accountable to these in writing.
Authorship
Every tool page carries a byline naming the editorial team that reviewed it and the date of the last review. Bylines are real, not pen names. Multiple contributors share the same editorial identity so a reader can trust a single voice across the catalog without tracking individual authors.
Voice
Plain English. Active voice. We explain things directly without filler. We do not use marketing language to describe a calculator. We do not start a section with "in today's fast-paced world" or close with "we hope this was helpful." The reader is here to compute something, not to be sold to.
What we will not publish
- AI-generated explanations. Tool descriptions, "how it works" sections, examples, and FAQ entries are written by a human. AI assistance for outline or grammar is fine; AI prose published as editorial voice is not.
- Templated sibling pages. We do not generate one tool page per minor variation (every unit-pair conversion, every state permutation) just to capture more search terms. One canonical tool per problem, with worked examples covering common variations.
- Unsourced formulas. If a tool computes a value, the page names the source the formula comes from.
- Hidden affiliate placement. If a page links out to a commercial product, the link is disclosed as such.
Review cycle
Tools are reviewed at minimum every twelve months. Tools that depend on regulations which change (tax brackets, labor law, building codes) are reviewed when the regulation changes, regardless of the twelve-month minimum. The "last reviewed" date in the byline always reflects the most recent substantive review.
Corrections policy
When a reader reports an error and the report is correct, we:
- Fix the tool or content within seven days of confirming the report.
- Update the last-reviewed date.
- Note the change in the editorial changelog.
- Reply to the reader who reported it.
Corrections that materially change a published result (a tax calculation, for example) carry a visible note on the tool page for at least 30 days after the fix.
Reporting a problem
Send corrections to the address on the contact page. Include the tool URL, the input you used, the result you got, and what you expected.