Garage door safety-check records: reversal tests, photo eyes, springs.

A garage door job is finished when the technician has checked the opener's entrapment protection and written the result down. A per-job safety-check record covers the reversal test, the photo eyes or edge sensor, the warning label near the wall control, and the spring that was fitted, and the technician signs it.

An AI assistant can pre-fill that record, chase the ones left incomplete, check each file for gaps, and draft a care note that mirrors the US Consumer Product Safety Commission's advice to test the reversing feature monthly. It never performs, judges or signs the test.

As checked on 13 October 2026, a US Consumer Product Safety Commission news release dated December 1992 announced final rules for automatic residential garage door openers manufactured on or after 1 January 1993 for sale in the United States. Each opener must use either an external entrapment protection device, such as a photo eye or a door edge sensor, or a wall-mounted constant-contact control, and new openers must carry a warning label near the wall-mounted control.

The rules sit in 16 CFR part 1211, the Safety Standard for Automatic Residential Garage Door Operators. Section 1211.6 requires built-in entrapment protection on every operator and, for vertically moving doors, one of several further protections, such as a constant-pressure close control or a connection point for an external secondary device. Section 1211.5 sets testing parameters that refer to Supplement SA of UL 325-2017.

Those rules govern how openers are built. The reversal test a technician runs before leaving is trade practice rather than a quoted legal requirement, and it is the moment the business confirms that the protection works on this door, today, before handing it back to the homeowner.

This is the record Aevrion uses as a starting point. The owner adapts it to the doors and openers the business works on, and the technician agrees every field before it is used.

A 'no' in the reversal field is not a paperwork problem. It goes to the owner at once, and the technician decides what happens to the door.

The records assistant is one of the account's Bots in Grok Bot. It has a name, the single job of keeping safety records, and a chat of its own, and it works on the account's cloud computer, where it can browse and keep files. From the work order it pre-fills the fields it is allowed to and lays out the blank record as a document or a column-by-column spreadsheet for the technician. The instruction 'never complete a test field' is one of its lasting rules, but a remembered rule steers the Bot rather than enforcing anything, so the procedure also has a person check that no test field was touched.

The limits are firm. A Bot does not inspect a door, interpret a test or sign a record; the technician does all three. There is no telephony in Grok Bot, no calls and no texts, and no connector is named for field-service software, so reaching the job system is a custom integration or supervised browser use where the vendor permits it, subject to testing, with logins and two-factor checks handed to a person.

Based on the Grok Bot documentation at docs.x.ai as checked on 13 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

A photo of the spring after fitting, and one of the photo eyes or edge sensor after the test, give the record something to point to. Bots accept image attachments alongside documents and spreadsheets, so the photos sit in the same file as the record.

On an iPhone, the technician can share a photo from the share sheet straight into the records Bot's chat. On Android, the share sheet currently accepts text only, so photos are added later from the desktop app. Either way the photo is attached to the record as evidence; the Bot does not read a pass or a fail from it.

The same CPSC release gives consumers simple advice: test the reversing feature following the manufacturer's instructions, then retest it monthly; if the door does not reverse, adjust it according to the owner's manual or have a professional inspect it; and keep remotes and transmitters out of children's reach. A care note that mirrors that advice, with the business's details, is a natural end to every job.

The assistant drafts the note from the owner's approved template and the job record. In the Grok Bot documentation an email draft is an editable card that leaves only if the user presses send, so the owner reviews and sends. The note can add that springs are not a homeowner job, in line with the DASMA-published advice to have such repairs done by a trained door systems technician. It does not say the door is safe, and it does not diagnose anything.

A weekly routine can read the week's jobs and list every record missing a field, a signature or a care note. A routine can run no more often than every five minutes, which a weekly check never approaches, and the last 20 runs stay on record, enough to show which recent weeks the check actually ran.

The output is a list for the technician, not a corrected file. If a reversal field is blank, the routine says so; it does not infer the answer from a photo or from a previous visit. Memory is not the record either, as the Grok Bot documentation warns, so the record lives in the business's own job system and the routine reads it from there every time.

If the technician uses the owner's account, the records Bot and every other Bot share the job-system login, so a technician who should not see invoices needs a separate user account. The job system's session sits on the one computer all the Bots use, and separate Bots are not a security boundary.

Approvals do not change that picture much. Where a step in the records workflow is set to pause, the card shows Allow once, Always allow and Deny, and which steps pause is up to the tool, its risk and the owner's rules. A request raised by the weekly routine lapses after about ten minutes (Cursor's help pages say thirty) with nothing done, and approving never undoes a change already made. That is why the weekly check prepares lists and drafts rather than sending anything.

Write the record first, with the owner and the technician agreeing every field, then let an assistant pre-fill it and run the weekly check on read-and-prepare work. Add the care-note draft once the record is reliable. The garage door overview page explains how this sits beside the sales-side pages, and the owner-operator office article in this series shows the records desk on a busy weekend. For the sales side, the lead-flow checklist covers inquiry to outcome.

Aevrion Ops can help garage door companies write the record, set the rules and build the integration with their job system, provided the job system's API or terms allow it and it passes testing. The workflow automation readiness assessment is a good first step.

1. US opener rules in 16 CFR part 1211 put entrapment protection at the center of every garage door job.
2. A per-job record covers the reversal test, sensor alignment, the warning label and the spring size and cycle rating, and the technician signs it.
3. An assistant pre-fills, chases and checks the record; it never performs, judges or signs a safety test.
4. The customer care note mirrors CPSC's advice to test the reversing feature monthly, and a person sends it.
5. A weekly routine returns gaps to the technician rather than filling them, and reads records from the job system each time.