30-min call with RobBook a proof-of-concept call
Job 02 · Maintenance records

// Elevator contractors · The other first job

Every unit's maintenance control program records, checked before the inspector asks.

Maintenance control program records, tested as a free AI proof of concept on copies of 20 to 30 unit files that have already been through an inspection. AI reads each unit's program and its records, checks them against the tasks and intervals the program calls for, and lists what is missing. Your reviewer, the maintenance superintendent who knows these files best, compares that list with what the inspector actually wrote.

Book a proof-of-concept call30 minutes with Rob
Unit files
20 to 30
Records signed by AI
None
Units cleared by AI
None

// The one job

The inspection is three weeks out. Someone has to open every binder.

An office tower's annual inspection is coming and each car has its own file. Were the monthly tasks initialed? Is the oil record current on the hydraulic? Did last winter's callbacks get a corrective action written down? Is the five-year test on file and the tag in the machine room, and can a mechanic actually find the wiring diagrams? Usually a superintendent answers those, or a route mechanic between calls.

In the proof of concept, AI reads copies of those records and drafts a check for each unit: every task and test the program calls for, the date it was last recorded, where the record sits, and what looks late or missing. It writes nothing into any record and makes no judgment about the equipment. Your reviewer sets the draft beside what the inspector found on that unit.

Unit binderCopies
Conveyance no.
Program on file
Last Category 1
Last Category 5
TaskIntervalInitials
Illustration, not one of your files
Checked against
the unit's program
Records checkDraft
Unit
Inspection date
Jurisdiction form
Gaps
ItemFound inStatus
Illustration, not a real check

// Where it gets hard

The program sets the intervals, and the inspector reads the binder

The intervals are each program's own. The Illinois State Fire Marshal, summarizing the 2007 edition of ASME A17.1/CSA B44, the Safety Code for Elevators and Escalators, lists what procedures and intervals rest on: the equipment's age, condition and wear, its design and quality, how hard it is used, its environment, improved technology, and the manufacturer's recommendations for SIL rated devices. A January 2025 Fairfax County round table for the industry made the point by setting a church used on Sundays beside a parking garage. So the draft reads each unit's interval from that unit's program and never assumes a house schedule.

Washington's forms show what a complete file holds. Its Elevator Program publishes separate sets for electric elevators (F621-122-000), hydraulic elevators (F621-123-000) and escalators and moving walks (F621-124-000). A documentation binder, kept on site permanently, holds as-built wiring diagrams, procedures for SIL rated devices and for anything specified under ASME A17.7/B44.7, the performance-based safety code, and written checkout procedures. Unit binders, kept five years, hold maintenance, code non-compliance, repair and replacement, acceptance test and callback records. On the monthly grid, the mechanic marks the month a task falls due, initials it when done, writes the interval in months, adds a next due date past 12 months and writes NA where a task doesn't apply. A due month with no initials is one gap, and a long interval with no next date is another.

Each kind of unit has records of its own. Hydraulic files add a record of oil usage and a checkout procedure for the overspeed valve, and the ASME A17.2 inspection guide, as reproduced in that round table, has the inspector look into unexplained fluid loss. Escalator grids run through step-to-skirt clearance, the step/skirt performance index, broken comb teeth and brakes. Washington's callback log wants the date, time, company or mechanic, the reported trouble and the corrective action, and the 2007 text counts trouble reported to elevator personnel by any means. The draft pairs each callback with its resolution and lists any left open.

Test records have their own owners and posting rules. Washington's Electric Elevator Periodic Test Record (F621-116-000) must be posted conspicuously in the machine room, calls testing the owner's responsibility and may stand in for a metal tag. New York City's posted ELV3 instructions describe that tag: test date, category, who ran the test and the agency's license number. Firefighters' service varies most. California's log is monthly and signed by a Certified Competent Conveyance Mechanic, with the CCCM number, the company's CQCC number and the fire key number, while Washington tests quarterly by authorized personnel and has fire alarm staff verify initiating and shunt trip devices yearly. The draft reports the cycle your jurisdiction's form sets and who signed.

Where records must live depends on the edition and the state. Illinois's summary of the 2007 text keeps maintenance records at a central location. The later text Fairfax presented has them viewable on site, with location instructions posted on the controller in characters at least 3 mm tall, and retained for the most recent five years. Mississippi wants records and programs available in the building for the life of the equipment. Washington has the contractor provide the forms and the owner leave them in the machine room unless its program approves otherwise. Your reviewer will check first: gaps the inspector also found, gaps the draft invented, units matched to the wrong program, and dates read from the wrong year. These are summaries of public pages read in November 2026, not legal or engineering advice.

// What you send

What the test needs from your maintenance side

