# CNC Program Revision Log Worksheet

> Source: https://netray.co/tools/cnc-program-revision-log-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable log of CNC program changes with revision, reason, proveout status and approver, exportable to Excel.

## Category

engineering-plm

## Industry

Machining

## Audience

- CNC programmer
- Manufacturing engineer
- Quality manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Program

**Key:** program

**Type:** text

#### Part and print rev

**Key:** part

**Type:** text

#### Program rev

**Key:** rev

**Type:** text

#### Reason for change

**Key:** reason

**Type:** select

**Options:**

- New program
- Print revision
- Cycle time reduction
- Tool change
- Scrap or quality fix
- Machine change
- Other

#### Cycle time before

**Key:** before

**Type:** number

**Unit:** min

**Format:** decimal

#### Cycle time after

**Key:** after

**Type:** number

**Unit:** min

**Format:** decimal

#### Time saved per part

**Key:** saved

**Type:** number

**Unit:** min

**Expr:** before - after

**Format:** decimal

#### Proveout status

**Key:** proved

**Type:** select

**Options:**

- Not proved
- Dry run done
- First piece approved
- Released

#### Changed by

**Key:** by

**Type:** text

#### Date

**Key:** date

**Type:** date

**Rows:**

**Program:** O1042

**Part:** BRK-2210 Rev C

**Rev:** A

**Reason:** New program

**Before:** 0

**After:** 16.2

**Proved:** Released

**By:** A. Singh

**Date:** 2026-09-02

**Program:** O1042

**Part:** BRK-2210 Rev C

**Rev:** B

**Reason:** Cycle time reduction

**Before:** 16.2

**After:** 14.5

**Proved:** Released

**By:** A. Singh

**Date:** 2026-10-05

**Program:** O1042

**Part:** BRK-2210 Rev D

**Rev:** C

**Reason:** Print revision

**Before:** 14.5

**After:** 14.8

**Proved:** First piece approved

**By:** P. Rao

**Date:** 2026-10-18

**Program:** O2210

**Part:** SHF-0450 Rev A

**Rev:** A

**Reason:** New program

**Before:** 0

**After:** 9.4

**Proved:** Dry run done

**By:** P. Rao

**Date:** 2026-10-19

**Totals:**

#### Net time change recorded

**Key:** saved

**Agg:** sum

**Format:** decimal

**Summary:**

#### Revisions logged

**Key:** entries

**Expr:** count

**Format:** integer

**Primary:** true

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the log

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Is a spreadsheet enough for program control?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

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

## Search terms

cnc program revision log, nc program version control spreadsheet, g-code revision tracking, cnc program change log excel, cnc program release form, nc program control log, cnc program history template, program revision control machining

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json