In a small job shop, the machine can be cutting, the operator can be ready, and the work order can technically be in setup complete status, yet production still has not truly started. The missing step is first-article approval. That gap between first piece submitted and first piece approved is where a surprising amount of capacity disappears.
Many shops already measure setup time, cycle time, scrap, and on-time delivery. Those are important. But first-article delays often hide inside setup, quality, or waiting time buckets, so nobody sees them clearly enough to fix them. If you want to stop startup delays from bleeding into production hours, you need to timestamp the first-article process directly, then break the delay down by machine, part family, and shift.
This article shows a practical way to do that without overcomplicating your system. The goal is not more paperwork. The goal is to make startup loss visible so supervisors, quality staff, and operators can shorten the time from first part made to production fully running.
Why first-article approval delays are a hidden capacity loss
In many shops, setup is treated as everything that happens before the machine begins making parts. But in reality, the startup window often continues after the first part is produced. The operator runs the first piece, waits for inspection, adjusts offsets, waits for a lead or supervisor sign-off, and only then begins normal production.
If you do not separate those events, your reports can tell the wrong story:
- Setup time looks high, but nobody knows whether the delay came from tooling, programming, inspection response time, or repeated first-piece corrections.
- Machine utilization looks weak, but the machine may be ready and simply waiting for approval. For more on comparing runtime losses by crew, see Machine Utilization by Shift for Small Manufacturers.
- Quality looks acceptable, because approved parts eventually run, but the startup delay that consumed available capacity never gets measured.
- Scheduling gets disrupted, because every late startup pushes downstream operations and increases expediting pressure. This ties closely to queue and release timing issues discussed in Manufacturing Queue Time Tracking for Small Job Shops.
For a high-mix, low-volume shop, these small delays compound quickly. A shop with many daily changeovers may lose more production time from slow first-article approvals than from major breakdowns.
What to timestamp in the first-article process
You do not need a complicated quality system to start. You need a simple event trail that captures when the first-article process starts, when it is submitted, and when it is cleared to run.
The minimum event set
At a minimum, log these timestamps for each first-article event:
- Setup start — when the machine begins preparing for the job.
- First piece produced — when the operator completes the first article or first sample part.
- First article submitted for inspection — when the part and any required paperwork or digital record are handed off or marked ready.
- Inspection start — when the inspector, lead, or authorized approver begins checking it.
- Approval complete — when production is authorized to proceed.
If the process often includes corrections, add two more fields:
- Rejection or adjustment required
- Resubmission timestamp
That gives you the ability to separate pure waiting from actual measurement and correction time.
Supporting fields that make analysis useful
Along with timestamps, capture a few identifiers so you can group results:
- Machine or work center
- Part number
- Part family
- Operation number
- Shift
- Operator
- Inspector or approver
- Approval result: approved first pass, approved after adjustment, rejected
- Reason code for delay, if known
If you are digitizing quality checks, this pairs well with a structured inspection process like the one outlined in Digital Quality Inspection Checklist Guide.
The core metrics to calculate
Once you have timestamps, do not stop at one average. You want to isolate where startup slows down.
1. Submission-to-approval time
This is the main metric:
Submission-to-approval time = approval complete timestamp - first article submitted timestamp
This shows how long production waited after the first article was ready for sign-off.
2. First-piece-to-submission time
First-piece-to-submission time = first article submitted - first piece produced
This tells you whether the delay happened before the inspector ever saw the part. Causes may include paperwork, operator uncertainty, missing gages, or a supervisor not being informed.
3. Inspection handling time
Inspection handling time = approval complete - inspection start
This isolates the hands-on review period from the wait before inspection begins.
4. Wait-for-inspection time
Wait-for-inspection time = inspection start - first article submitted
This is often the hidden bottleneck. If this number is high, the issue is not measurement complexity. It is response time, staffing, coverage, or unclear ownership.
5. First-pass approval rate
First-pass approval rate = first articles approved without adjustment / total first-article submissions
A long approval delay can come from slow response, but it can also come from multiple adjustment loops. This metric helps separate the two.
6. Lost startup capacity
To make the problem visible in business terms, convert approval delay into lost machine time.
Lost startup capacity = submission-to-approval time during machine waiting state
For example, if a machine waits 22 minutes for first-article approval and this happens 3 times per day, that is 66 minutes of startup capacity lost on that machine. Across five similar machines, the weekly effect becomes material very quickly.
If you want to translate those delays into rough financial impact, you can pair the analysis with a simple costing exercise such as FactoryOS's downtime cost calculator.
How to classify delay reasons without creating data-entry fatigue
Small shops often fail at tracking because they ask for too much detail. Keep your delay codes short and practical. Start with a small list that reflects real shop-floor causes.
Recommended first-article delay codes
- Inspector unavailable
- Supervisor or customer sign-off unavailable
- Missing gage or inspection tool
- Paperwork or traveler incomplete
- Program or offset adjustment needed
- Measurement clarification needed
- Material or print discrepancy
- Priority interruption
Do not ask operators to write essays. A dropdown code plus optional note is enough. The goal is pattern detection, not perfect storytelling.
How to analyze approval delays by machine, part family, and shift
This is where the tracking becomes valuable. Looking at the overall shop average can hide your real problem.
By machine
Group first-article approval time by machine or work center. Ask:
- Which machines have the longest average and median submission-to-approval time?
- Which machines have the highest frequency of waiting more than your target, such as 15 or 20 minutes?
- Are certain machines seeing more resubmissions or offset adjustments?
If one machine family has much longer delays, the cause may be setup complexity, location relative to inspection, fixture variation, or the need for specialized gages.
By part family
Part family analysis often reveals whether the issue is process complexity rather than machine behavior.
- Do tight-tolerance turned parts wait longer than simple milled brackets?
- Do aerospace or medical jobs require additional sign-offs?
- Do repeat parts approve quickly while new parts stall?
Part-family reporting is especially useful in high-mix shops because it shows where standard work, check sheets, and pre-stage planning can reduce startup delay.
By shift
Shift comparison frequently exposes operational gaps.
- Does first shift approve quickly because quality staff are fully present?
- Does second shift wait for limited inspection coverage?
- Does weekend production slow because only supervisors can authorize startup?
Shift-level visibility matters because the same machine and part family can perform very differently depending on staffing and decision rights. If your shop already struggles with varying execution across crews, you may also benefit from Real-Time Shop-Floor Data Without IoT to capture events more consistently.
A simple reporting format for small shops
You do not need a giant dashboard on day one. Start with one weekly report and one review meeting.
| Dimension | Metric | What to look for |
|---|---|---|
| Shop total | Median submission-to-approval time | Overall startup delay trend |
| Machine | Average minutes waiting for approval | Where capacity loss is concentrated |
| Part family | First-pass approval rate | Where startup corrections are common |
| Shift | % of first articles approved within target | Coverage and response consistency |
| Reason code | Count and total minutes | Most common causes of delay |
Use median as well as average. Averages can be distorted by a few extreme delays. Median tells you what a typical startup experiences.
Where the bottlenecks usually are
When small job shops begin measuring first-article approvals, they often find one of four root causes.
1. The part is ready, but no one knows it
The machine operator finishes the first piece, but quality is not notified quickly or reliably. A visual queue, simple status button, text alert, or MES event can cut this delay immediately. If you are exploring digital tracking more broadly, see Complete Manufacturing Execution System Software Guide.
2. Approval authority is too narrow
If only one person can sign off, the entire line waits when that person is busy. Many shops can safely broaden approval authority using standard criteria, training, and escalation rules.
3. Inspection tools or requirements are not staged
Startup slows when gages, prints, revision notes, or check sheets are missing. In these cases, the problem started before setup ever began. Better pre-job preparation solves it.
4. The first pass is unstable
If parts routinely need offset tweaks or program corrections, the delay is not only an inspection problem. It is also a setup accuracy and process capability problem. Those cases should connect to rework and startup correction analysis. Related reading: Manufacturing Rework Tracking for Small Job Shops.
How to reduce first-article approval delays in practice
Once you can see the delay, improvement becomes much more targeted.
Set a clear response-time target
Define a practical standard such as: first-article inspection starts within 10 minutes of submission for in-process jobs during staffed hours. The exact number depends on your shop, but a target creates urgency and accountability.
Create a visible first-article queue
Do not let requests disappear into hallway conversations. Use a digital queue or a single clear board that shows:
- Job
- Machine
- Submission time
- Status
- Assigned approver
This turns an invisible wait into an active work queue.
Pre-stage high-risk jobs
If certain part families or machines regularly produce long approval times, flag them before release. Ensure the gages, print revisions, and qualified approver are ready before setup begins.
Expand cross-training carefully
Second-shift and off-shift delays often come from limited inspection coverage. Cross-training leads or senior operators for defined approval types can reduce waiting while maintaining control.
Separate waiting from correction time
Do not blame inspection for every long startup. If 5 minutes are spent waiting and 25 minutes are spent correcting dimensions, those are different problems with different owners.
Review the worst delays weekly
Pick the top five longest first-article approvals each week. Ask:
- What actually delayed startup?
- Could this have been prevented before setup?
- Was the wait caused by staffing, process, or technical correction?
- What standard should change?
This simple discipline often produces better results than a large monthly KPI review.
How first-article tracking fits into broader shop-floor control
First-article approval tracking should not live in isolation. It connects directly to scheduling, quality, and execution discipline.
- Scheduling: If startup approvals are slow on certain resources, planners need realistic launch assumptions. For related planning ideas, see High-Mix Low-Volume Production Scheduling Guide.
- Quality: Repeated first-pass failures may point to weak setup standards, outdated instructions, or unstable processes.
- Capacity planning: Lost startup minutes are real capacity loss, even if they never appear as downtime.
- Continuous improvement: This metric gives supervisors a concrete way to attack hidden waiting that standard setup reports often blur.
For small manufacturers building more disciplined operating systems, resources from NIST Manufacturing can also support broader process improvement efforts.
Start simple, but make the delay visible
The biggest mistake is waiting for a perfect system. A paper traveler with handwritten times is better than no data at all. A shared spreadsheet is better than assumptions. A basic MES workflow is better still, because it makes events visible in real time and easier to report by machine, part family, and shift.
The key is to define first-article approval as its own measurable process, not a vague tail end of setup. Once you do that, you can see whether startup is being delayed by response time, staffing, tools, paperwork, or unstable setups. Then you can fix the real cause instead of arguing over whether setup was “too long.”
Hidden startup loss is still lost capacity. If your shop runs frequent changeovers, measuring first-article approval delays may be one of the fastest ways to recover machine time without buying new equipment.
If you want a practical way to capture shop-floor timestamps, track approvals, and make these delays visible in real time, start a free FactoryOS trial.