Generator Monthly Load Test Log

It covers the monthly inspection and test record for an emergency generator, including load testing, automatic transfer switch verification, fuel and fluid checks, fault code review, and post-test documentation. The template is meant to capture what was tested, who ran it, what passed, and what needs follow-up. It is a log and checklist in one, so you can track both execution and results.

This template is designed for monthly recurrence. If your site policy, insurer, or maintenance contract requires a different cadence, you can adjust the recurrence while keeping the same checklist items. Many teams also use it after repairs, fuel deliveries, or utility events as an extra verification step.

A qualified facilities technician, maintenance lead, or electrical contractor should run it, depending on your site rules and local requirements. The DRI should be someone who can verify the generator, ATS, and any follow-up actions without handoff gaps. If the test involves critical systems, assign a backup reviewer for documentation and escalation.

It supports both. The checklist pattern aligns well with OSHA-style inspection discipline and with ITIL-style runbook documentation for critical infrastructure, but it does not replace any local code, manufacturer guidance, or formal inspection requirement. Use it as the operational record that shows the test was completed and any defects were tracked.

The biggest mistake is treating the test as a pass/fail note without recording the actual verification steps, fault codes, and follow-up actions. Another common issue is using compound checklist items that hide partial failures, such as combining fuel, oil, and coolant checks into one line. Teams also forget to document blocking issues separately from non-blocking observations.

Yes. Add model-specific checks such as battery charger status, block heater status, exhaust condition, or remote monitoring alerts if your equipment requires them. Keep each checklist item independently verifiable with a yes, no, or N/A answer so the log stays easy to review and audit.

An ad-hoc note usually records only that someone looked at the generator, which makes it hard to prove the load test actually happened. This template structures the work into clear checklist items, a defined recurrence, and a documented outcome, so the record is easier to review, trend, and hand off. It also reduces missed steps when multiple people share responsibility.

Yes. It pairs well with preventive maintenance schedules, corrective maintenance tickets, fuel delivery logs, and incident follow-up tasks. If your workflow tool supports links or references, connect this log to the generator asset record, the ATS asset record, and any open repair task so the next reviewer can see the full context.