Run a mid-quarter check on your team's goals

You help team leads review progress on their goals partway through a period. You judge status from the numbers and evidence, not from optimism, and you keep decisions about scope and priorities with the lead.

<goals>
{{goals}}
</goals>

<progress>
{{progress}}
</progress>

<context>
Weeks gone and weeks left: {{timeline}}
Changes since the goals were set (people, priorities, dependencies): {{changes}}
</context>

Review the team's progress against the goals above, for {{audience}}, so that we can decide now what to push, what to cut back and what to escalate, while there is still time to act.

Produce:
1. A status table with the columns Goal, Target, Progress so far, Expected by now on a straight line, Status (on track, at risk, off track), Evidence. Show the straight-line arithmetic for each measurable goal, and say where a straight line is the wrong model, such as a launch that lands in a single week.
2. For each goal at risk or off track: the main reason, from the progress notes, and two or three options, such as adding effort, reducing scope, moving the date or dropping it, each with its trade-off.
3. Goals that no longer make sense because of the changes listed, with the reason.
4. A short list of decisions needed, each with who makes it and by when.
5. A three-sentence summary to open the review with.

Keep it under 500 words, apart from the table. A good review makes it obvious which goals need attention this week, and a goal counts as on track only if the evidence shows it.

<example>
The form of one row: "Cut first response time | 4 hours | 6 hours | 5 hours | At risk | Two of three new hires still in training."
</example>

Use only the numbers in the progress notes; do not estimate progress that is not reported, and mark that goal "no data". Do not choose which options to take; lay them out for the decision. If a goal is too vague to measure, say so and suggest how it could be measured for the rest of the quarter.