30-min call with RobBook a proof-of-concept call
Job 02 · Service desk

// Generator dealers · Compliance files

A customer's annual generator compliance file, assembled from your service records for your service manager.

When a service year closes, a hospital, a water system or a property manager wants the record: weekly and monthly run logs, load bank or exercise test reports, fuel tests and transfer switch tests. Someone on your service desk builds that file from tickets, log sheets and lab reports, and works out what is missing. A free AI proof of concept does the same building on copies of 20 to 30 files you already sent. Each draft shows the records it found by date and the ones it could not find. Your reviewer, the service lead who knows these files best, sets every draft beside the file that actually went out.

Book a proof-of-concept call30 minutes with Rob
Past files
20 to 30
Test results judged by AI
None
Reports signed
None

// The one job

From a year of scattered records to one file per generator

A commercial customer's generator year leaves paper in several places: weekly inspection sheets, monthly exercise logs, a load bank or annual exercise report, fuel samples at a lab, transfer switch test sheets, repair tickets and notes on anything found wrong. Your service manager turns that into one file for each site and generator, and sends it to the customer.

For the test, AI reads the same records and drafts the annual file: what was done, on which date, by whom and which document shows it, followed by the dates and records still missing. It judges no test result, changes no record, signs nothing and sends nothing. Your service manager reviews the file and decides what goes out.

Service recordsOne generator, one year
Site and unit
Hour meter
Run logs
Test reports
RecordDateSource
Illustration, not a real record
Assembled for
your service manager
Annual fileDraft
Weekly and monthly
Load bank or exercise
Fuel test
Transfer switches
RequirementFound inMissing
Made-up file, for illustration

// What makes it hard

One generator, several agencies, and no single retention period

A single year runs on several clocks. Minnesota's Department of Health, in guidance revised in June 2024, has health care facilities inspect generators weekly, exercise them under load at least monthly and, under NFPA 99, test them 12 times a year at intervals of 20 to 40 days. Transfer switches are operated monthly. Main and feed breakers on Level 1 systems are exercised annually, and those above 600 volts every six months, with a simulated overload test every two years. A Level 1 system also gets a test within every 36 months, continuous for the generator's assigned class but not required past four hours. The draft places each record on that calendar, generator by generator, and names any interval it can't show.

The monthly line is a form, not a checkmark. Minnesota's list covers the generator's identity, install date, standby nameplate kW, fuel type, test date and initials, the transfer switch used to start the test and its transfer time, cooldown, elapsed run time backed by hour meter start and stop readings, oil pressure, operating temperature, the kW under test, and any problem with its fix and the parts replaced. Warm-up and cool-down don't count toward the minimum run. Kansas's State Fire Marshal prints an operating log that adds jacket water temperature, battery amperes, volts and amps on each phase, frequency and restoration of service in seconds, and says a site short of the minimum load has to document everything connected to the generator and the total load carried. The draft fills each field from the log, notes any field left blank, and doesn't interpret a reading.

A load bank report has to say which test it was. Kansas describes the annual diesel load bank run as two hours in three steps, conducted by a generator contractor, and its reference line points to NFPA 110's 2005 edition. Minnesota, citing the 2010 edition, states a supplemental annual run of one and a half continuous hours. A 2022 article in Health Facilities Management notes the standard is referenced by CMS K-tag K918 and Joint Commission Standard EC.02.05.07, and says a combined annual load bank and 36-month test should be labeled as combined and cite NFPA 110-2010, Section 8.4.9.7. So the draft records the edition, the steps and the load values as the report shows them, and leaves the limit in the document that sets it. Whether the test met it is your service manager's call and the customer's.

Fuel and air records answer to other people. The Accreditation Commission for Health Care's 2023 checklist says a fuel quality test must happen at least annually, using tests approved under ASTM D 975, and a federal survey from June 2023, posted by Indiana's health department, cited one site for no annual fuel quality test on three diesel generators and for no documented 36-month test on two. EPA's rules want hours from a non-resettable meter split between emergency and other running (40 CFR 63.6655(f)), the time and reason of each run (60.4214(b)), and maintenance checks and readiness testing kept to a maximum of 100 hours per calendar year (63.6640(f)). For an existing emergency diesel at an area source, meaning construction began before June 12, 2006, Table 2d of Subpart ZZZZ sets oil and filter and hose and belt checks every 500 hours or within a year and 30 days, and the air cleaner every 1,000 hours. A 2007 New Jersey advisory has logs for generators above 37 kW show each test run's reason and operator, and bars routine testing when poor air quality is predicted. The draft sets out hours, runs and service dates for your reviewer and doesn't decide which rule applies.

