Editorial Policy & Research Methods
How SavvySkull guides are researched, sourced, illustrated and corrected, including how AI assistance is used and who is responsible for what is published.
DeltaSpark is responsible for everything SavvySkull publishes. The diagram shows the path every guide takes, and the sections below cover each step in practice.
What each guide must deliver
Each guide addresses one task, such as sizing equipment, reading a protection claim, or writing a request for quotation. Each also gives you at least one reusable asset: a comparison table, a checklist, or verification steps you can apply to your own situation. The reusable tables are collected on the checklists and templates page.
How a reader task is chosen
We start from a task that a buyer, site lead, engineer or maintenance team has to finish, and only then look at products. The test: if every commercial link were removed, could the reader still complete the task with the page alone? If not, the topic is not ready. Topics are grouped into four areas, listed on the power and lighting, cases and protection, camp and site equipment and buying and maintenance hubs. Guides compare published specifications. They do not publish a ranked best-product list.
Source priority
We prefer sources in this order:
- Model manuals for the specific equipment under discussion.
- Original test documents.
- Standards publishers and accreditation bodies.
- Public technical documentation from government agencies and technical organizations.
Manufacturer statements are used where they are the only source, and they are labeled as manufacturer statements. A claim in marketing copy is not treated as a verified fact. Where we cannot verify something, the guide says so and points readers to the current edition of the standard or the model manual.
When sources conflict
Sources sometimes disagree, for example when a product page and its manual state different figures. In that case the more specific and more controlled document wins: the manual for the exact model outranks a general product page, and an original test document outranks a summary of it. If the disagreement cannot be settled, the guide does not quietly pick a side. It says the documents differ, names them, and tells the reader to ask the supplier which one applies to the model being bought. The same approach appears in the guide to checking a supplier’s test report, where conflicting identifiers between a report and a product are treated as a reason to stop and ask.
Recording editions, models and scope
Standards are revised, and models change. When a guide cites a standard, it records the edition, and where the edition is unknown it says so and tells the reader to check the current one. When a guide discusses a figure for a product, it identifies the model and version the figure belongs to. When a claim only applies in certain conditions, such as a protection rating that covers a specific sample configuration, the guide states that scope next to the claim. How to read IP ratings shows why this matters: the same code can describe different configurations.
Units and conversions
Guides always show units. Power is given in watts, energy in watt-hours, and lighting in lumens or lux, and the guide says which one it means. Where a conversion is needed, the formula and the numbers are written out so the reader can repeat it. For example, the sizing method multiplies watts by hours to get watt-hours. We do not mix units in a table without labeling them.
Phrasing we use
Figures that come from a manufacturer are introduced with “According to the manufacturer’s published specifications…”. A comparison names the manuals it uses. “We tested…” is reserved for a real, documented test, and a guide that uses it states what was tested, who carried out the test, the conditions, and the limits of the result.
Worked cases
A worked case writes every input next to the arithmetic: watts, hours, loss, and reserve. Replace those inputs with the nameplate and the manual. Where a figure comes from a manufacturer, the guide names the manual and the edition. The sizing guide shows the pattern.
How test reports are read
Some guides discuss test reports that suppliers provide. Read each one for the model, the configuration, and the issuer. A report supports a claim when it covers the model and configuration in question, and the issuer can be confirmed independently. The method is described in how to check an equipment supplier’s test report.
Dates
SavvySkull pages do not display publication dates. When a page changes substantively, an update note on the page says what changed. Dates of historical events are stated as facts in the text of the page where they matter.
Images
Illustrations and diagrams are created to explain a point. Captions say illustration or diagram, and they name what the picture is for. Some images may be produced with AI image tools.
AI-assisted drafting
Drafts may be prepared with AI assistance. AI output is never treated as a source. Every factual statement must trace to a cited source, and the cited source is checked before publication. Tools can help with structure and wording. They do not decide what is true, and they do not replace the source check.
Review before publication
Before a guide goes live, DeltaSpark reviews it. The review checks that the short answer matches the body, that each claim names its source or the planning inputs on the page, and that any commercial relationship is labeled.
Bylines and reviewers
Guides carry the SavvySkull Editorial byline by default (see the byline page). A real author or a technical reviewer is named only when that person took part and their identity can be verified. The byline does not imply a team of any particular size.
Updates and corrections
When a guide changes substantively, we update it and add an update note that says what changed and why. Small fixes such as typos do not need a note. If a reader or an editor finds a factual error, we correct the page and note the correction on the page in an update note. To report a problem or suggest a better source, use the contact page.
Licensed historical material
Where historical material is republished under permission, it is logged item by item: the original URL, the rights holder, and the permitted use. Anything the permission does not cover is not reused. Historical context is kept on the historical blog reference, separate from current guides.
Commercial relationships
How ownership, sponsorship, affiliate links and supplied products are disclosed is described on the disclosures page. A disclosure does not change the source rules on this page: a claim from a sponsor is held to the same standard as any other.