// Electrical testing companies · Acceptance test reports
Acceptance test report packages, assembled from field sheets for your engineer to review and sign.
The gear is tested and the results are spread over a stack of sheets from two or three technicians. A free AI proof of concept has AI put copies of 20 to 30 closed projects back together as report packages, with readings as recorded and every missing sheet listed. Your reviewer, the person who knows these reports best, holds each draft against the package you issued.
- Closed report packages
- 20 to 30
- Readings judged
- None
- Signatures or seals added
- None
// The one job
From a stack of field sheets to a package ready for review
A project closes and someone in the office builds the report: a summary, the equipment and tag list, the test specification the job was written to, each device's sheet, the instruments used and their calibration dates, and the deficiencies found and what became of them. Along the way they chase the technician whose sheet never came in, and work out whether a blank means the test was skipped or was never in scope.
For the test, AI reads copies of those sheets and assembles the package: equipment and tag list, named test specification, readings by device as recorded, instrument calibration references, deficiencies noted, and the devices with no sheet. Every value keeps the page it came from. It decides nothing about a result, and your qualified engineer or technician reviews and signs.
for your qualified person
// What makes it hard
The owner's spec writes the report, and no two owners agree
The table of contents changes by owner. Western Michigan University's electrical testing section lists the pieces: project name, equipment tested, a checklist of visual and mechanical inspections, test values, a summary interpreting the results, infrared photos, the test equipment with calibration dates, and a line signed and dated by the firm's field superintendent that all required tests are done. Portland State's 2013 specification asks for nameplate data, a description of tests, and analysis and recommendations. Penn State's 2010 checklist wanted its own report forms in one named software format, with one electronic and four paper copies. The draft follows the layout your reviewer names for each owner.
Scope is set device by device. The University of Washington's August 2026 standard pulls in dry-type transformers from 167 kVA single-phase or 225 kVA three-phase, molded and insulated case breakers from 400 amps or with adjustable instantaneous trip, and motors from 10 hp. Penn State went down to individual 100 amp breakers, even on temporary power, and counted every NETA test marked optional unless waived in writing, where Maryland's standards leave most optional tests out. That same Washington standard still names NETA ATS-1999. So each draft records the spec section and edition, and lists a device with no sheet without assuming whether it was in scope.
A reading is never only a number. Western Michigan wants results corrected to 20 degrees C, with both the actual reading and the corrected value reported. Portland State's data records carry humidity, temperature, the technician, as-found and as-left results, and each instrument's traceable ID and calibration due date. Western Michigan caps analog field instruments at 6 months between calibrations and digital ones at 12, while Portland State allows 12 for both. The draft copies each reading with its unit, conditions and instrument, says so when a sheet shows only one of the two values, and lists any instrument with no date on file.
Deadlines stack up before the final binder. Portland State wanted preliminary data within 24 hours of finishing each apparatus and the full report within 15 business days. Washington wants handwritten results within a week and the engineer's results within seven working days, with two weeks for the owner's review before energizing, and says a test that turns up a problem is repeated until corrected and reported again in writing. Maryland asks for reports within five working days and, as each high voltage component finishes, a written statement of whether it is suitable to be energized. So one device can hold two sets of results, and the draft keeps both with their dates.
The signature is someone's license. Maryland wants a registered engineer's signature and seal on the first page of the report body, not on a cover, and a Remarks column saying whether each set of data is within accepted limits. Washington has a licensed engineer review and stamp the compiled report. Those calls stay with those people. Your reviewer will check that each reading sits on the right device and tag, that every deficiency on a sheet reached the deficiency list, and that each missing sheet is really missing. We describe public documents here, and none of it is legal or engineering advice.
// What you send
Closed projects and the packages that went out
20 to 30 closed projects
The field sheets for each project as they came in, with the report package you issued. Include one that shipped with a device missing and one an owner sent back.
Specs and owner formats
The testing section of each project's spec, plus any report form or layout an owner gave you. Note the edition of the test standard where you know it.
Instrument and deficiency records
Your instrument list with calibration dates for those jobs, and any deficiency log or retest sheets, handwritten or typed.
After the NDA, and only then
Customer names can be masked and nobody connects to your test-data software or instruments. If a job can't leave your office, we build look-alikes with your reviewer. Defense and aerospace projects stay out.
// Before it starts
Agreed before any field sheet is copied
Your owner puts these in writing first, since the reports go out under your firm's name.
- Your reviewer
- Named by the owner, usually the engineer or senior technician who signs reports
- Who signs
- Your qualified person, during the test and in the live month
- Success criteria
- Written first: readings placed, tags matched, deficiencies carried over, gaps listed
- Sample
- Picked by your reviewer across owners and equipment types
- Price
- Your range for the live job, given before the test
- NDA
- Signed before a single sheet moves
// How it gets judged
The package you issued, beside each draft
| On the same 20 to 30 projects | The package you issued | The AI draft |
|---|---|---|
| Equipment and tag list complete | Filled in from your projects | Filled in from your projects |
| Test specification and edition named | Filled in from your projects | Filled in from your projects |
| Readings placed on the right device, as recorded | Filled in from your projects | Filled in from your projects |
| As-found and as-left values kept apart | Filled in from your projects | Filled in from your projects |
| Instruments matched to calibration dates | Filled in from your projects | Filled in from your projects |
| Deficiencies carried onto the list | Filled in from your projects | Filled in from your projects |
| Devices with no sheet, named, with nothing filled in | Filled in from your projects | Filled in from your projects |
// After a yes
About 30 days on projects still in the field
If your reviewer says yes, new projects get the same assembly for about 30 days, while a technician can still go back for a missing sheet.
A qualified person reviews and signs every report, and no draft reaches an owner on its own.
Before you sign you'll have a fixed price for that job. Later jobs are priced one at a time, with monthly support after that.
// What could follow
Next, once report packages are running
- 01Next
Arc flash field data sheets
Technicians' sheets for a power system study read into device tables, for the engineer running the study.
- 02Then
Test scopes from a spec section
A project's testing section read into a list of equipment, tests, witness points and report deadlines for whoever prices it.
- 03After that
Maintenance report history by device
Several years of maintenance reports lined up by device for your engineer to read side by side.
// One hard limit
Readings and signatures stay with your people.
The proof of concept works only on copies. It never touches test equipment, your test-data software, a study model, a live report or a live site. It never says whether a reading is acceptable, never calculates incident energy, never sets a protective device and never signs or seals a report. A qualified person makes every technical judgment and signs every report.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
The range depends on how many projects you close in a month, how many owner formats you keep, and how many sheets a typical package holds.
// Questions
Questions from the report desk
Will the AI tell us whether a reading is within limits?
Does this need our test-data software?
What happens when an owner wants its own form?
Can it read handwritten sheets from the field?
Will it seal or certify a report?
Does this show that a job followed ANSI/NETA ATS?

Rob Eason, founder
// Book a proof of concept call
Bring the package that took longest to close.
Thirty minutes with Rob on your firm, your role and about how many reports you issue in a month. Nothing leaves your office until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
