Use one dated ledger with mutually exclusive unit states. Then calculate the overall ratio from quantities, rather than averaging batch percentages that have different target sizes.
One original two-batch ledger
Fictional paper-packet production snapshot: October 13, 2026. All quantities count packets from the listed batches at the same snapshot. Each started packet occupies exactly one state. The accepted-output targets apply to that same scope.
| Batch | Accepted target | Started | Accepted | Quality hold | Scrap | Unfinished |
|---|---|---|---|---|---|---|
| A | 80 | 100 | 60 | 10 | 5 | 25 |
| B | 20 | 20 | 20 | 0 | 0 | 0 |
| Total | 100 | 120 | 80 | 10 | 5 | 25 |
For this exercise, accepted means completed and accepted; quality hold means physically finished but awaiting disposition; scrap means physically finished and rejected; unfinished means not physically finished. These are original ledger definitions, not a universal inspection policy.
Batch A reconciles as 60 + 10 + 5 + 25 = 100 started. Batch B reconciles as 20 = 20 started. Together, 80 + 10 + 5 + 25 = 120. Investigate a mismatch before calculating a dashboard total; do not silently put the unexplained units into accepted output.
Keep finished and accepted quantities distinct
Under the declared definitions, physically finished packets total 80 accepted + 10 held + 5 scrapped = 95. Only 80 count toward the accepted-output target. The 25 unfinished packets have not become finished merely because work started on them.
Keep quality hold visible as a separate quantity. Nothing in the ledger authorizes releasing those ten packets, explains the five scrap decisions or predicts how many unfinished packets will be accepted later.
The Mokkup daily-production template description proposes comparing output with targets over the reporting period. This original ledger narrows that comparison to accepted packets and explicit states. It does not adopt the vendor's dashboard artwork or its broader efficiency claims.
Aggregate quantities before dividing
Batch A's accepted-output attainment is 60 ÷ 80 = 75%. Batch B's is 20 ÷ 20 = 100%.
For the total, sum accepted quantities and matching targets first: (60 + 20) ÷ (80 + 20) = 80 ÷ 100 = 80%. Averaging 75% and 100% gives 87.5%, which gives the small batch the same weight as the large one and does not answer the overall quantity question.
The accepted-output shortfall is 100 − 80 = 20 packets at this snapshot. That is a comparison with the supplied target, not a forecast of a missed deadline or a staffing recommendation.
In a workbook, retain the raw quantities and a state-reconciliation check in each row. For a selected group of valid rows, calculate SUM(accepted) / SUM(accepted target). Display the selected batch IDs, date and included target quantity beside the ratio.
Give missing and zero targets explicit states
A test row with accepted output zero and target zero has no defined attainment ratio: 0 ÷ 0 is not applicable, not 0% or 100%. Keep that row visible, label it not applicable and exclude it from the attainment scope unless a documented reporting policy says otherwise.
A missing target is different from a supplied zero. Flag it for confirmation. If excluding such a row, disclose which row was excluded; do not show a partial ratio as though it covers every batch. Positive output against a zero target also needs an explicit policy before aggregation.
Runtime, equipment availability and ideal cycle time were not supplied. This ledger therefore provides no OEE or hourly productivity score. Its useful result is the reconciled state total and accepted-output comparison.
Copy an accepted-output dashboard brief
Prepare a production dashboard specification in US English.
Maintained workbook/ledger and required format: [enter]
Snapshot date, batch IDs and common unit: [enter]
Started, accepted, quality-hold, scrap and unfinished quantities: [paste]
Mutually exclusive state definitions: [paste]
Accepted-output targets for the same scope: [paste]
Missing/zero-target inclusion policy: [paste or TO CONFIRM]
Reconcile every started-unit row before summarizing. Keep held, scrapped and
unfinished units outside accepted output. Show physically finished quantities
only under the supplied definitions. Sum accepted quantities and matching
targets before dividing; do not average batch percentages. Show included IDs.
Keep missing targets distinct from zero; 0/0 is not applicable. Disclose
excluded rows and request a policy for positive output with zero target.
Do not invent releases, future output, runtime, OEE or productivity scores.
Return checked source rows, workbook calculation instructions and labeled
summary views. If requested, specify a sanitized HTML review snapshot with
local batch selection. No inspection approval, machine control, live import,
saved record editing, automatic alerts or guaranteed improvement.
Read the 95 finished packets back against the 80 accepted packets before sharing the target comparison. NOS can save and display a sanitized HTML review snapshot with the reconciliation beside the ratio. Keep the operational workbook and inspection records as the maintained originals, and resolve unexplained state differences there before changing the reported accepted output.