ProcirelOur one non-negotiable
When speed and accuracy conflict, accuracy wins. Every time. A tutorial that ships a week late with verified numbers is worth more than one that ships today with guesses. That single rule explains most of how this site works, so this page documents it in full, policies, workflows, and the trade-offs we accept.
Why we picked this fight
Electronics content has a peculiar failure mode: wrong information does not look wrong. A tutorial with a transistor base resistor sized carelessly reads exactly like a correct one right up until the reader’s component runs hot. A “5 V regulator circuit” with a misread datasheet pinout assembles cleanly on a breadboard and then dies quietly in a product. The reader has no way to smell the difference, which is precisely why the writer has to care.
Most of the mistakes we have made on the bench, and every mistake we have published and later fixed, traces to one of three shortcuts: trusting a forum post over a datasheet, estimating a number instead of measuring it, or copying a value between projects without re-checking its conditions. Our priority policy exists to make those three shortcuts structurally difficult.
The five-part verification workflow
1. Datasheet verification, every time
Every formula, rating, pinout and part number is checked against the manufacturer’s datasheet before publication, not from memory and not from another tutorial. Datasheets are the contract between us and reality, and we read the fine print: footnotes, test conditions, and the difference between typical and maximum ratings. A regulator’s dropout voltage quoted from its “typ” column will fail the worst-case unit eventually, so we design against the max column and say so.
2. Measured values, with conditions stated
Numbers in our worked examples come from instruments: multimeters, oscilloscopes and analysers used during the actual build. We state the conditions, supply voltage, load, temperature, frequency, because a number without its conditions is a rumour. When a reader reproduces our setup, they should land within rounding of our result. If they do not, we want to hear about it, and several corrections on this site began exactly that way.
3. Technical review of safety-relevant content
Anything touching mains voltage, lithium batteries or high current passes a second review focused purely on safety accuracy: isolation distances, fuse ratings, discharge paths, and the explicit warnings a beginner needs before they touch 230 V. We would rather over-warn than under-warn, and our mains content carries precautions in the text, not buried in a footnote.
4. Scheduled re-verification
Guides covering prices, tool availability, component sourcing or software versions are revisited on a rolling schedule. A 2024 tutorial about a bench supply that is no longer sold is a broken tutorial no matter how correct its electronics remain. Each refreshed guide carries an updated review date, so you can see how fresh your information is.
5. Corrections in public
When we get something wrong, the fix ships with a date, and where the error was consequential we note what changed. Silent rewrites are a small dishonesty that compounds; public corrections cost a little pride and buy something better, a record you can trust. Reader reports are credited by name unless the reporter prefers otherwise.
What we will not do
The honest trade-offs
Accuracy-first has costs and we accept them knowingly. We publish fewer tutorials than a content farm would. Our guides are longer, because conditions and failure modes take words. Some topics wait months until we can buy the parts and bench them properly. And occasionally a reader wants a quick answer we refuse to compress past the point of honesty.
We think that trade is correct for electronics specifically, where the reader’s hardware, time and occasionally fingers are on the line. If you ever find a number on this site that does not survive contact with your multimeter, tell us via the contact page. Finding our errors is not an embarrassment to us; shipping them quietly would be.
> See also: Why Choose Procirel, What Sets Us Apart, and the editorial team and review process.
Frequently asked questions about our standards
How fast do you correct errors?
Verified corrections ship within days. The contact page reaches the author directly; every message is read.
Do you accept guest posts or sponsored tutorials?
No. Every guide is bench-built in-house. Sponsored content would break the exact promise this page documents.
What happens when a component in an old guide becomes unavailable?
We re-verify the guide with a current equivalent, update the parts list, and refresh the review date. The electronics stays; the sourcing catches up.
Have you actually published corrections?
Yes, several, each dated and credited to the reader who reported it. The list grows, and that is the policy working, not failing.
Why not just test in simulation?
Simulation verifies intent; the bench verifies reality. Stray capacitance, contact resistance and component tolerance live only on the bench, and they are where beginners actually get stuck.
How do you treat mains-voltage content?
With extra review and explicit precautions in the text. Some experiments we deliberately do not simplify for beginners, because 230 V does not grade on a curve.
The metric we watch
Not pageviews per tutorial. Reproduction rate, the share of readers who report building the project successfully. A guide that gets built beats a guide that gets clicked.