Editorial / corrections published within 14 days
Editorial standards
Every clause below is paired with the thing that enforces it. A standard with no mechanism behind it is a wish, and this site is asking to be trusted on numbers.
- Author One person
- Corrections Within 7 days
- Publication 14 days to fix
- Log Substantive only
The author
Who writes and reviews this site
Everything here is written by Mark McNeece, director of BSolve IT Limited, who also did or supervised most of the work it describes.
On a single-person site, the author and the reviewer are the same person. That is declared on every page rather than dressed up with an invented second name, because a reviewer line that names a person who does not exist is worse than no reviewer line. The review is real: a page's reviewed date moves only when its content has actually been re-checked against its sources.
The code
The standards, and what enforces each one
-
01
No figure is published without a source.
Every number lives in one data file with its value, its unit, the date it was measured and a URL where a reader can check it. Pages render figures through that register, so a number with no entry cannot be put on a page.
-
02
The visible date, the schema date and the sitemap date are the same date.
All three read one "reviewed" field per page. There is no second copy to fall out of step, and no way to bump one without bumping all of them.
-
03
The contents list and the structured data cannot drift.
The on-page table of contents and the schema hasPart array are generated from the same array in the same file. Editing a section heading changes both or neither.
-
04
Word counts in structured data match the page.
wordCount is computed from the rendered body at request time, not typed into a data file, so it cannot become stale after an edit.
-
05
Every external link is verified live before publication.
A script fetches every outbound link on every page and fails the build on anything that is not reachable. Each source in a study also carries the date it was last checked.
-
06
Every claimed URL behaviour is tested.
A harness asserts that all 475 URLs from the old site return exactly the status the published disposition says they should, run against local before launch and against live after.
-
07
Limitations are published alongside findings, not instead of them.
Every study carries a section stating what its numbers do not show. It is written before the piece is finished, not bolted on if there is room.
-
08
This site never retells a story one of our brands already publishes.
Research here is the pattern across projects, and every figure links down to the brand case study that owns the underlying project.
Sourcing
Sources and quotations
Primary sources are preferred over commentary about them. Where this site describes what a search engine does, it quotes that company's own documentation and links to it, rather than paraphrasing a blog post that paraphrased the documentation.
Quotations are verbatim and attributed, with the date they were checked, because documentation changes. Where a quoted source later changes, the page gets an update log entry rather than a silent edit.
Nothing on this site quotes a person who did not say the thing quoted. There are no invented expert endorsements, no unattributed "experts say", and no statistics carried over from another article without going back to the original.
Client work
Writing about client work
Clients are anonymised by default. A client is named only where they are already publicly named in a case study they agreed to, and only for the facts that case study already carries.
Structural facts, such as how many pages a site had, are publishable anonymised. Commercial facts, such as revenue, lead volumes, internal arrangements, suppliers or insurers, are not published at all, and are excluded before writing starts rather than anonymised afterwards and hoped for the best.
The full sourcing process is on the build standard page.
Production
How this site is produced
Drafting and technical assistance may be used while preparing a page: outlining, checking code, running the verification scripts. Every word published is read, checked and approved by the named author before it goes live, and every figure is traced back to its record by hand.
Nothing is published because a tool produced it. Where a source could not be verified, the claim is cut rather than softened into something vaguer that would survive review.
Corrections
How to report an error, and what happens after
Report an error to support@bsolveit.com. Reports are investigated within seven days, and any needed correction is published within fourteen days of being confirmed.
Substantive changes, meaning corrections, revised figures and new sections, are recorded in the affected page's update log with the date and what changed. Typographical and formatting fixes are made silently, because logging them would bury the changes that matter.
The reviewed date on a page is not a freshness signal and is never bumped to look current. It records when the content was last checked, and nothing else.