Editorial policy

Direct answers, visible limits, safer next steps.

The policy below defines how troubleshooting guidance is researched, structured, reviewed, corrected, and separated from commercial influence.

Evidence hierarchy

Model-specific manuals, official support documents, safety notices, standards, and manufacturer instructions take priority. General diagnostic reasoning is used only where it does not conflict with product documentation.

Source labels

Error-code guides require an official reference and a warning that meanings can vary by model, region, firmware, or product family. Symptom guides display whether official sources were checked or whether the page is general safety-first guidance.

Page structure

Each guide should identify the likely meaning, list observable causes, order checks from lower risk to higher complexity, compare outcomes, and state when the user should stop.

Review identity and claims

A review date means the page was checked under this editorial policy and its cited references were re-evaluated. Troublio does not imply a named technician, engineer, or manufacturer reviewed a guide unless that reviewer is explicitly identified on the page.

Similarity and programmatic quality

Shared page structure is allowed, but diagnoses should not be created by changing only the brand, model, or code inside generic text. Error-code content is checked for unusually high similarity, and new pages should add model-specific evidence, display distinctions, observations, or stop conditions that materially help the reader.

Safety

Guides do not instruct unqualified users to open mains-powered equipment, handle refrigerant, bypass interlocks, work near live circuits, or continue when heat, smoke, leaks, swelling, chemical smell, or structural damage is present.

Updates and corrections

Pages include a review date. Material changes to the diagnosis, safety path, sources, structured data, or internal links count as significant updates. Corrections should be made promptly and should not preserve outdated advice for traffic reasons.

Found a problem?

Use the problem submission page and include the exact guide title, model context, and the official document that conflicts with the page.

Submit a correction or missing problem →

User feedback

Helpful and not-yet-helpful votes are collected as aggregate analytics after consent. They are prioritization signals, not proof that a diagnosis is correct for every model.

Commercial independence

Advertisements or affiliate links must be visually separated from editorial guidance. Commercial relationships do not determine the diagnosis, source selection, or order of checks.