Twenty minutes. Four items. Same time every Monday, before the first block, and it ends when the clock says so whether or not everyone has spoken.
That is the whole format, and the reason it needs stating is that the meeting most teams actually hold is forty-five minutes long, has no fixed agenda, opens with each agent reciting how many dials they made last week, and closes with the team lead saying something encouraging. Nobody’s week changes as a result. The meeting below is built so that something does: a count that tells the team what the week owes, one recording that teaches something, and a set of list assignments that stop two agents calling the same house. Everything else that a team meeting might contain, the market update, the transaction rundown, the celebration of the closing on Alder, belongs in a different meeting or an email.
Item one: the board, read, not discussed
Four minutes. The team board was posted Friday afternoon, and everyone has seen it. The team lead reads the three ranked columns aloud in order, conversations, dated calls made on time, appointments per conversation, and the two team-only numbers on the bottom line, collisions and stop requests honored same day. Then stops.
There is no discussion of the board in the meeting. An agent who wants to talk about their appointments-per-conversation number does that in the coaching review, one on one, where it can be useful. Reading the board aloud is a ritual with a purpose, which is that the whole team hears the same three numbers in the same order every week until the numbers become the definition of the work. A team that hears “conversations, dated calls on time, appointments per conversation” fifty Mondays a year stops thinking about dials without being told to.
The one number that is never read aloud is dials. It is in the system for the frequency caps and nowhere else, per the board piece, and a team lead who reads it out has just told the team, whatever the board says, that volume is what gets noticed.
Item two: the dated calls due this week
Six minutes, and this is the center of the meeting. The system produces a count of every stage-three record, per the pipeline stages, whose date falls in the coming week, per agent. The team lead reads each agent’s number aloud: eleven, four, nineteen. The count is the point. Then each agent says one sentence: whether they can make all of them on the day, and if not, which ones need to move to someone else.
That is the whole item, and it does three things. It puts the week’s promises to homeowners on the table before the week starts, so that nobody discovers on Thursday that the agent with nineteen callbacks also had an inspection. It surfaces the agent whose count is zero, which is a pipeline problem that the busy-week piece explains will show up as an empty calendar in ninety days, and which is easier to talk about on a Monday than in December. And it makes the handoff of a dated record a normal, spoken thing, with the ownership rule applied in the room: the record moves with its words and its date to a named agent, who opens the call by saying so.
Nothing else about the pipeline is discussed. Not the appointments set last week, which are on the board. Not the listings taken, which are a lagging number. The dated calls due this week are the only forward-looking count the team has, and they get the middle of the meeting.
Item three: one recording
Six minutes. One call, chosen by the team lead from the pull list, played once, stopped once at the moment it turned, with one question asked of the room: what had the homeowner just heard? Then two people answer. The meeting moves on.
The call is never the appointment-setting call. The coaching piece explains why: the good call teaches least, because the homeowner’s readiness and the agent’s contribution cannot be separated. The call is an under-twenty-second decline, or a “send me something” with nothing recorded after it, or a long call that ended in nothing, and it is played with the agent’s agreement, which is given in advance as a condition of being on the team, and with the homeowner’s consent to the recording established per the recording rules. A recording of a homeowner who asked not to be called is never played. Ever.
One recording, not three, because a team that hears one call and one question every week for a year has heard fifty calls and fifty questions, which is a coaching curriculum, and a team that hears three calls in a rushed ten minutes has heard noise.
Item four: the list assignments
Four minutes, and this is the only decision the meeting makes. Which lists are being worked this week, by whom, in which blocks. The fresh expired pool is open to whom. The farm boundaries are unchanged or moved. The new agent is on rung one or rung two, per the first two weeks. The pre-foreclosure file is with the one agent who has read the pieces on it. Any collision on the board’s bottom line is traced here to the list that produced it, and the assignment is fixed so it cannot recur.
The team lead announces the assignments; the team does not debate them in the room. An agent who wants a different list asks afterward. Not in the room. What the four minutes buys is that every agent leaves knowing exactly which records are theirs this week, which is the condition the shared list piece says prevents the collision, and which most teams never state out loud.
| Item | Minutes | Who speaks | What it produces |
|---|---|---|---|
| The board, read | 4 | The team lead only | The three numbers and the compliance line, heard in the same order every week |
| Dated calls due this week | 6 | The lead reads counts; each agent says one sentence | The week’s promises on the table; handoffs made by name; the zero surfaced |
| One recording | 6 | The lead plays and stops it; two people answer one question | One thing to try, for the whole team, this week |
| List assignments | 4 | The team lead | Every agent knows which records are theirs; collisions closed at the source |
What is not in it
Dial counts, as above. Wins, unless a win is a dated call that became a listing, in which case it is reported as that, in one sentence, because it teaches the mechanism. Market commentary. Transaction status. Motivation, in the speech sense; the meeting’s design is the motivation, and a team lead who feels the need to add a talk at the end has usually let one of the four items run long.
And it is not longer than twenty minutes. The block starts at the half hour, and a meeting that runs over has taken the first ten minutes of the week’s prospecting from every agent in the room, which is the opposite of its purpose. When the clock reaches twenty, the meeting is over, whichever item it was on. The next week’s meeting is shorter as a result, because everyone learned that the lead meant it.
Why Monday, and why before the block
The solo agent’s Friday review looks back at the week and changes a decision. The team meeting looks forward at the week and assigns it, and the two are different acts that belong on different days. Monday, before the first block, puts the dated calls and the list assignments in every agent’s head at the moment they open the dialer, and the recording’s one thing to try is tried within the hour rather than remembered on Wednesday.
The teams hub covers the tools a team coordinates on. The meeting is the twenty minutes a week in which the coordination is said aloud: three numbers, the week’s promises, one call, and whose list is whose. Four items, and the clock.