An assessment worksheet. Status reflects what has been reviewed, not a warranty of system behaviour.
Completion milestone

Operational Finish Line

Establish a hard completion boundary for an operations implementation. An operation is complete when its normal business lifecycle can be executed end-to-end inside the system without disconnected manual workarounds bridging missing core workflow. This does not mean every future feature, automation, exception, integration, analytics capability, or enterprise enhancement is finished.

0 of 10 lifecycle areas accepted

Definition of done. An implementation is operationally complete when a normal business transaction can begin with the customer, proceed through sale, procurement, receiving, inventory, scheduling, field execution, equipment lifecycle, and financial handoff, and management can determine what happened and what remains outstanding from the system.

Core completion blockers

Must be resolved before the implementation counts as operationally complete. Categories A and B only.

Verification required

Category C — appears to exist, not yet proven in the actual operational workflow.

Owner acceptance required

Category D — technically working, awaiting owner visual review.

Post-finish-line work

Categories E and F. Recorded, deliberately not blocking. There will always be more the system can do; there must not always be more it must do before the operation counts as working.

Send this assessment

Your answers stay in this browser until you press send. A copy is saved to your machine at the same time.