Editorial policy

What we cover, and what we do not

We write about a narrow set of subjects: invoicing and getting paid, the documents small businesses have to produce, image formats, and web performance. We chose that scope because it matches the tools we build and the work we actually do. When a topic falls outside it, we do not write a thin article to catch the search traffic — we link to someone who covers it properly, or we leave it alone.

How a guide gets written

1. Start from a real question. Usually one that came up in our own work or in a message from a reader — “does my invoice need my address on it?”, “why did my PNG get bigger?”
2. Go to primary sources. For anything legal or regulatory, that means the statute, the tax authority’s own guidance, or the standards document — not another blog post. For anything technical, that means the specification, and where possible our own measurements.
3. Write the answer, then the context. The direct answer goes near the top. The nuance follows. We do not pad the opening with three paragraphs of throat-clearing to push the answer below an advert.
4. Mark what varies. Where a rule depends on jurisdiction, business size or registration status, we say which, rather than flattening it into a single confident claim.
5. Cite it. Every guide that makes a legal, tax or regulatory claim carries a sources list linking to the documents it relies on.

Sourcing standards

• Legal and tax claims are sourced to the relevant authority — for example the IRS, HMRC, GOV.UK, or the text of the legislation itself.
• Technical claims about formats, browsers and performance are sourced to specifications, browser documentation, or measurements we can reproduce.
• We do not cite content farms, undated pages, or articles that themselves cite nothing.
• If we cannot find a solid source for a claim, we either leave the claim out or state plainly that it is uncertain.

Dates and review

Every guide shows when it was published, and when it was last reviewed if that is a later date. Guides touching rules that change — tax thresholds, statutory payment terms, browser support — are revisited at least annually and whenever we learn of a change. We do not bump a date without actually rereading the piece against its sources.

Corrections

If we publish something wrong, we fix it and update the review date. For a change that alters the substance of the advice, we note what changed at the foot of the guide rather than quietly editing it. Please report errors to info@talentrasolutions.com — a specific correction with a source is the most useful message we can receive.

Advertising and independence

This site is funded by display advertising. That relationship is arm’s length: we do not choose which ads appear on a page, advertisers have no input into what we write, and no guide is commissioned, reviewed or influenced by an advertiser. We do not publish sponsored posts, paid guest posts, or paid links. If that ever changes, any sponsored content will be labelled as such at the top of the page, and we will say so here.

We also do not use affiliate links. When we recommend an approach, there is no commission attached to it.

On the use of AI

We use AI tools the way we use a spell-checker or a search engine: to draft an outline, to find a source we then read ourselves, to tighten a paragraph. We do not publish machine-generated text as-is. Every claim in a published guide has been checked by a person against a source, and every guide is read end to end by a person before it goes live. A guide that is merely plausible is not good enough; it has to be right.

Who writes this

The guides are written by the same small team that builds the tools on this site. More about us, and why the site exists, on the about page.

Questions about this policy: info@talentrasolutions.com. — Talentra Solutions