8D Gate

Launch · Excel

Tool and die maintenance log by hit count: free Excel

One row per event on a tool, die or mould: counter readings, planned maintenance, sharpening or regrinding, repairs and inspections. Maintenance is tracked by the counter (hits, strokes or shots) against your own interval, not by the calendar. The latest maintenance of each tool shows the count left to the next one, and tools at or past it are flagged.

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

Get the free tool and die maintenance 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 intervals, not ours

  • Count intervals come from your toolmaker, your customer or your own records. The file quotes no intervals or values from any standard or supplier and fills in none for you.
  • This log works by counter reading. For date-based maintenance of tools your customer owns, with location and owner marking, see the customer-owned tooling register.
  • After a repair, the log asks whether a first piece check was recorded. The check itself goes in your own first piece record, for example a first piece inspection log.

What is in the file

  • Settings: an as-of date (blank means today).
  • Log, one row per event: tool ID, tool or die description, line or machine, event type, event date, counter reading at the event, your count interval to the next maintenance, done or read by, released to production (Yes, No, Not yet), released by, first piece check recorded after (Yes or No), notes.
  • Next due at count: counter reading plus your interval, on maintenance rows. Count left to due: on the latest maintenance row of each tool only, next due minus the highest counter reading logged for that tool. A reading equal to the next due count counts as reached. Count left is negative once the due count is passed.
  • 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, latest maintenance rows at or past your interval, a line that should read 0 (rows not in any status), rows per event type and rows per release answer. No score and no ranking.
  • The log does not restart the count after a counter reset. After a reset, use a new tool ID for the reset counter (for example T-01-B).

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 tool IDThe row has an entry but no tool ID. It still counts.
Enter line or machine, Enter event typeIn that order. Event type blank or typed outside the list (Counter reading, Planned maintenance, Sharpen or regrind, Repair, Inspection only, Other).
Enter event date, Enter counter reading, Enter done or read byIn that order. Text in the date or counter cell counts as blank.
Counter reading loggedEvent type Counter reading, all of the above filled.
Logged, not a maintenance eventEvent type Inspection only or Other.
Enter your count intervalMaintenance event (Planned maintenance, Sharpen or regrind, Repair) with no interval, or an interval that is not a number above 0. The interval is your own; the file fills in none.
Enter released to productionBlank, or typed outside the list (Yes, No, Not yet).
Not released yet, Held, not releasedReleased to production Not yet, or No.
Enter released byReleased Yes, name missing.
Earlier maintenance, a later one is loggedThis tool has a maintenance row with a higher counter reading.
Count reached or past your intervalLatest maintenance of this tool: the highest counter reading logged for the tool on any row is at or past the next due count.
Within your count intervalLatest maintenance of this tool, highest counter reading still below the next due count.

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

  • Counter reading lower than on an earlier-dated row of this tool
  • Counter reading or interval not a number above 0
  • Date not readable (text in a date cell)
  • Event date after the as-of date
  • Same tool, event type and counter reading on more than one row
  • Repair with no first piece check recorded after it
  • Released by filled, released to production is not Yes
  • Held, nothing written in Notes
  • Interval entered on a row that is not a maintenance event
  • Rows of one tool differ in line or machine
  • Count reached or past your interval

Example (fictional)

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

Tool IDEventDateCounterYour intervalReleasedFirst piece check afterCount leftStatusCheck
T-01Planned maintenanceMon 5 Oct 202612000050000YesYesEarlier maintenance, a later one is logged
T-01Counter readingMon 12 Oct 2026145000Counter reading logged
T-01Sharpen or regrindThu 15 Oct 202616000040000YesYes2000Within your count interval
T-01Counter readingTue 20 Oct 2026198000Counter reading logged
T-02RepairFri 16 Oct 20268000030000YesNo-2000Count reached or past your intervalRepair with no first piece check recorded after it: worth a check; Count reached or past your interval: worth a check
T-02Counter readingWed 21 Oct 2026112000Counter reading logged
T-03RepairTue 20 Oct 2026500020000Not yet20000Not released yetRepair with no first piece check recorded after it: worth a check
T-04Inspection onlyWed 21 Oct 20263000Enter done or read by
Counter readingWed 21 Oct 2026190000Enter tool ID
T-01Counter readingWed 21 Oct 2026150000Counter reading loggedCounter reading lower than on an earlier-dated row of this tool: worth a check

Worth a check each week

  • Tools at or past your count interval (red rows).
  • Repairs with no first piece check recorded after them.
  • Counter readings lower than an earlier one: a reset counter or a typing slip. The log does not restart the count after a counter reset. After a reset, use a new tool ID for the reset counter (for example T-01-B).
  • Tools held or not released yet.

Whether a tool goes back into production is your call. The file records it and does not judge it.

Related

Advisory template, in English. Not a customer decision.