Lessons · MODEL · PERIOD 1 · LESSON 1.6 · 25 MIN · SAVE BY DAY 28
Model review
By the end of this lesson you will have closed the Model period the way every M closes: you know exactly what you finished, one task is written down so someone other than you can do it, and one task has left your week for good. Three parts: every acceptance line reviewed, one SOP written, and one task handed to Coach or your team.
- An honest review of lessons 1.1 to 1.5
- One SOP, a written procedure, for a task you repeated this period
- One task that leaves your week, with a start date
Why it matters. Every M in Million Dollar Year ends this way. You check what you finished, you write one task down so someone other than you can do it, and you hand one task over. Done once a period, that habit is meant to move work off your calendar steadily, instead of in a rush when you are already overloaded. It also tells you plainly where the period left gaps.
What you need. Lessons 1.1 to 1.5, and your Mind log for the period.
Do this.
- Open the review. Coach lists the acceptance line for each of lessons 1.1 to 1.5, with the deliverable you saved and the day you saved it.
- Mark each line met or not met. Write one sentence of reason for each. A line with no saved deliverable, or one saved after its day, is not met.
- For each line not met, set a date to finish it in period 2, or record the day it was finished late.
- Choose one task you did more than once this period. Your Mind log (the first blocks you named) and the Hour ranker show which tasks repeat.
- Write its SOP: what starts it, what it needs, the steps in order, what finished looks like, and who checks it.
- Assign one task to Coach or a named team member, with a start date. It can be the task you just wrote up.
- If Coach will send anything that leaves the business, approve its voice and knowledge first, as in lesson 1.5. After that it sends on its own, and you can mark any task "review first".
- Save. Your review, SOP and handoff open period 2.
A review records what you did. It does not measure revenue or profit, and it promises neither.
Done when. By day 28, the member has marked each Model acceptance line met or not met with a reason, saved one SOP for a task they repeated this period, and assigned one task to Coach or the team.
Max's example
The same deliverable on his own business
Max's plan: his review, day 28, with the days he intends to save each deliverable.
| Lesson | Status if saved on the planned day | Reason |
|---|---|---|
| 1.1 Targets | Met | Planned: day 3 |
| 1.2 Offer shape | Met | Planned: day 8 |
| 1.3 Owner hours | Met | Planned: 15 tasks on day 11, first move dated day 12 |
| 1.4 The Model | Met | Planned: day 18 |
| 1.5 Transition | Met | Planned: day 24 |
SOP: new application to booked call. Sales first. Starts when an application arrives. Needs the entry conditions ($20k a month, and $300 a day on Meta for Million Dollar Acquisition) and Max's open call slots.
- Coach checks the application against the gates and replies within minutes.
- Coach books the call in an open slot, sends the pre-call video and the reminders.
- Max holds the call.
- Coach records the outcome and the payment status.
Finished looks like: every qualified applicant booked within one business day. Checked by Max.
Handoff: ad scripts and copy for clients, marked automate in 1.3, go to Coach from period 2, day
- Coach drafts them and places them in the client's account on its own, since Max approved its voice and knowledge in period 1. Max marks the first two sets "review first".
This closes the period's work. It shows no result.
The form for this deliverable arrives in the next build step. The list below is what it asks for.
- Review, one row per lesson from 1.1 to 1.5: the acceptance line, met or not met, the reason, and a finish date if not met
- SOP: task name, what starts it, what it needs, numbered steps, what finished looks like, who checks it
- Handoff: the task, who takes it (Coach or a named person), the start date, and what the member still reviews