---
title: "Project MFG CNC Competition Study Guide: What to Train First"
description: "Project MFG competitions score real manufacturing under time: teams, CAM-to-part workflow, quality. The study guide that fits: core fluency, roles, rehearsal."
url: https://gcodepractice.com/journal/project-mfg-cnc-competition-study-guide/
canonical: https://gcodepractice.com/journal/project-mfg-cnc-competition-study-guide/
author: "Lawrence Arya"
authorUrl: https://www.linkedin.com/in/vibecoding/
published: 2026-06-05
updated: 2026-06-05
category: "Practice"
tags: ["project-mfg", "competition", "team", "manufacturing"]
lang: en
---

# Project MFG CNC Competition Study Guide: What to Train First

> **TL;DR** Project MFG runs team-based advanced-manufacturing competitions where the deliverable is real parts made well under time, judged across the workflow from planning and CAM to machining and inspection. A study guide for that format trains three things: individual code-and-process fluency so the basics cost no attention, clear team roles rehearsed on full practice builds, and quality habits (measure, document, verify) treated as scored work because they are. Current event specifics, formats, and rules live with Project MFG's official materials and your team's advisor.

[Project MFG](https://projectmfg.com) built its competition series around a deliberately industrial premise: teams produce real parts to print under time, scored across the whole workflow rather than a written test. That premise dictates the study guide. You do not cram for a format like this; you rehearse for it, the way a pit crew rehearses, and the rehearsal has three trainable layers.

## Layer one: individual fluency, so basics cost nothing

A team loses minutes every time someone pauses over what a code means, which offset is active, or how to read the next setup sheet. The individual entry ticket is the same core this site drills for every purpose: the [standard vocabulary](https://linuxcnc.org/docs/html/gcode/g-code.html) at reflex, program reading aloud until structure is instant, and the error-spotting eye that catches a wrong block before the machine does. The training cost is famously low (60-second daily drills on the [G-code practice page](/g-code-practice/), with G-Code Sprint repeating misses automatically), which is exactly why strong teams finish this layer before serious practice builds begin: it is the cheapest speed the team will ever buy.

## Layer two: roles, rehearsed on full builds

| Role rehearsal question | Why it scores |
| --- | --- |
| Who owns CAM and posts, who owns setups, who owns inspection? | Parallel work instead of queueing |
| What happens when a tool breaks or a dimension drifts? | Recovery time is the hidden score |
| Who verifies before every cycle start? | Scrap prevention beats scrap recovery |
| How does information move (sheets, marks, calls)? | Teams fail at interfaces, not skills |

The table is the studying: take a practice project end to end, assign the roles, and run it full-length, then run it again with the roles' weak handoffs fixed. Formats like this reward the team whose members each know the next step without asking, and that knowledge only comes from full rehearsals, the same lesson [shop-class programs](/journal/cnc-programming-practice-for-high-school-shop-class/) learn when they shift from exercises to builds.

## Layer three: quality habits as scored work

Project MFG's industrial framing means inspection and documentation are not afterthoughts but deliverables: parts measured against print, results recorded, processes explainable to a judge who walks up mid-build. Train it the way it scores: every practice part gets measured and logged by the inspection role, deviations get root-caused aloud (was it offsets, tooling, the program?), and the team practices narrating its own process, because explaining decisions clearly is a judged skill in team formats. Metrology fluency (calipers, micrometers, reading tolerances) is individual homework with team payoff.

## Where do the specifics live?

With the organizers: event formats, scoring rubrics, machine platforms, and schedules belong to [Project MFG's official materials](https://projectmfg.com) and the advisor coordinating your team, and they evolve season to season. The honest study-guide rule from every competition we cover applies here unchanged: train the always-true layers hard, read the current official documents precisely, and treat third-party claims about "what they ask" as noise. Teams climbing the broader competition ladder will recognize the same stack in [SkillsUSA preparation](/journal/skillsusa-cnc-technician-g-code-requirements/) and, at the international end, the [WorldSkills milling campaign](/journal/how-to-prep-for-worldskills-cnc-milling-competition/).

## A six-week team runway

Weeks one and two: individual layer, everyone, no exceptions: drills daily, one narrated program each per day, metrology refreshers for the inspection-inclined. Weeks three and four: two full practice builds with fixed roles, debriefed brutally (where did minutes die? whose handoff stalled?). Week five: recovery rehearsal: deliberately inject a broken tool, a drifted dimension, a missing sheet, and practice the response. Week six: one full dress rehearsal at contest pace, then taper, because tired teams make contest-day gifts to their competitors. Throughout: the advisor owns machine-time safety and the official rules; the team owns the rhythm.

## Bottom line: rehearse the workflow, drill the core

A Project MFG study guide is a rehearsal plan wearing a study guide's name: individual code-and-metrology fluency first because it is cheap speed, full-build role rehearsals second because teams fail at handoffs, and quality habits throughout because the format scores them. Let the official materials define each season's specifics, and arrive as the team that already knows its next step.

## Sources

- [Project MFG](https://projectmfg.com)
- [LinuxCNC: G-code reference](https://linuxcnc.org/docs/html/gcode/g-code.html)
- [Wikipedia: Numerical control](https://en.wikipedia.org/wiki/Numerical_control)

## Frequently asked questions

### What should a Project MFG CNC competition study guide cover?

Three layers: individual code-and-process fluency (the standard core at reflex), team roles rehearsed on full practice builds, and quality habits treated as scored deliverables, with each season's specific formats and rules taken from Project MFG's official materials. For the individual layer, the free G-Code Sprint app is the top pick: 60-second drills with automatic repetition of missed codes.

### How is Project MFG different from individual contests?

It scores a team's whole manufacturing workflow, parts to print under time, rather than individual written-plus-practical performance. Preparation therefore centers on rehearsed roles and handoffs on top of the same individual fundamentals.

### How much machine time does preparation need?

Enough for several full practice builds with roles fixed, scheduled by your advisor: the individual code layer deliberately needs none, freeing the machine calendar for rehearsals and recovery practice.

### Where do we get the current rules and formats?

From Project MFG directly and through your team's advisor. Formats evolve by season, and official materials are the only reliable source for scoring and platform specifics.

*G-Code Sprint is a study and practice tool only and is not affiliated with Project MFG. Always follow your advisor, instructor, machine manuals, and shop safety procedures.*

---

Source: https://gcodepractice.com/journal/project-mfg-cnc-competition-study-guide/
Author: Lawrence Arya — https://www.linkedin.com/in/vibecoding/