Corrections & Fact-Checking Policy
We publish Microsoft licensing analysis that enterprise buyers rely on for high-value commercial decisions, so accuracy matters more than reach. We aim to be conservative and correct, and when we get something wrong we fix it openly rather than quietly. This page explains how we fact-check, how to report an error, and how we handle corrections.
How we fact-check before publishing
Every substantive Microsoft commercial claim is checked against primary sources — the Microsoft Product Terms, the Microsoft Customer Agreement, Enterprise Agreement documentation, and official Microsoft pricing and licensing pages — and reviewed by a second senior partner before publication under the two-partner rule set out in our Editorial Standards. Figures drawn from our own engagement book or research function are checked against the underlying data.
Report an error
If you believe something we have published is inaccurate, out of date, or unclear, tell us through our contact form. To help us verify and act quickly, please include:
- The page URL.
- The specific statement you believe is incorrect.
- What you believe the correct position is, and a source if you have one.
Because Microsoft commercial terms change frequently, a guide that was correct when published can become outdated when Microsoft revises the underlying terms. We treat "this is now out of date" reports with the same seriousness as factual-error reports.
How we respond
- Acknowledgement: we aim to acknowledge correction requests within three business days.
- Verification: we check the claim against primary sources and our own data.
- Action: if the claim is wrong or outdated, we correct it and update the article's "last updated" date and structured-data
dateModified. - Transparency: for a material correction — one that changes the substance of guidance a reader might act on — we note at the foot of the affected article what was changed and when. Minor fixes (typos, broken links, formatting) are made without a logged note.
Distinguishing corrections from updates
A correction fixes something that was wrong at the time of publication. An update refreshes content that was accurate when written but has been overtaken by a Microsoft change. Both are reflected in the article's "last updated" date; only material corrections carry an explanatory note.
Editorial accountability
Accountability for the accuracy of published content rests with the firm and its managing partner, not with individual authors. We do not publish anonymous third-party content, and we do not allow commercial relationships to influence whether or how we correct an error — consistent with our Disclosures.