Trust in a technology publication rests on a simple thing: are the facts right? This policy describes how Techiadd checks its work before it reaches you, and what we do when something slips through anyway.
What we verify
Before publication we check the claims an article depends on. In our world that means prices, model names and specifications; release and availability dates; performance figures and benchmark results; quotes and who said them; and any factual assertion about what a product or company has done. If a number or a claim is load-bearing, it gets confirmed before it is published.
How we verify it
We work from primary sources wherever possible: a manufacturer’s official specifications and pricing, a published research paper, an official announcement, court or regulatory filings, or our own hands-on testing. We are wary of figures that appear only in marketing material or that circulate without an original source, and we try to confirm important claims through at least one independent route. When we quote someone, we check the quote against the recording or the original document.
Testing as verification
For reviews, the most important fact-check is the test itself. We do not take a manufacturer’s performance claims on trust — we measure them where we can, using the methods described in How We Test, and we report what we actually found rather than what we were told to expect.
Who is responsible
Accuracy is not left to chance or to a single person working alone. Every article is checked by an editor before publication, and the named section editor is accountable for the accuracy of what their section publishes. For significant or sensitive stories, the Editor-in-Chief, Marcus Chen, has final sign-off. The writer’s byline and the editor’s oversight mean there is always a named human standing behind the facts.
Handling uncertainty
Sometimes a fact cannot be fully confirmed by deadline. In those cases we are honest about it: we attribute the claim to its source, we say what we have not been able to verify independently, and we update the piece once we know more. We would rather tell you what is uncertain than present a guess as a fact.
Sources we treat with caution
We treat leaks, rumours and unverified specifications as exactly that, and we label them clearly when we report them at all. We do not launder a rumour into a fact by repeating it without qualification, and we tell readers how solid — or how speculative — a piece of pre-release information is.
When we get it wrong
No process is perfect. When an error reaches publication, we correct it openly under our Corrections Policy, and if a particular type of mistake recurs we change the process that allowed it. If you spot a factual error, please write to corrections@techiadd.com — readers are part of how we keep the record straight.