Batch material balance — working review WORKING NOTES — review decisions belong in your controlled records. Guide: https://seal.run/blueprints/guides/batch-material-usage-reconciliation Use one material and a defined physical boundary for the batch. Keep the actual movements, their measurement basis and the difference assessment in one reproducible account. 1. Batch, material and balance boundary Identify the batch, material, source lots and containers. State whether the balance begins at warehouse issue, manufacturing receipt or process addition. Define the net-mass unit and keep reservations outside the physical source population. Your evidence and observations: [Not recorded] 2. Actual source quantity List the issue events included once each, with container identities and supporting observations. Retain gross/tare/net readings where used, their units, instrument and time. Explain any conversion before aggregating. Your evidence and observations: [Not recorded] 3. Supported destinations List actual use, physically received returns, samples and evidenced waste by event ID. Identify the receiving location/container for returns and the quantity evidence for losses. Check that a sample has not also been counted inside waste. Your evidence and observations: [Not recorded] 4. Calculation and difference investigation Record source total minus accepted destinations, preserving the residual. Examine the original measurement records, duplicate attribution and late events. Distinguish a supported transcription correction from a later reweigh after possible intervening handling. Your evidence and observations: [Not recorded] 5. Assessment and separate posting exceptions Cite the process’s actual assessment criteria and the evidence supporting the conclusion. Name unresolved quantities and owners. List ERP delivery issues separately so a late acknowledgement does not create another physical use or change the balance. Your evidence and observations: [Not recorded] EVIDENCE NEEDED TO FINISH Every included quantity has attributable evidence on the same basis, each event contributes once, and any residual has an explicit assessment. Planning and posting exceptions remain distinct. A zero difference alone does not establish correct lot identity or batch release.