Keep a one-week food waste log
Record disposal events for seven ordinary days, then identify one repeated reason and one small change to observe next.
No CrispSum test result is claimed here.
This page supplies a method and an empty record for you to use. CrispSum has not observed your household, completed these trials on your behalf, or published invented measurements, participant quotes, before-and-after photographs, or success rates.
Create a descriptive record of what the household discarded, the immediate reason, and the context available at the time, then select one modest response for a later observation period.
A household that wants to replace a vague sense of waste with a consistent week of direct observations using practical household estimates.
Producing a representative annual waste rate, environmental impact estimate, food-safety judgment, nutrition assessment, or verified financial saving.
Materials and baseline
Keep the first record faithful to the current routine. A baseline edited to look orderly cannot answer where the friction started.
Materials
- Blank seven-day log
Keep it near the place where disposal decisions are usually made or use the editable CSV on a device.
- Receipt or price history, optional
Use it only to explain an estimated cost basis. Missing cost is better than invented precision.
- Household measure, optional
A cup, spoon, package fraction, or kitchen scale can help, but a consistent practical estimate is acceptable.
- Shared reason list
Agree on a short set of reasons before the week begins so similar events are classified consistently.
- Daily reminder
A brief end-of-day completeness check reduces reliance on memory without changing food-handling decisions.
Baseline record
- 1Choose seven ordinary days
Record the start and end dates, household size, away-from-home meals, guests, travel, celebrations, or other context that could make the week unusual.
- 2Define what counts
Include edible food discarded to trash, drain, compost, or another destination. Decide whether inedible preparation parts will be logged and label them separately.
- 3Define avoidable status
Use Yes, No, or Unsure. This is a household planning classification, not a safety instruction or moral judgment.
- 4Do not pre-correct behavior
Begin with the current routine if the goal is a baseline. Note any change already underway rather than pretending the week is unaffected.
Run the observation in order
Record an incomplete step as incomplete. Do not manufacture a clean result by changing a fact after the session.
- 01
Open the observation week
Write the date range, household context, included disposal destinations, reason categories, and amount units the household can use consistently.
Record: Week start, week end, household context, inclusion rules, and measurement method. - 02
Log at the disposal decision
Record the food when it is discarded. Never keep questionable food or delay disposal so it can be measured later.
Record: Date, meal or context, food item, food form, amount, unit, and destination. - 03
Record the immediate reason
Use the closest observed reason, such as over-purchased, hidden, schedule changed, disliked, over-prepared, storage problem, or inedible part.
Record: Discard reason, avoidable status, and a short handling or scheduling note. - 04
Estimate cost only when supportable
Use a receipt, package price and fraction, or another stated basis. Leave cost blank when the basis would be guesswork.
Record: Estimated cost, currency, and cost basis. - 05
Check completeness daily
At the end of each day, check whether an event was missed and note uncertainty. Do not recreate detailed events from vague memory.
Record: Completeness status and uncertainty note. - 06
Group the week without overclaiming
At the end, total only fields recorded consistently. Group repeated reasons and keep inedible parts separate from potentially avoidable events.
Record: Category totals, reason counts, missing-data note, and unusual-week context. - 07
Choose one next observation
Select one small change tied to a repeated reason, name an owner, and set a follow-up week. Keep other definitions as stable as practical.
Record: Change to test, reason addressed, owner, follow-up date, and comparison limits.
Fields and why they are present
The CSV contains no completed household entries. Unknown and not applicable are valid values when they accurately describe the record.
| Field | What to record | Why it matters |
|---|---|---|
| Week context | Date range, household size, guests, travel, away meals, and unusual events. | Prevents one unusual week from being presented as a typical household rate. |
| Food and form | Ordinary item name and state such as raw, cooked, opened, prepared, or inedible part. | Provides enough identity to group events without requiring a nutrition database. |
| Amount and unit | A practical estimate such as grams, cups, pieces, servings, or package fraction. | Supports consistent grouping while making the measurement basis visible. |
| Estimated cost and basis | Amount, currency, and whether it came from a receipt, package fraction, or another stated method. | Separates a documented estimate from unsupported precision. |
| Discard reason | The immediate observed cause using the household's agreed categories. | Points toward a purchasing, storage, portion, preference, or scheduling response. |
| Avoidable status | Yes, No, or Unsure under the household's written definition. | Keeps uncertainty and inedible parts separate from potentially preventable events. |
| Handling context | Known timing, location, package, schedule, or identity facts relevant to disposal. | Preserves facts without using the protocol to decide safety. |
| Destination | Trash, drain, compost, donation before disposal, or another defined route. | Clarifies what the household included in its log; it is not an environmental impact calculation. |
| Completeness and uncertainty | Daily check status, missed-event note, and fields left unknown. | Makes data gaps visible instead of silently estimating them. |
| Change and follow-up | One response, the repeated reason it addresses, owner, and follow-up week. | Connects the observation to a modest next step without claiming success in advance. |
What the record can and cannot support
Summarize only what was recorded. The useful output is a transparent description of one week and a reasoned next question, not a universal household waste figure.
Can supportA small response tied to that reason, such as quantity, visibility, scheduling, or portion review.
Cannot showThat the reason caused every event or that the proposed response will reduce waste.
Can supportA note that the total is sensitive to an unusual event and should be interpreted with context.
Cannot showA typical weekly or annual spending pattern.
Can supportA qualitative reason count and a plan to simplify measurement next time.
Cannot showA defensible quantity or cost total obtained by filling gaps with guesses.
Can supportSeparate reporting of preparation scraps from potentially avoidable food.
Cannot showThat those parts were preventable or equivalent to edible food waste.
Can supportA reason to repeat with the same definitions and note changes in household context.
Cannot showCausation, annual savings, or environmental benefit from two short household observations.
Observation never overrides a safety response.
- Never retain, taste, donate, or repurpose questionable food merely to reduce the log total or avoid recording a discard.
- The avoidable field describes a planning opportunity; it does not override recalls, allergy controls, package instructions, illness precautions, or public-health guidance.
- Use local rules for composting, donation, animal feeding, and waste disposal. The protocol does not determine whether a destination is permitted or safe.
- Clean measuring tools and surfaces appropriately, and do not measure discarded food in a way that increases contamination or handling risk.
Leave uncertainty in the record.
A blank field, not found result, or unresolved safety question is more useful than a confident guess. This protocol becomes evidence about your workflow only when the observations remain honest about their limits.