Design-to-launch: daily operating review pack
This is a short daily sheet for the people working on a new product or service launch. It brings design tasks, samples, test results, supplier material and cost into one view, so the project lead can see what is blocking the launch date and who must act today.
When to use it
Use it every working day while a launch is active, from the day the specification is fixed until the first lot or first customers are served. Stop the daily review once the launch is done and move to a weekly one.
The template
| Workstream | What to enter | Source record | Action trigger | Owner |
|---|---|---|---|---|
| Design tasks | Tasks due today, number finished, any waiting for a decision | Task list | A task past its due date | Design lead |
| Change requests | New requests received, and whether each was approved or held | Change log | A change after the specification was fixed | Project lead |
| Samples and trials | Which sample or trial is in progress and its stage | Sample tracker | A trial not started on its planned date | Operations head |
| Test results | Tests finished, tests waiting, and any measurement outside the agreed range | Test records | Any result outside range | Quality lead |
| Material and supplier | Items due, items received, and expected arrival dates | Purchase orders, supplier messages | Material due within a few days but unconfirmed | Purchase lead |
| Cost against target | Current cost per unit in ₹ against the target in ₹ | Costing sheet | Cost above target | Accounts lead |
| Days to launch | Days left to the planned date and the date you now expect | Launch plan | Expected date later than planned | Project lead |
| Open issues | Issues without a named owner or without a date | Issue list | Any issue with no owner | Project lead |
How to fill it
- What to enter: counts, dates and rupee values, with a three or four word note when something is out of range.
- Source record: state which list you took each line from, so the same line can be rebuilt the next day.
- Action trigger: set your own triggers at the start of the project and note them in this column. They belong to your team, and should not change midweek.
- Owner: the person who explains the line in the huddle.
- Add one line at the bottom for the single decision needed today and who will take it.
Example row
| Workstream | Planned | Actual | Note | Owner |
|---|---|---|---|---|
| Cost against target | ₹140 per unit | ₹146 per unit | Packaging quote rose from ₹6 to ₹10; asking two other suppliers for rates by Thursday | Accounts lead |
Review and sign-off
- The project lead runs the review and initials the sheet, and the owner reads the week's sheets on a fixed day.
- Review daily during the launch, and look at the week's pattern every Friday for lines that were red more than twice.
- Escalate to the owner on the same day when the expected launch date slips, when cost goes above target, or when a failed test needs a design change.
Keeping it up to date
- Remove workstreams that are finished and add any that the project newly needs, such as a trial run at a second site.
- Carry the last week's sheets into the launch review so the cause of each delay is on record.
- Keep the sheets for the period your CA or the law requires, as they support project cost and decision records.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →