TRG Report Template
This template for Overall Equipment Effectiveness (OEE) is designed for machine operators and quality managers to identify key losses during daily manufacturing operations. Utilize this comprehensive OEE report template to document any instances of unplanned downtime, planned downtime, minor stoppages, slow cycles, production rejects, and startup losses.
Use this template with flowdit
- Customize this template or build your own
- Complete inspections using the mobile app
- Get reports and analyze your data
Start inspecting smarter — free for one user.
How to Use This Checklist
- Set the context. Record the conducted on, prepared by, and location details, and capture the inspection real start date, so the report has a clear point of reference.
- Work through each cause section in turn: unplanned downtime, planned downtime, minor stoppages, slow cycles, production rejects, and startup rejects. Answer Yes or No for each question, in the order that suits your shift.
- Record everything, not just the largest event. Minor stoppages described in the template, such as brief periods of slowdown, add up over a shift, so capture them as they happen.
- Sign off and close out. Complete the signature, finished at, and inspection real end date fields so the report is traceable and comparable against other shifts.
Start inspecting smarter — free for one user.
What OEE reporting is
Overall Equipment Effectiveness (OEE) reporting is the practice of recording the losses that stand between the equipment's theoretical capacity and what it actually produced during a given period. Rather than measuring output alone, it forces attention onto the reasons output fell short. This template supports that work by breaking the causes down into six sections, each covering a distinct category of loss: - **Unplanned downtime** - equipment failures, malfunctions, unplanned repairs, material shortages, an absence of transport for finished goods, and operator unavailability. - **Planned downtime** - equipment setup duration and lengthy changeovers. - **Minor stoppages** - brief periods of slowdown and incorrect operations performed on the equipment. - **Slow cycles** - lack of maintenance, noticeable equipment wear, and improper settings such as running speed slower than necessary. - **Production rejects** - products that cannot be salvaged at all, and products that needed reworking to be usable. - **Startup rejects** - losses during production ramp-up. The questions are answered on a simple Yes or No basis. A 'Yes' identifies a loss that occurred; a 'No' shows the category was clean for that period. In total the template carries 22 items, covering both the six loss sections and the reporting and sign-off fields.
Why it matters
Equipment losses hide in plain sight. A machine that runs all shift can still lose a large portion of its capacity to changeovers that run long, brief stoppages that nobody records, or settings that hold it below its capable speed. When those losses go undocumented, the same problem repeats the following shift, and the following week. Recording them gives you the evidence to act on. A pattern of frequent long changeovers points to a setup problem; repeated equipment wear or a lack of maintenance points to the maintenance schedule; recurring rework points to a process or quality issue. The value is not in the record itself but in the decisions it supports - where to direct maintenance effort, which changeover to tackle first, and which stoppages are worth engineering out. The template also makes records comparable. Because every section uses the same Yes or No scale and covers the same categories, reports from different operators, machines, or shifts can be set side by side and read in the same terms.
What a good report covers
A useful OEE report is complete, specific, and comparable. - **Complete.** Every loss category is reviewed, not just the main one. Leaving minor stoppages or slow cycles unrecorded flatters the numbers and hides where the real capacity sits. - **Specific.** The template's questions distinguish between causes that look similar but require different responses. Unplanned repairs, insufficient maintenance, and noticeable equipment wear are separate items because each points to a different action. - **Attributed to a time and a place.** The conducted on, location, and prepared by fields in the header, and the finished at field in the sign-off, position the record in context. Without them, a report cannot be compared with the one before it. - **Signed off.** The signature field confirms that the report has been reviewed and accepted, which matters when the record is used to justify maintenance, process change, or investment. - **Honest about rejects.** The template separates products that cannot be salvaged at all from those that needed reworking. Both are losses, but they carry different costs, so they are recorded separately.
How to run it well
Carry out the report close to the work. The closer the record is made to the event, the more reliable it is - a stoppage noted at the time it happens is worth more than one recalled at the end of the week. Work through the sections in the order that matches how your shift actually ran, or in the order they appear in the template if you prefer consistency. When a question is answered 'Yes', the loss occurred; the template is designed to capture that fact simply, so record it and move on rather than debating borderline cases mid-shift. Involve the people closest to the machine. Machine operators see minor stoppages and brief slowdowns that quality managers may never learn about otherwise, and quality managers bring the perspective to judge which losses matter most. The template is written for both. Use the sign-off fields honestly. The finished at, inspection real start date, and inspection real end date fields record the actual timing of the inspection, not its scheduled timing. Actual timing is what makes trends visible over time. Finally, treat the completed reports as a series rather than one-off documents. A single report tells you what happened in one period; a stack of consistent reports tells you what keeps happening, which is far more useful for improvement.
Frequently Asked Questions
Ready to simplify inspections and get your team moving faster?
Start free today and turn inspections into a clear, consistent digital workflow. Prefer a guided walkthrough? Book a demo and see how flowdit can fit your team.