How this site's content gets made, labelled, reviewed and corrected — and who is accountable when it is wrong. Published because you should be able to check our work, not because a policy required it.
ElectricalDocs is accountable for what it publishes. Pages that touch regulation, electrical practice, code, calculators, or exam preparation carry a review record and are checked by a qualified reviewer before publication:
Published by ElectricalDocs. The responsible reviewer is recorded in the internal editorial record for each technical page.
Software may assist with research, consistency checks, formatting, and calculations. It is not the accountable reviewer and does not decide whether a technical page is ready to publish or retire.
We source in this order, and we say which one we used:
| Priority | Source type | Examples |
|---|---|---|
| 1 | Primary and governing | The adopted code itself, state statute and administrative code (RCW, WAC), the AHJ's own published requirements |
| 2 | Primary, non-governing | Utility tariffs and rebate program documents, manufacturer specifications and installation instructions, state agency guidance |
| 3 | Field experience | Work Elevated Systems has actually performed, permitted and inspected |
| 4 | Secondary | Trade publications and industry commentary — used for orientation, never as the basis of a code claim |
A code-related claim is never sourced from a secondary source alone. General-purpose web results and search-engine summaries are not sources; they are, at best, a pointer to one. In our experience they are frequently out of date on code editions.
A code claim without an edition and a jurisdiction is not a usable claim. So every code-adjacent statement on this site carries:
Article numbers move between editions. Washington amends the model code. Local AHJs amend further. If you are outside Washington, or working under a different adopted edition, assume our numbering does not transfer and verify against your own adopted code.
The National Electrical Code is a copyrighted standard published by the National Fire Protection Association. We cite article and section numbers and explain them in our own words. We do not reproduce code text. Where you need the exact language — and for anything you are going to build, permit, or sign, you do — go to the code itself.
We use AI tools to help draft, structure, edit and check content on this site. We are telling you because you deserve to know, and because a lot of sites in this trade are not telling you.
What AI does here: drafting and restructuring prose, checking internal consistency, catching omissions, and formatting.
What AI never does here: originate an electrical or code claim that a qualified human has not verified against a primary source; act as the responsible expert; decide whether a page is accurate; or generate a calculation result that is presented as authoritative.
Every technical assertion is reviewed by the responsible reviewer before it publishes. If a page is wrong, that is a human failure and we own it as one — "the AI wrote it" is not an explanation we will ever offer you.
Where this site shows a worked example, the arithmetic is produced by the same calculation code that powers our tools — not re-typed by hand into the page and not estimated in prose. Duplicated arithmetic drifts from the tool it claims to mirror, and a page that looks authoritative while being wrong is worse than no page. Examples are re-verified whenever the underlying calculation changes.
Pages are not published and forgotten. Each carries a review interval and a condition that makes it stale:
| Content class | Reviewed |
|---|---|
| Regulatory / code content | Every 6 months, and on any amendment |
| Calculator explanatory content | Annually, and whenever the calculation changes |
| Exam-preparation material | Annually, and on any code-cycle adoption |
| Company and service pages | Annually, and on any change to our contact details |
| Commentary | Every 2 years, then kept, merged, or retired |
Expiry is a condition, not a date. A page about a 2029 requirement is not stale in 2027 because time passed — it is stale the moment the requirement is amended. We write our expiry rules that way.
When we get something wrong:
Report an error to admin@elevatedsystems.net. Corrections from readers who work in the field are the most useful mail we get.
Content that has stopped being true gets retired rather than left to rot. Depending on the case we will remove it from search while leaving it reachable, merge it into the stronger page on the same subject, or remove it and redirect to the nearest genuinely relevant page. We do not delete a published address into a dead end.
ElectricalDocs is published by a company that also performs electrical work, and this site exists partly to introduce you to what it does. That is a commercial interest and we are not going to pretend otherwise. What it does not do is change a technical answer: we do not adjust code guidance, calculator behaviour, or a recommendation because a particular answer would sell more work. Where we mention a product, a rebate program, or a manufacturer, we are not paid to do so, and we will disclose it plainly if that ever changes.
Elevated Systems LLC · Bonney Lake, Washington · admin@elevatedsystems.net · (253) 285-7421