Tech Hence editorial standards are designed for technology topics where features, prices and platform policies can change quickly. The method begins with a real reader decision and ends with practical limits, verification steps and a route to correct material errors.
Define the reader outcome
A broad phrase such as “best AI tools” is narrowed to a task, audience and constraint. For example, a student choosing a research organiser has different privacy, citation and budget needs from a company automating customer support.
Use appropriate sources
Official documentation, developer notes, provider policies, security advisories and current product pages are preferred for changing facts. Independent testing and reputable secondary sources can add context. A source is selected because it supports the claim, not because it ranks highly for the same keyword.
Distinguish evidence from judgement
Specifications, prices and published policies are factual claims that can be checked. Ease of use, value and suitability require editorial judgement. Articles should make that distinction visible and explain which criteria produced a conclusion.
Explain trade-offs and uncertainty
Convenience may increase data collection; lower price may reduce support; powerful software may demand more learning; high performance may reduce battery life. A guide should identify who benefits, what becomes harder and when a different option is sensible.
Use AI responsibly
AI may assist with outlines, language review or organising source notes, but it is not treated as an unquestioned authority. Human editorial responsibility remains. Generated material must not invent quotations, hands-on testing, credentials, benchmark results or personal experience.
Protect readers in higher-risk topics
Articles involving accounts, money, privacy, security or health receive additional caution. Tech Hence provides general information, not guaranteed outcomes or individual professional advice. Readers should verify current terms before a purchase or consequential action.
Corrections and updates
A useful correction identifies the URL, the exact statement and supporting evidence. Confirmed material errors should be corrected on the live page. Articles with changing features should be reviewed when an update materially changes the reader’s decision.
The reader promise
Tech Hence aims to provide clear purpose, visible reasoning, realistic limitations and actionable next steps. The official Tech Hence guide explains the publication’s scope, while this standard describes how that promise is applied article by article.
