Keep the audit a records check, not a feeding decision
Work from a clear list and minimize unnecessary handling. Keep milk appropriately stored while checking labels; do not spread bags out at room temperature to complete a spreadsheet. Follow current CDC handling guidance and any individual instructions from your pediatrician, lactation professional or care team.
CDC advises labeling expressed milk with the expression date and using older milk first. That limited organizational principle does not permit guessing a missing date or treating every oldest bag as suitable to feed. Storage conditions, thawing and handling history still matter.
Give each bag a stable local ID and distinguish the date expressed from the date entered into the app. Adding a bag today does not make it newly expressed. If a bag moved between freezer locations, retain its history rather than resetting its age to the move date.
Worked audit: four bags, five records and two separate issues
Fictional records check on October 24: physical bags B01, B02, B03 and B04 are present. B01 has expression date October 20, B02 October 21, B03 an unreadable date and B04 October 22. The app contains five rows because B02 was entered twice.
| Physical bag | Record situation | Evidence | Audit action |
|---|---|---|---|
| B01 | One row | Oct 20 label; amount matches | Retain linked record |
| B02 | Two rows for the same bag | Same bag ID and physical item verified | Correct duplicate record; keep one bag |
| B03 | One row with guessed date | Physical date unreadable | Remove unsupported certainty; resolve before use |
| B04 | One row | Oct 22 label; location changed | Update location without resetting expression date |
Four physical bags and five rows is not five bags of milk. Correcting the duplicate is an inventory action; it does not change the contents of B02. B03 is a different problem: its identity may be known while its expression date is not. Do not invent a date just to make the count or sort look complete.
Among the date-readable bags, October 20 precedes October 21 and October 22. B03 cannot be placed reliably in that order from the available label. The example deliberately gives no instruction to feed any bag and no safety clearance based on age alone.
Keep unresolved labels visible before new stock hides them
Check whether a contemporaneous pump record or other reliable original evidence resolves the discrepancy. Retain what you changed and why. If the relevant history cannot be established, do not feed based on a guess; seek appropriate feeding guidance rather than treating the inventory as a safety assessment.
Count and, where useful, total only amounts whose units and record identity you have checked. A bag count is not a volume. Keep an unknown amount unknown rather than making it zero, and do not add ounces and milliliters as bare numbers.
Before entering new bags, compare the current physical IDs with the corrected record list in both directions. An app-only row may be a used bag, a missing item or a duplicate; it needs evidence. The linked thawed-time guide handles a separate time-sensitive record once milk changes state.
MilkVault organizes the stash; dates remain records
MilkVault’s current listing describes pump logs, storage batches by expression date and location, older-batch-first deductions, bottle logs with stash updates, charts and totals. Premium includes CSV export of pump, batch and feeding records. Check current other free limits and purchase terms in the app.
We publish MilkVault. Its listing explicitly states that app dates and estimates do not determine whether milk is safe and that it does not provide medical advice or lactation treatment. A recorded expiry or automatic deduction cannot reconstruct an unknown storage history.
Use this independent CSV as a discrepancy log; it does not import into MilkVault or certify a batch. Keep personal feeding details private. The broader stash-log parent explains ordinary records, while this guide checks record-to-bag mismatches before adding more.
If the method fits your task, explore MilkVault’s listed features on an iPhone. Check current features and plans before downloading.
See MilkVault for iOSDownload the free worksheet
Use the CSV in Numbers, Excel or a spreadsheet editor. Four fictional bags and a blank row. Dates illustrate a record audit, not feeding suitability, expiry calculation or safety clearance. Replace them with your own observations. The CSV is separate from the app and no email is required.
Questions answered
Does an app expiry label prove safety?
No. Check current handling guidance and the actual history.
Can I estimate an unreadable expression date to sort the bags?
Do not present a guess as verified. Keep the discrepancy unresolved and seek appropriate guidance before use.
Does deleting a duplicate row remove a physical bag?
No. Verify that both rows describe the same actual bag before correcting the record.
Continue with MilkVault on iOS
Use the App Store listing to check compatibility, privacy information and current plan terms. A free download may offer paid features.
Download MilkVault for iOSSources and product details
- CDC: Breast milk storage and preparationUS public-health handling/label guidance read October 24, 2026; no individual batch safety determination.
- MilkVault on the App StoreCurrent US App Store product description; checked October 24, 2026.
Editorial method: primary guidance, a current Apple listing, an original worked example and an independent critique. No search ranking, install or outcome result is claimed.