ABOUT SOFTENERWISE
How we build our guides
Original references, transparent calculations, and clear limits on what a guide can tell you.
Use sources that fit the claim
Model-specific instructions should come from the matching manufacturer’s manual or support material. General reference sources may explain a principle, but they do not establish the settings or service procedure for every system.
Sources are linked where they help support an explanation. A model number, version, date, and applicable operating condition matter when they affect the answer.
Show the calculation
Tools expose their inputs, units, formulas, and worked examples. Example values are identified as arithmetic scenarios, not measured averages, performance tests, or universal settings.
Be accurate about experience
We distinguish source-based research, calculations, illustrations, and actual testing. We do not invent product-use experiences, professional qualifications, reviewers, or endorsements. A reviewer is credited only when a real review has taken place.
Use AI with clear responsibility
AI-assisted tools may help with writing, code, and illustration. That assistance does not establish that a technical claim has been independently verified. A guide should provide enough source context for readers to assess the scope of its claims.
Update for a reason
Corrections and substantive changes should explain what changed where that context matters. Publication dates are preserved; changing a year alone is not a content update.
Separate guidance from promotion
Commercial relationships, if introduced, should be disclosed near relevant content. Our current disclosure page describes what is active on this site.