20 to 30 unit files
Copies only
01

20 to 30 unit files

Copies of the program, the maintenance, callback and repair records, and the test records for units that have been through an inspection. Mix traction, hydraulic and escalator units, and include one you inherited.

02

What the inspector wrote

The inspection report for each of those units, and any note your superintendent made about what the inspector asked to see.

03

Your jurisdictions' forms

The state or city record forms your mechanics fill in, and your own program template if your company uses one.

04

NDA first, look-alikes if needed

Unit records show your customers' buildings and the condition of their equipment, so the NDA is signed before anything moves. Where an owner refuses copies, we rebuild the files as look-alikes with your reviewer.

// Before it starts

Written down before any binder is copied

The owner decides who judges the checks and which misses count most.

Records test termsOwner signs off
Reviewer
Named by the owner. Often the maintenance superintendent or whoever prepares units for inspection.
Success criteria
Written first, including how missed gaps and false gaps count
Records
Read from copies, never edited, initialed or signed by AI
Price
Given as a range for the live run, ahead of any copying
NDA
Signed before any binder or export moves

// How it's judged

Each unit's check beside what the inspector wrote

Unit by unit
Record by record
Same 20 to 30 unitsThe inspector and your teamThe proof of concept
Tasks due but not initialedFilled in from your unit filesFilled in from your unit files
Intervals read from that unit's own programFilled in from your unit filesFilled in from your unit files
Callbacks with no corrective action recordedFilled in from your unit filesFilled in from your unit files
Category 1 and Category 5 records found and datedFilled in from your unit filesFilled in from your unit files
Firefighters' service test cycle and signaturesFilled in from your unit filesFilled in from your unit files
On-site documents missing from the binderFilled in from your unit filesFilled in from your unit files
Gaps flagged that turned out to be wrongFilled in from your unit filesFilled in from your unit files
Nothing scored yet. These rows wait for your own unit files.Your reviewer marks each row against the agreed criteria.

// After a yes

About 30 days on units coming up for inspection

Once your reviewer says yes, the same job runs for about 30 days on units with an inspection ahead.

A person approves every check before it goes to a mechanic or a customer. A licensed person makes each entry and signature in the record, exactly as today, and a draft only points at what looks late or absent.

You see the live job's fixed price before signing. Any other job gets a price of its own, and monthly support starts once a job is live.

// After records

Jobs that could follow the records check

Ideas, ranked
Each after its own yes
  1. 01

    Violation repair proposals

    Inspectors' citations and your mechanics' notes drafted into a proposal, with each item's cure date on it.

    Next
  2. 02

    Inspection readiness by building

    A list by building and month of the units whose test, certificate or tag falls due, so your scheduler can book the inspector and the mechanic together.

    Then
  3. 03

    Callback patterns by unit

    A year of trouble calls sorted by unit and reported cause, for your superintendent to decide what deserves a closer look.

    After that

// One hard limit

It reads the records. It never signs one or clears a unit.

The proof of concept never touches your field service or accounting system or any live proposal or inspection record, and it never decides whether a unit is safe to run. It writes no task, initial or date into a record. A licensed person decides every repair and signs every record, and the code official has the last word on what passes.

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 we know how many units you maintain and how many jurisdictions set their own record forms.

// Questions

Program record questions from maintenance superintendents

Will the AI fill in or initial our maintenance records?
No. The proof of concept writes nothing into any maintenance record. It produces a separate check listing what looks late or missing, and a licensed person makes every entry and signature as they do now.
Can it tell us a unit will pass inspection?
No. The check says which records are present, which look late and which are missing. Whether a unit is safe to run, or passes, belongs to your licensed people and the code official.
Will you write our maintenance control program?
No. The test reads the maintenance control program you already keep for each unit and checks the records against it. Where a unit has no program on file, the draft says so, and writing one stays with your licensed people.
Our records are part paper binder and part field service app. What do you need?
Copies of both, in whatever form you keep them: scanned binders and exports from the app. The test never logs in to your field service system, and a fair sample includes the untidy units.
We took over units from another company and the records are thin. Should those go in?
Yes, include a few inherited units. Thin files are where gaps hide, and your reviewer can judge whether the draft listed what was really missing. A gap stays a gap on the draft, never a guessed date.
How do you know what the check should have caught?
The inspector's report on each unit is the yardstick, along with any notes your team kept on what an official asked to see. Your reviewer scores the draft's gaps against those, and against units that came through clean.
Rob Eason

Rob Eason, founder

// Book a proof-of-concept call

Bring the binders from your last inspection season.

Thirty minutes with Rob about your company, your role, the job to start with and roughly how many units you maintain. Keep binders and exports 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.