Skip to main content

Editorial standards

Useful answers require honest sourcing and visible limits.

These standards govern FormEsque guides, templates, comparisons, blog articles, and product education. They describe the process we intend readers to hold us to; they do not imply legal or professional review where none is named.

Effective and last updated: July 15, 2026

Publishing principles

Use the strongest available source

Product, pricing, legal, regulatory, and technical claims should link to the primary source whenever one is public. Third-party discussion can identify customer questions, but it is not treated as proof of a product fact.

Separate fact, judgment, and limitation

A comparison explains workflow fit and tradeoffs instead of declaring a universal winner. Current FormEsque limitations are stated on the relevant page, especially for payments, subscription availability, accounting, legal advice, and enterprise contract management.

Never manufacture authority

FormEsque does not publish invented testimonials, ratings, customer counts, awards, certifications, named reviewers, or performance results. A real author, reviewer, customer, or metric is added only after identity, permission, and evidence are verified.

Update or correct the page

Material product or source changes should update the page date and affected copy. Clear errors should be corrected rather than hidden. Readers can report an issue through the support page with the page URL and source in question.

Comparisons

Competitor pages use public official product and pricing sources, show the date those sources were checked, describe fit on both sides, and include a non-affiliation disclosure. Competitor names and trademarks remain the property of their owners.

Browse comparisons

Drafting tools and professional review

Drafting tools may assist content preparation. Publication does not mean a lawyer, accountant, engineer, clinician, or other specialist reviewed the page. When a named professional review is relevant, FormEsque will identify that person only after the review and permission are documented.

Report a correction

Found something that needs a correction?

Send the page URL, the statement in question, and the strongest supporting source you have. Product support requests should use the same support page without including sensitive customer documents.

Contact support