How long a file lives depends on who is asking, and your reviewer watches the rest. Minnesota recommends keeping logs at least three years. Virginia's emergency generator general permit wants records current for the most recent five years, covering rolling 12-month hours, fuel supplier certifications, each unit's make, model, serial number and model year, and maintenance, testing and training. Texas tells small water systems to keep completed checklists for the life of the generator. Your reviewer checks that every record lands on the right site, generator and date, that each gap is named, that load values are copied and never rounded, that a report's edition and steps are shown, and that no line says a test passed. Rules differ by site and jurisdiction, and nothing here is legal, regulatory or engineering advice.

// What you send

Annual files your service desk already closed

Copies only
Closed service years
01

20 to 30 annual files

Files your desk already sent, each for one customer site and service year. Include one that needed fixing after it went out and one with a gap you had to explain.

02

The records behind them

Weekly and monthly logs, load bank or exercise reports, fuel lab results, transfer switch test sheets and repair tickets for those years, as you really keep them, paper included.

03

What each customer asked for

The list or letter a hospital, water system or property manager gave you, and any rule or permit page your team works from.

04

NDA first, copies only

The NDA is signed before anything moves. Customer and site names can be masked. No one here logs in to your service system, a remote monitoring site or a generator controller, and if records must stay on site, your reviewer helps us build look-alikes.

// Before it starts

Settled before the first log is copied

The owner writes these down before any file moves.

Compliance file test termsOwner signs off
Your reviewer
Named by the owner, most often the service manager or service coordinator
Success criteria
In writing: which records must be found, and how a missed gap counts
Files
Your reviewer's pick, across the kinds of customer you serve
Test results
Read by your people, never judged by the draft
Price
A range for the live job, settled in advance
NDA
Signed first

// How the test is judged

The file your desk sent, beside each draft

Generator by generator
Date by date
On the same 20 to 30 filesThe file your desk sentThe AI draft
Site, generator and service year on every recordFilled in from your filesFilled in from your files
Weekly and monthly runs placed on the right datesFilled in from your filesFilled in from your files
Load bank or exercise report, with steps and load values as writtenFilled in from your filesFilled in from your files
Fuel test date and lab reportFilled in from your filesFilled in from your files
Transfer switch tests, by switch and dateFilled in from your filesFilled in from your files
Missing dates and records, listed by generatorFilled in from your filesFilled in from your files
Any draft line that claims a test passed, flagged as a faultFilled in from your filesFilled in from your files
No marks yet. Cells stay empty until your own files have gone through.Each row's verdict comes from your reviewer.

// After a yes

About 30 days on the next files due

After your reviewer's yes, the next annual files that come due get the same drafting for about 30 days.

Your service manager reviews every file and sends it, and anything still missing goes to your service desk to find. The side-by-side comparison keeps running on live files, and anything further is a new decision with its own price.

// Later, one at a time

What could follow the compliance file

Ideas, ranked
Priced one by one
  1. 01

    Specification section quotes

    A project's generator section and electrical schedule read into a draft quote sheet for your sales engineer.

    Next
  2. 02

    Due lists for the next service year

    Each generator's next weekly, monthly, annual and 36-month dates drafted from the file, for your dispatcher to schedule.

    Then
  3. 03

    Repair quotes from service findings

    Problems noted on logs and reports drafted into a repair quote for your service manager to price and send.

    After that

// One hard limit

It never judges a test result and never signs a report.

The draft lists what the records show and what they don't. It never judges a test result, decides whether a site complies, sizes a generator or signs a report, and it never touches your service system, a generator controller, a live quote or a live compliance file. Your service manager reviews and sends every file. Rules differ by site and jurisdiction, and this page isn't legal, regulatory or engineering advice. Out of scope: defense and aerospace.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

The range comes on the call, once Rob knows how many customer sites you keep files for and how many generators are on them.

// Questions

Compliance file questions from service managers

Will it tell us whether a load bank test passed?
No. It copies what the report shows and names the document behind it. Whether a test met its limit is a call for your technician, your service manager and the customer.
Our records live in a service system, in log books and in customers' binders. What do you need?
Copies of whichever of those your team really used. A photographed weekly log and an exported ticket are both fine, and the draft marks where each record came from so your reviewer can check it.
Can it cover weekly logs that the customer's own staff keep?
Yes, when those logs reach you for the file. Where they don't, the draft lists them as missing and doesn't treat a service visit as proof of a weekly check.
Does it send anything to a surveyor, an inspector or an air agency?
No. Nothing leaves your office through the test. Your service manager sends the file to the customer, and anything filed with an agency stays with the customer or your team.
Our customers follow different editions of NFPA 110 and different state rules. How is that handled?
Each file follows the checklist your team already uses for that customer. The draft says which checklist it used and which edition a report cites, and your reviewer confirms it. It doesn't decide which edition applies.
Who fills the gaps it finds?
Your service desk. The draft shows the generator, the date and the record it couldn't find, and someone on your team tracks it down or notes why it doesn't exist. The draft never fills in a number.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Bring last year's files, gaps included.

Thirty minutes with Rob, covering your territory, your role, the job you'd test and roughly how many customer sites you keep files for. Logs, test reports and customer names stay with you 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.