8D Gate

Launch · Excel

First piece inspection log: free Excel

One row per characteristic measured on a first piece: part, line or machine, what triggered the check, who checked it and when, your own lower and upper limits, the measured value, and the run decision with who made it and when. Values outside your limits are flagged, and a released run with any value outside your limits gets its own status.

Free, no card. Enter your email to get the Excel file.

Get the free first piece inspection log

We store your email to give you what you asked for. If you tick the box, we may also email you about new tools. We never sell your data. Privacy · To delete it, email 8dgate@agent.mailboxkit.com

Own structure and wording. Tested in LibreOffice. Advisory only.

Your characteristics and limits, not ours

  • Characteristics, limits, units and when a first piece is needed come from your drawing, control plan or customer. The file quotes no limits or values from any standard or customer and fills in none for you.
  • A logged first piece records what was measured on that part on that date. It says nothing about the parts made after it.
  • First piece and first article are not the same thing here: this log is for the routine check at a setup, tool change or shift start. For a full first article report, see the first article inspection report template.

What is in the file

  • Settings: an as-of date (blank means today).
  • Log, one row per characteristic: FPI ID, part number, revision (if any), line or machine, trigger, checked on, checked by, characteristic, lower limit and upper limit (yours), measured value, gauge or method, run decision, decision by, decision on, notes.
  • Within your limits: Yes, No, or blank when a number is missing, worked out from your limits and the measured value. A value equal to a limit counts as within.
  • A separate check column. The status does not hide it, a filled date or number is checked for the cases listed below, and a row can show several notes, joined with a semicolon.
  • Counts under the log: rows logged, rows per status, rows with a check note, rows outside your limits, a line that should read 0 (rows not in any status), rows per trigger and rows per run decision. No score and no ranking.

How the status is worked out

In this order; the first match wins. Text typed in a date or number cell counts as blank:

StatusWhen
Enter FPI IDThe row has an entry but no FPI ID. It still counts.
Enter part number, Enter line or machineIn that order. Revision is optional.
Enter triggerBlank, or typed outside the list (New setup, Tool change, Shift start, Material lot change, After repair, Other).
Enter checked-on date, Enter checked byDate (blank or text counts as blank), then the name.
Enter characteristicCharacteristic blank.
Enter a lower or upper limit (yours)Neither limit is a number. One limit is enough for a one-sided limit. The limits are your own; the file fills in none.
Enter measured valueBlank, or text instead of a number.
Enter run decisionBlank, or typed outside the list (Released to run, Held, Not decided yet).
Run decision not madeRun decision Not decided yet.
HeldRun decision Held.
Enter decision by, Enter decision dateReleased to run, name or date missing.
Released, a value in this FPI outside your limitsReleased to run, and any row with the same FPI ID is outside your limits.
Released, a value in this FPI could not be checkedReleased to run, and any row with the same FPI ID has no measured value or no limit, so Within your limits is blank.
Released, all values in your limitsReleased to run, every row of this FPI ID within your limits. A value equal to a limit counts as within.

Check column notes, each followed by "worth a check", on any row whatever its status:

  • Lower limit above upper limit
  • Decision date before the checked-on date
  • Decision by or date filled, run decision is not Released to run or Held
  • Rows of one FPI ID differ in part number or checked-on date
  • Rows of one FPI ID differ in run decision
  • Same FPI ID and characteristic on more than one row
  • Limit or measured value not a number
  • A checked-on or decision date after the as-of date
  • Date not readable (text in a date cell)
  • Held, nothing written in Notes
  • This row is outside your limits, run decision is Released to run

Example (fictional)

Made-up parts, names, limits and dates, extract, as of Wednesday 21 October 2026 (Wed 21 Oct 2026):

FPI IDPartChecked onCharacteristicYour limitsMeasuredWithin your limitsRun decisionStatusCheck
F-01BR-100Mon 19 Oct 2026Hole diameter8 to 8.18.04YesReleased to runReleased, all values in your limits
F-01BR-100Mon 19 Oct 2026Flange height12 to 12.412.2YesReleased to runReleased, all values in your limits
F-02HS-220Tue 20 Oct 2026Outer diameter24.95 to 25.0525.08NoHeldHeld
F-02HS-220Tue 20 Oct 2026Length40 to 40.340.1YesHeldHeld
F-03CL-310Wed 21 Oct 2026Slot width5 to 5.25.25NoReleased to runReleased, a value in this FPI outside your limitsThis row is outside your limits, run decision is Released to run: worth a check
F-03CL-310Wed 21 Oct 2026Bend angle89.5 to 90.590.1YesReleased to runReleased, a value in this FPI outside your limits
F-04BR-100Wed 21 Oct 2026Hole diameter8 to 8.18.05YesNot decided yetRun decision not made
F-05HS-220Wed 21 Oct 2026Outer diameter24.95 to 25.0525.01YesReleased to runEnter decision by
CL-310Tue 20 Oct 2026Slot width5 to 5.25.1YesReleased to runEnter FPI IDDecision date before the checked-on date: worth a check

Worth a check each shift

  • Runs released with a value outside your limits (status Released, a value in this FPI outside your limits).
  • Held runs with nothing written in Notes, and runs with no decision yet.
  • Released runs with no name or date for the decision.

Whether a first piece is good and what to do with a held run is your call. The file records it and does not judge it.

Related

Advisory template, in English. Not a customer decision.