--- title: "Editorial Policy" date: 2026-11-12 author: "Editor" --- # Editorial Policy TechRT publishes how-to guides, explainers, technology news and statistics pages for people working on a computer or phone. Most readers arrive partway through a task: a setting that will not stick, an app that stopped opening, a Discord or gaming problem they want fixed before they close the tab. This policy sets out how a TechRT page is researched, checked and reviewed before it goes live, and how it is kept accurate afterward. ## Who writes and reviews TechRT TechRT is run by its founders, Rajesh Namase and Tushar Thakur. Each new or refreshed article carries one of them as the named author, and the other founder reviews it. The reviewer is never the author of the same page, and both names appear on the page. Drafting tools assist with research, outlining and language. They do not decide what a page says. The named author owns the sources and the final text, and the named reviewer checks the facts against those sources and signs off. A page with no second sign-off does not publish. ## What we cover, and what we leave out Our core subject is practical: Windows, Mac, Android and iOS how-tos, desktop software, Discord and gaming, plus explainers and statistics pages on the technology industry. We would rather give a reader a step they can repeat than a recommendation they have to trust. We do not publish financial, medical or legal advice. We do not publish press releases or republish wire copy. We do not publish guides whose purpose is to identify, track or scrape a private person. ## Sources Each claim goes back to the organization closest to it. For software behavior that means the vendor’s documentation, support pages and release notes, or the project’s own repository and changelog. For hardware it means the manufacturer’s specification. For a regulatory or legal point it means the filing, the ruling or the regulator’s own notice. For a statistic it means the body that measured it, with the period the figure covers. Community sources have a real place in this subject, because many working fixes start in a forum thread or a bug report. When a fix comes from one, the page says so and links it, and it is never presented as official vendor guidance. We do not source from download portals, spec aggregators, sites that compile other sites’ statistics, paid market-research summaries, or machine-written summaries of other articles. A vendor’s figure about its own product is reported as the vendor’s claim, attributed to the vendor in the sentence. A forecast is labeled as a forecast, with the name of whoever made it. ## Fact checking The supporting passage for each fact is saved before drafting starts, in the source’s own words, with the URL and the date it was read. Every factual sentence in the draft is tied to one of those passages. Software then checks what software checks well: figures against their passages, arithmetic, quotations and dates. A second check asks a different question, whether the passage really supports the sentence as written, at the scope the sentence claims. Our [Fact-Check Policy](/fact-check-policy/) describes these steps in full. A claim that fails is supported with better evidence, narrowed until the evidence carries it, or cut. ## Review The reviewer reads the finished page end to end, against the saved sources, before it is published. The reviewer looks at the steps, the figures and the wording together, because a correct figure in a misleading sentence is still an error. The verification record stays with the article, so a later edit can see what each sentence rested on. ## Rankings and comparisons A list that ranks tools or services states the criterion it ranked by. We do not give scores out of ten, and we do not call something the best without saying what it is best at. ## Advertising and sponsored content TechRT carries advertising and publishes sponsored content. Sponsored work is labeled as sponsored and kept apart from editorial pages. Any commercial relationship that touches a page is disclosed on that page. ## Updates and dates Statistics pages are reviewed on a fixed schedule, and how-to guides are re-checked when an update moves a setting or renames a menu. The date shown on a page changes when its content changes in substance. Small fixes such as a typo or a link are not listed as updates. A guide we can no longer keep accurate is retired rather than left to go stale. ## Errors and contact When we get something wrong, we fix it on the page and record what changed. Our [Corrections Policy](/corrections-policy/) explains how. To report an error or ask about this policy, email or use the [contact page](/contact/).