First Pass Yield Daily Tracking Form

This template records daily production counts, first-time-right units, scrap, and rework so you can calculate first pass yield by line and shift. It also captures whether yield fell below target and whether there has been a consecutive drop that needs review. Use it when you want a simple, repeatable quality log instead of ad-hoc notes or spreadsheet comments.

A shift supervisor, line lead, or quality technician usually completes it at the end of each shift or production day. The person entering the form should have access to the actual counts and know whether an issue was observed on the floor. If your process uses a separate quality owner, the form can still be submitted by operations and routed for review.

This template is designed for daily use, with one entry per line and shift. If your operation runs multiple shifts, create a separate submission for each shift so yield trends are easier to compare. For high-volume or unstable processes, some teams also review the data mid-shift, but the form itself should still capture a clean end-of-shift record.

The production date, line, shift, total units produced, first-time-right units, and target yield should be required because they are needed to calculate and interpret yield. Scrap, rework, issue summary, and root cause category can be required only when yield falls below target or a drop is flagged, using conditional logic. That keeps the form aligned with data minimization and avoids forcing unnecessary detail on stable shifts.

The consecutive shift drop field helps identify patterns that a single daily total can hide. When yield falls below target more than once, the form creates a clear trigger for review, root cause classification, and follow-up ownership. That makes it easier to separate one-off events from process problems that need corrective action.

Yes. You can use a line dropdown, shift dropdown, and conditional logic to match your plant structure without changing the core yield calculation. Many teams also add product SKU, work cell, or machine ID if those details are needed to explain variation. Keep the form focused on the fields you will actually use in review meetings.

First pass yield should be calculated from first-time-right units divided by total units produced, with the result displayed as a percentage. The form should not rely on free-text math entered by the user when a calculated field can do the work. If scrap and rework are tracked separately, make sure the logic is consistent so the same unit is not counted twice.

Common mistakes include mixing shift-level and daily totals in the same entry, leaving the target yield blank, and entering counts that do not reconcile. Another frequent issue is collecting too much narrative detail on every submission instead of using progressive disclosure only when yield drops. The form works best when it stays short on good days and expands only when review is needed.

A spreadsheet can store the numbers, but this template adds structure, validation, and a clear review path. It reduces inconsistent field names, missing context, and manual follow-up because the same fields appear every time. If you need an audit trail for quality review, a form is usually easier to standardize than free-form spreadsheet entries.