# On-Time Delivery for Cabinet Projects: Define the Promise

Canonical: https://millbase.ca/blog/on-time-delivery-for-cabinet-projects-define-the-promise
Author: [Coby Birenbaum](https://www.linkedin.com/in/cobybirenbaum/)
Published: 2026-10-19
Updated: 2026-10-19
Archive edition: 2026-09-11

On-time delivery depends on the promise being measured.

On-time delivery depends on the promise being measured. Original commitment, revised commitment, dispatch date, and accepted site receipt are different events. Keep them distinguishable so the metric cannot improve simply by repeatedly moving the date.

## Define the measure

- State the event that counts as delivery and the required quantity or scope.
- Preserve the original promise and approved revisions.
- Record reasons for changes and partial deliveries.
- Separate internal and external causes where evidence supports the distinction.

## Worked example

An illustrative order promises 20 cabinets Friday, but only 18 arrive. Whether that counts as on time depends on the agreed metric and shipment scope. State the rule rather than choosing the interpretation after seeing the result.

## Review misses

Examine the last preventable decision point: late approval, material shortage, capacity conflict, quality issue, or dispatch coordination. The goal is an earlier intervention next time.

## Related reading

- [Production Lead Time vs Cycle Time in Woodworking](https://millbase.ca/blog/production-lead-time-vs-cycle-time-in-woodworking)
- [Reducing Setup Time Without Creating Larger Cabinet Batches](https://millbase.ca/blog/reducing-setup-time-without-creating-larger-cabinet-batches)

## Definitions and further reference

- [Lean Enterprise Institute: standardized work](https://www.lean.org/lexicon-terms/standardized-work/)

## How Millbase can help your shop

### Make production conversations specific

A woodworking schedule is easier to review when the team can see the work already recorded. [Millbase Floor Pulse](https://millbase.ca/#floor-pulse) shows active workers, projects, workstations, and elapsed time. Pair it with [project records](https://millbase.ca/#projects) to discuss a delayed cabinet order with the people and work behind it, and compare logged labour with the estimate.

Ask the [Millbase AI agent](https://millbase.ca/#how-it-works) a question grounded in your workspace records. For example: *“Who is working on this project, at which workstations, and how many hours have been recorded?”* You can select a project or worker, ask follow-up questions, and request [supported reports and CSV exports](https://millbase.ca/#insights).

Use the breakdown to prepare the next production conversation. Current activity and recorded hours are evidence for planning; they do not by themselves prove that an assembly has passed inspection or is ready to ship.

## Explore the wider topic

For the broader workflow and decisions behind this guide, read [Production Scheduling for Custom Cabinetry](https://millbase.ca/blog/production-scheduling-for-custom-cabinetry).

## Frequently asked questions

### Should customer-approved date changes count as late?

Report according to a defined policy and preserve both original and revised commitments. The two views answer different questions.

### Is dispatch the same as delivery?

No. Use the event relevant to the commitment and keep transit or receiving differences visible.