Opening the book…
Suppose 18 of 60 eligible batch packages had at least one required entry missing at first review during the previous month. These counts are hypothetical. Under that definition, 18 ÷ 60 × 100 = 30% had a missing entry, and 42 ÷ 60 × 100 = 70% had none. The second figure does not prove that those 42 packages were accurate or met every other review requirement.
A temporary cross-functional improvement team is a reasonable starting choice. Its purpose is to reduce avoidable missing information and review rework. Production, QC, QA, and document control each contribute necessary knowledge. A manager with suitable authority sponsors the work and arranges time for staff to participate.
Before adopting these figures as a baseline, verify which packages were eligible, when first review occurred, and how missing entries were counted. Count each package once, even if it has several omissions; a separate count can describe individual omissions. Then examine the handoffs and propose a trial through the required approval process. Historical record gaps still need handling under the applicable procedure; they must not be filled through unsupported reconstruction.
A useful measure is the percentage of eligible packages with no required entries missing at first review. Keep the definition, review point, and denominator consistent. Track record accuracy, review time, and later corrections separately. If counting rules change, report the change so it is not mistaken for better performance. Once an improvement is accepted, the named process owner monitors whether it lasts.
This page titled 8.9: Example - choosing a team for batch-document delays was last modified on Sun, 08 Nov 2026 10:54:36 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.