Our editorial standards
HBHR builds HR and payroll software, and we write about the work our software supports: paying people correctly, staying compliant, and managing a workforce fairly. Our guides are written for HR leaders, payroll managers and business owners who need to get something right, often under a deadline. This page explains how we produce that content and who stands behind it.
Who writes for us
Every guide is written by a named member of the HBHR team, not an anonymous byline and not a generative tool left to its own devices. Each writer has a profile that lists their role, their qualifications and the subjects they cover, and every article links to it. You can see the full team on our authors page.
We write about what we know. A payroll guide is written or reviewed by someone who has run payroll; a compliance guide by someone who works with the regulations day to day. Where a topic sits outside the team’s direct experience, we say so and we cite sources you can check.
How we review
Guides on regulated or high-stakes subjects, right to work, statutory pay, employment status, data protection, are reviewed by a second qualified member of the team before they publish. The reviewer is named on the article alongside the writer, with the date the review took place. A guide that has been reviewed says so; one that has not carries only its byline, so you always know which you are reading.
How we keep guides current
The law changes and so do the products it describes. We show a visible “last updated” date on every guide, and a “last reviewed” date on those that carry a review. When the substance of a guide changes, we update the content and the date together, rather than leaving a stale page with a fresh timestamp. Minor corrections that do not change the guidance do not reset the date.
How we use sources
Where a guide relies on a specific rule, figure or deadline, we link to the primary source: the relevant government guidance, legislation or official body. Sources are listed at the foot of the article and referenced inline, so you can follow any claim back to where it comes from. We do not cite a source we have not read, and we do not present another organisation’s material as our own.
Independence and corrections
Our guides are editorially independent of our sales team. We recommend an approach because we believe it is right for the reader, not because it routes to a product demo. Where a guide mentions HBHR’s own software, we make that context clear.
If you spot something in a guide that is wrong or out of date, tell us and we will correct it. Accuracy matters more to us than being first, and a correction is not an embarrassment, it is the process working.
Contact
Questions about a guide, a correction, or this policy can go to the editorial team at hello@hbhr.io.
Last reviewed: 1 September 2026. Owned by the HBHR editorial team.