Accuracy

Every article is checked against primary material before publication: vendor documentation, published standards, regulatory guidance or the direct experience of practitioners who have run the process being described. Where a claim cannot be substantiated, it is removed rather than softened.

We avoid false precision. If we cannot verify a figure, we describe the range or the mechanism instead of quoting a number. We do not publish statistics without an identifiable basis, and we do not attribute claims to research we have not read.

Sourcing

Preferred sources are, in order: public product and API documentation; official regulatory, tax and standards material; publicly filed company statements; and named practitioner experience. Vendor marketing material is treated as a claim, not as evidence.

Every article lists the categories of source used in a sources and further reading section. We do not fabricate citations or link to material we have not consulted.

Corrections

Factual errors are corrected in place as soon as they are confirmed, and the article's updated date changes. Substantive corrections — anything that changes the meaning of a passage — are described within the article so readers can see what changed.

Corrections can be requested via the contact page. We respond to correction requests before we respond to anything else.

Vendor coverage

We cover vendors because buyers cannot evaluate a market without them. Coverage describes capability, architecture and trade-offs. We do not rank vendors, publish scores, or maintain 'best of' lists that imply a testing process we have not run.

No vendor sees an article before publication, and no vendor can pay for coverage, placement, inclusion or removal.

Historical claims

A significant share of HR software's current structure is the result of acquisitions and platform shifts from earlier eras. We write about that history because it explains today's products.

Historical events are always framed as historical, written in past tense, and dated only when we are confident in the date. We never republish an archived announcement as current news, and we do not imply that a past acquisition, partnership or product release is a present-day development.

Product information

Product capabilities change frequently. Descriptions reflect our understanding at the article's updated date and are written at the level of capability categories rather than release-specific feature lists, which age badly.

Readers evaluating a platform should confirm current behaviour with the vendor's own documentation and in a scoped trial or demo environment.

Conflicts of interest

Contributors disclose any commercial relationship with a vendor to the editor before writing, and are not assigned coverage where a material conflict exists.

The publication holds no equity in the vendors it covers and accepts no consulting engagements from them.

Editorial independence

Editorial decisions — what to cover, how to frame it, and what to leave out — are made by the editorial desk alone. No commercial arrangement grants influence over that process.

Sponsored content disclosure

If sponsored or paid content is ever published, it will be labelled as such at the top of the page, excluded from editorial indexes, and visually distinct from editorial articles. No such content is published today.

Update policy

Evergreen guides are reviewed periodically and revised where the underlying practice has moved. Each article shows both a published and an updated date so readers can judge currency at a glance.

Where an update materially changes a recommendation, the change is described in the article rather than made silently.