What a post-mortem leaves behind
This is a fictional demonstration case created for a coursework assignment; no real brand, buyer or order is described.
When a retail emergency-lighting project is closed, the useful thing left behind is not the final report but the list of what was missed. The project described here was a fictional chain-retail emergency lantern order, and its post-mortem produced a checklist that is more useful than the project itself. This article presents that checklist and the reasoning behind each line.
The parameters that had to be confirmed in writing
The first category of omission was the parameter confirmation. The buyer had asked for figures in the request and received figures on the spec sheet, but several figures arrived without the conditions that make them comparable. The post-mortem checklist now requires the parameter confirmation to be returned in writing at quotation stage, not at sample stage.
The light figure must carry the machine type, the mode, the detector distance, the drive current, the ambient temperature and the warm-up. The runtime figure must carry the battery capacity, the starting voltage, the ambient temperature and the cutoff condition, and must be split by brightness level. The weather claim must be expressed as IP-rated with declared test conditions, and must name the procedure and duration. Each line is a claim that has to travel with its condition.
Runtime per brightness level sets out the split, and lumens without test conditions sets out the light-side conditions.
The file that had to be assembled early
The second category of omission was the file. The retail channel required documents at inbound, and the buyer discovered at the end that some documents had been requested but never checked for validity. The post-mortem checklist now requires the file to be assembled before the shipment, with the validity period noted against each entry.
The file covers the compliance documents for the destination market, the transport documents for the lithium cells, and the test-condition sheets for the claims on the label. A document that is valid on the day it is issued may not be valid on the day the consignment arrives, and that gap is invisible unless the file is assembled early.
CE, FCC and UKCA: what files buyers should request sets out the file types, and UN38.3 test summary: the four checks sets out the transport checks.
The delivery that had to be held in pieces
The third category of omission was the calendar. The project had one lead time and it slipped. The post-mortem checklist now requires the calendar to be held in pieces: parameter confirmation, sample approval, production, packing, and inbound. Each piece has its own lead time, and the delivery date is held against the last piece rather than the first.
The quantity tolerance was the fourth. A retail order is placed against a planogram, and a short shipment changes the planogram. The checklist now requires the tolerance and the handling of a shortfall to be agreed before the order is placed.
Retail emergency project post-mortem checklist
| Category | What the checklist requires | The omission it prevents |
|---|---|---|
| Light figure | Machine, mode, distance, current, ambient, warm-up in writing | A figure that cannot be compared |
| Runtime figure | Split by brightness level with capacity, voltage, ambient, cutoff | A figure that belongs to an unknown setting |
| Weather claim | IP-rated with declared test conditions, procedure and duration | An unconditional claim with no content |
| File | Compliance, transport and condition sheets with validity dates | A document that is not valid on arrival |
| Calendar | Confirmation, sample, production, packing, inbound in pieces | A single lead time that slips unseen |
| Quantity | Tolerance and shortfall handling agreed | A short shipment against the planogram |
| Sample | Golden sample signed off against a written list | No reference for the production batch |
| Labelling | Label artwork matched to the condition sheet | A mismatch the audit will find |
A checklist ≠ a guarantee
A post-mortem checklist is not a guarantee. It is a list of the places a project has already slipped, and it can be used to find the next slip earlier. The first boundary is that a checklist is a habit rather than a document.
A second boundary: a retail channel requirement is not the same in every market. The file checklist should be verified against the destination rather than copied from a previous project.
A third boundary: a fictional post-mortem is not evidence about a real channel. The checklist is derived from a fictional project, and the process it describes is a process to be anticipated, not a record of a real engagement.
Five questions for the supplier
- Which test conditions produced the light and runtime figures, and will you attach the condition sheet to the quotation rather than after the order? Parameters should be confirmed in writing at quotation stage.
- How is the runtime split by brightness level, and what is the battery capacity, starting voltage, ambient temperature and cutoff for each? One runtime figure cannot be planned against a duty period.
- How is the weather claim expressed, and what procedure and duration do the declared test conditions name? The claim should travel with the condition.
- Which documents travel with the shipment, and what are their validity periods against the arrival date? The file should be assembled before the shipment.
- What is the calendar in pieces, from parameter confirmation to inbound, and what quantity tolerance do you accept against the planogram? The delivery date is held against the last piece.
Next step
Attach the post-mortem checklist to the request and ask the supplier to answer each line before the order is placed. Keep the answers, the file and the calendar together. Related reading: emergency backup lighting for the acceptance dimensions and quote comparison beyond the unit price for comparing the returned parameters. To prepare a retail emergency project brief, start at contact.
Part of the Lumizuno outdoor-lighting notes. Illustrative values only; lumens and ingress ratings must be read with their test conditions.