Your task: keep every unresolved enquiry visible and identify repeatable problems without creating an unnecessary customer-data archive. Give each case a reference, category, owner, next action and follow-up date. Keep the detailed correspondence in its existing controlled system and link to it where appropriate.
A useful log serves two purposes: following up individual cases and deciding what to improve. Keep those purposes clear so the improvement view does not need every customer’s message or address. The free order problem log spreadsheet uses the fields below.
Create a minimal case record
Start with these fields:
| Field | Why it exists |
|---|---|
| Case reference | Distinguishes separate issues |
| Opened date | Shows age and supports period comparisons |
| Order reference, if relevant | Connects to the controlled order record |
| Category and concise issue | Supports routing and review |
| Owner, next action and due date | Makes follow-up accountable |
| Status | Distinguishes waiting, working and resolved cases |
| Resolution and closed date | Records what actually finished the case |
| Improvement note | Identifies a process change or an unresolved cause |
Avoid duplicating names, full addresses, payment information or complete email threads in a general tracker. Even an order reference can be linked to a person, so control access appropriately. The Privacy Commissioner’s guidance says collection should serve a necessary, lawful purpose that is explained.
Keep categories practical
Use a small set such as product information, compatibility, stock availability, dispatch, delivery, wrong item and damaged item. Add an “other — review” category rather than forcing every new issue into the closest inaccurate label.
Separate the customer’s reported problem from a confirmed cause. “Parcel late” describes the report. “Missed handover” is a cause only if evidence supports it. Keep “cause unknown” available so staff do not invent an explanation to close the record.
Define whether one case can carry secondary tags. If one case has both a compatibility question and a delivery enquiry, decide how it enters counts. A documented convention prevents misleading totals.
Make waiting states actionable
“Waiting for supplier” should include the information requested and the next follow-up date. “Waiting for customer” should identify what is missing and what happens if no reply arrives under your process.
Do not mark a case resolved simply because you sent a response. Record the actual outcome, such as corrected product information, accepted remedy or completed investigation. Some cases may close without a confirmed cause; preserve that distinction.
Review overdue actions at a regular time. For a sole operator, a short daily queue check may be appropriate, while the broader pattern review can happen weekly. Choose a cadence that matches the promises you give customers.
Analyse counts with the right denominator
Illustrative example: a shop logs six delivery enquiries among sixty orders in one week, and four among twenty orders in another. The counts fell, but the enquiry-to-order ratio rose from 10% to 20%.
That does not prove service quality worsened. Some enquiries may refer to earlier orders, and the sample is small. To study order incidence, match cases to the order cohort and count distinct affected orders. To study workload, count enquiries received in the week. Those answer different questions.
Show counts beside rates and describe your convention. Do not treat a one-week difference as a reliable trend without examining the cases and context.
Turn repeated issues into small changes
Choose one recurring, evidenced problem. For example, repeated questions about package contents may justify a clearer contents list and photo. A wrong-variant pattern may call for shelf labels and a packing check rather than a longer customer-service reply.
Record the proposed change, owner, completion date and what you will look for afterwards. Keep the old period’s counts so you can compare, but do not claim the change caused improvement merely because the next week was quieter.
Keep the tracker maintained
Limit access, review unnecessary copied information and set a retention approach suited to the purpose and any applicable obligations. A log left open on a public screen undermines the benefit of minimising its fields.
This method supports operations; it does not replace formal complaint procedures or legal advice. Your next step is to create the minimal table, enter current unresolved cases and review one repeated category in the weekly operating review.
Sources & reference dates
- Collecting personal informationOffice of the Privacy Commissioner · accessed 3 October 2026
Spot something that needs correcting? Send a correction. See our editorial policy and commercial disclosures.