EDITORIAL
Editorial Policy
This page describes the rules behind every guide on the site: how it is written, how it is tested, what its labels mean, and what happens when something in it is wrong. The intent is that a reader can tell how much weight a page deserves before following it.
One task per page
Each guide solves one specific job, such as forwarding invoice attachments into a spreadsheet folder or drafting replies to a shared inbox. A page that tries to cover three jobs is split into three pages. This keeps the prerequisites honest and makes a guide possible to finish in one sitting.
Two verification states
Every guide carries one of two labels, and the two are never presented as the same thing. The label appears near the top of the page, with the date attached.
| Label | What it means | What it does not mean |
|---|---|---|
| Verified | A human ran the workflow end to end in a real account on the date shown, including the failure cases listed below. | That the vendor has not changed something since that date. |
| Documentation reviewed | Written from the vendor's own documentation and interface, without a full hands-on run of the workflow. | That the steps have been executed successfully by anyone. |
A documentation-reviewed guide is not upgraded to verified because it looks correct. It is upgraded when someone has run it and recorded the date.
How a guide is tested
The same five cases are attempted before a guide is marked verified. A guide that fails any of them is either fixed, or published as documentation-reviewed with the failure named.
- Normal input: the expected data, in the expected shape, produces the expected result.
- Missing fields: a record with an empty subject, no attachment, or no address does not break the run silently.
- Ambiguous input: a message that could be classified two ways is handled predictably, not randomly.
- Duplicate trigger: the same event firing twice does not create two rows, two emails, or two charges.
- Expired authorization: a revoked or expired connection fails loudly, and the guide says how to reconnect.
What every guide states
- Prerequisites: accounts, plan level, permissions, and anything that must exist before step one.
- Cost and plan caveats, flagged as needing confirmation, because plans change more often than anything else on the page.
- Failure modes: what usually goes wrong, and what the error looks like.
- The exact point where a human review is mandatory, rather than optional.
- The verification label and the date the check was made.
Screenshots
Screenshots are taken from the current interface at the time of writing, and the date of the capture matches the guide date. Where an interface has changed since a screenshot was taken, the screenshot is replaced rather than annotated with an apology. Stock imagery of a dashboard is never used to stand in for a real screen.
How AI is used
AI assistance is allowed for drafting and structure: outlining a procedure, tightening wording, drafting an explanation of a concept, or organizing a table. It is not allowed to stand in for using the product.
- A human operates the tools, clicks the buttons, and observes what actually happens.
- A human approves every page before publication. No guide is published automatically.
- No guide is marked verified on the basis of model output alone.
- Where a claim cannot be checked, it is removed rather than softened into something plausible.
Corrections
If a step is wrong, a screenshot is stale, or a price is out of date, report it. Write to mail@keliecorp.com with the page address and what went wrong.
What happens next: the report is checked against the live interface, the page is corrected or the verification label is downgraded, and the date at the top of the guide changes. Corrections that change a step are noted at the foot of the guide so a reader who followed the old version can see what moved.
Review schedule
All guides are reviewed quarterly, whether or not a problem has been reported. Between scheduled reviews, a guide is re-checked when a vendor changes its interface, reprices a plan, or removes a feature the workflow depends on. A guide that cannot be re-checked is labeled as unverified rather than left looking current.
Commercial independence
Advertising, sponsorship, and affiliate arrangements do not decide what is covered or how a tool is described. The specifics of how links are labeled and where disclosure appears are set out in the affiliate disclosure. How the site handles data is set out in the privacy policy.