Engineering & PLMFree worksheetPDF, Excel, Word exportMachining

CNC Program Revision Log Worksheet

The wrong program revision on the machine is a classic cause of scrap and customer returns. This log ties each program change to a reason, a cycle time effect and a proveout status, so you can see what is released and why.

Download:

Program	Part and print rev	Program rev	Reason for change	Cycle time before (min)	Cycle time after (min)	Time saved per part (min)	Proveout status	Changed by	Date
						-16.2
						1.7
						-0.3
						-9.4

Net time change recorded

-24.2

Revisions logged

For new programs, set cycle time before to zero; the saved column then shows a negative number that you can ignore. Keep a copy of each released program file, not just the log entry.

Compare program cycle times with ERP routings

Optional: a review of how routing times could be checked against real program cycle times.

Optional. The tool and every export work without this. No spam.

How to use the log

Add a row each time a program is created or edited. Record the program name, the part and print revision it matches, and a short revision letter. Choose the reason for change from the list, enter cycle time before and after, and set proveout status as the program moves from dry run to released. Name the person making the change and the date. Export to Excel for audits or to share with the quality team.

Controlling NC programs

A log is a record, not control. Real control means one authoritative location for released programs, a rule that machines only run what is released, and a way to see differences between revisions. Many shops use a DNC system or a source control tool for this, and the log complements it by explaining why a change was made.

Match each program revision to a print revision
Require proveout before status becomes Released
Record cycle time changes so quoting and capacity data stay honest
Retire old revisions and remove them from machine memory

Common mistakes

Operators often make small edits at the control and never write them back. Name your programs so that the revision is visible, and require edits to be saved to the master location. Another mistake is changing feeds to fix a problem without noting it, so the same problem reappears at the next job. Review the log at least when the print revision changes, and compare cycle times against what the ERP routing says.

Frequently Asked Questions

Is a spreadsheet enough for program control?

For small shops it can be, if there is one master location and discipline about edits. Larger or regulated shops usually add DNC or version control so that machines only receive released files.

What should the revision scheme look like?

Any consistent scheme works, such as letters or numbers. Make sure the program revision is distinct from the print revision and that both appear in the log.

Do I need to log operator edits at the machine?

Yes, if they are kept. Either save them back as a new revision or revert them. Unrecorded edits are a common reason the same part runs differently on another shift.

Why log cycle time before and after?

It shows whether changes helped and keeps routing, quotes and capacity planning aligned with real cycle times.

If routing times in your ERP drift from real program cycle times, Netray can build a read-only comparison. This log works without any system behind it.

Talk to an Expert Explore More Free Tools

Related Tools

MES & Shop Floor

More Engineering & PLM tools

See all

Back to All Tools