In this article
Describe the launch before checking readiness
A launch checklist becomes useful when it is tied to a specific operating scope. Name the store, proposed service area, initial work periods and vehicle types. Describe the delivery work that is expected and the parts still under discussion. Without that boundary, teams can mark individual tasks complete while holding different ideas about what will start on the launch date.
Use the quick commerce page as a starting point for the operating conversation, then turn the agreed scope into a local record. Keep target capacity distinct from confirmed capacity. A proposed number of vehicles should not conceal missing Captains, incomplete handovers or an unresolved energy arrangement.
Give each dependency an owner and evidence
Group the readiness questions around the work: store pickup arrangements, Captain orientation, vehicle availability, energy access and support. Name the person or organisation responsible for each item. Use one row per dependency: item, owner, evidence, status and effect on launch. An illustrative row might read: collection point; store lead; rehearsal at the intended entrance; unresolved because the evening gate is locked; evening collection remains outside the proposed launch scope until access is confirmed. A message saying “in progress” is useful status, but it is not completion evidence.
Location matters as well. The International Transport Forum’s urban logistics research considers the relationship between distribution facilities and city operations, including dark stores. For a particular store, inspect access, waiting space and movement around the site. An approved address does not by itself show that Captains can collect orders without an awkward or unsafe handover.
Rehearse a normal order and an exception
Walk through a representative collection using the intended instructions and roles. Check how a Captain identifies the order, finds the pickup point, reports a problem and confirms the next step. Include a delayed order, an incorrect package and an unavailable vehicle. The rehearsal should reveal who makes decisions when the normal sequence breaks.
Involve the fleet operators and store team together so a missing contact does not fall between organisations. Record the result as ready, ready with a defined restriction, or unresolved. If an issue prevents a necessary part of the service, explain the implication for launch scope instead of hiding it beneath an overall green status.
Decide what the opening period must teach
Before launch, choose the observations that will inform the first review. These might include whether agreed capacity was available, which handover problems repeated and whether support could resolve interruptions. Define the terms consistently so different shifts do not report the same situation in incompatible ways. Ask Captains and store staff what the numbers fail to explain.
HM Treasury’s evaluation guidance encourages building evaluation into delivery from the beginning. Apply that principle with a dated review and a clear decision: continue at the same scope, change a dependency, expand or pause. A readiness check is complete when it supports an accountable operating decision and leaves a usable record for the next store.
