The big idea: A weekly brief earns trust when every line is specific and honest, so report results with evidence, flag risks early and make clear asks.
In 60 seconds
- A weekly brief is a one-page client update: where the project stands, what you did, what you learned and what comes next.
- Every line needs a number, a name or role, a date or evidence. Vague lines sound busy but show nothing.
- Report missed goals and why, flag risks the week you see them, and make asks with who, what and by when.
Do this: submit your seven-part Weekly Consulting Brief in Canvas every week, on time, on one page and with no vague lines.
How a weekly consulting brief works
Every week your team submits a short consulting-style progress brief: where the project stands, what you did, what you learned and what comes next. Think of it as the update a consulting firm gives a client: clear, focused, honest and actionable. It fits on one page.
Snapshot
2 to 3 lines: the project focus and the current stage, so a reader is up to speed in 10 seconds.
Part: 1. Project snapshot.
Goals vs. done
The 3 to 5 goals you planned, then what you actually did for each, with numbers.
Parts: 2. Weekly goals and 3. What we actually did.
Evidence
What you discovered, realized or decided, and what shows it.
Part: 4. Key insights or learning.
Blockers and asks
Risks flagged early, and the specific help you need.
Parts: 5. Roadblocks or risks and 7. Support needed.
Next steps
The priorities for next week, each with an owner or a day.
Part: 6. Next week’s priorities.
Vague lines sound busy
- “Worked on interviews.” How many? With whom? What did you learn?
- “Made progress on the prototype.” What exists now that did not last week?
- “Some issues with the client.” What issue, and what does it put at risk?
- “Need help.” From whom, with what, by when?
Specific lines show work
- “Interviewed 4 of 6 nurses on night shift.” A count, a group and an honest miss.
- “Built version 2 of the card and tested it with 8 patients: 5 used it.” A result you can check.
- “Client contact is out next week, so approval could slip a week.” The risk and its impact.
- “Need an intro to the IT manager by Friday to confirm text alerts.” Who, what and when.
The four specifics test
A strong line has at least one of these: a number, a name or role, a date or evidence (a quote, a count, an artifact). If a line has none, rewrite it.
Honest beats impressive
Report every goal, including the ones you missed, and say why. Flagging a risk early is what good consultants do. A brief that is always green is a brief nobody trusts.
How to flag a riskRisk, impact, response, ask
Write each risk in four short parts:
- Risk: what might go wrong. “The client has not approved on-site testing.”
- Impact: what it puts at risk and by how much. “Round 2 slips past the presentation.”
- Response: what you are doing now. “We sent the testing plan Monday.”
- Ask: what you need, if anything. “A faculty nudge if there is no answer by Thursday.”
A full example briefExample: a city permit office wait times
1. Project snapshot. We are helping the city permit office cut wait times at the walk-in counter. This week we tested a printed “what to bring” checklist with real applicants.
2. Weekly goals.
- Test the checklist with 10 walk-in applicants.
- Interview 2 counter clerks about rejected applications.
- Draft pilot success measures.
3. What we actually did.
- Tested the checklist with 12 applicants: 9 of 12 arrived with every document.
- Interviewed 1 of 2 clerks. The second moved to Monday.
- Drafted 3 of 4 success measures. The cost measure needs data from the client.
4. Key insights. 7 of 12 applicants were missing the same document, proof of ownership. Clerks said it is the top reason for return visits.
5. Roadblocks or risks. Our client contact is out next week, so pilot approval could slip one week. We asked for a backup approver.
6. Next week’s priorities.
- Move proof of ownership to the top of the checklist (research lead, by Tuesday).
- Finish the second clerk interview Monday.
7. Support needed. Approval from the permit office manager to run a 2-week pilot, by October 20.
Try it: Weekly Brief Builder
Tool · BUAD 497
Weekly Brief Builder
Write your brief in the seven parts Canvas asks for and catch the vague lines before your client does.
- 1Write
- 2Sharpen
- 3Share
Specific lines
Everything to fix
Vague lines are where briefs lose the “meaningful updates” check. A specific line has a number, a name or role, a date, or evidence.
Brief preview
Put it to work: your Weekly Consulting Brief in Canvas
The Weekly Consulting Brief: Goals and Progress Update is due every week in Canvas. In fall it is worth 2 points a week (20 points total). Each one is graded on three things: submitted on time, follows the brief format and gives meaningful updates (not vague statements). In spring it continues as your Weekly Team Consulting Report.
Start from last week
Copy last week’s Next Week’s Priorities into this week’s goals. That keeps your story honest.
Your deliverable: parts 1 and 2: snapshot and 3 to 5 goals.
Report results, not effort
For each goal, write what happened, with a number or evidence. Include misses and why.
Your deliverable: part 3: one specific line per goal.
Pull out the learning
What did you discover, realize or decide? Tie it to evidence.
Your deliverable: part 4: 1 to 3 insights with proof.
Flag risks and make asks
Name the risk, its impact and your response. Make asks specific: who, what, by when.
Your deliverable: parts 5 and 7.
Plan next week and check the page
Give each priority an owner or a day. Run the Brief Builder and fix every flagged line.
Your deliverable: part 6, then a one-page brief uploaded on time.
Why the brief pays off laterYour weekly briefs are your project record
A semester of honest briefs is the raw material for your biggest deliverables:
- HCD Technical Report: the number of interactions and iterations, who participated and what changed after testing.
- Final Prototype Presentation: your testing rounds and decisions in order.
- EUReCA poster and abstract: methods, iterations and limitations stated plainly.
Keep every brief in one shared folder, newest on top.
Before you submitCheck your brief
- [ ] All seven parts are there (Support needed may be blank).
- [ ] Snapshot is 2 to 3 lines and goals are 3 to 5.
- [ ] Every goal has a matching result line, including misses.
- [ ] Every line passes the four specifics test.
- [ ] Each risk says its impact. Each ask says who, what and by when.
- [ ] It fits on one page.
- [ ] If you used AI, it is noted as your course AI policy asks, and no confidential client data went into a public tool.
Go deeper
Back to all BUAD 497 topics · Next: Pitching Your Prototype
In-class team activity · 20 min
Vague Line Hunt
By the end: This week's Weekly Consulting Brief for your client project, drafted, swapped with another team for a vague line hunt, and fixed. Your instructor will give you the password in class.
Part of the Smith GLS human-centered leadership sequence: IB 407, BUAD 317 and BUAD 497, toward the Human Centered Consulting Certificate.
Frequently asked questions
What is a weekly consulting brief?
A weekly consulting brief is a one-page progress update, like the one a consulting firm gives a client. It has seven parts: project snapshot, weekly goals, what we actually did, key insights or learning, roadblocks or risks, next week's priorities and support needed. It should be clear, focused, honest and actionable.
How do you write a good project status update?
Report results, not effort. Copy last week's priorities into this week's goals, then write one line per goal with a number or evidence, including misses and why. Pull out one to three insights tied to proof, flag risks with their impact, and give each next step an owner or a day. Keep it to one page.
What is the four specifics test for a status update?
A strong line in a brief has at least one of four specifics: a number, a name or role, a date, or evidence such as a quote, a count or an artifact. "Worked on interviews" fails the test. "Interviewed 4 of 6 nurses on night shift" passes. If a line has none of the four, rewrite it.
How do you flag a risk in a project update?
Write each risk in four short parts: risk, impact, response and ask. Say what might go wrong, what it puts at risk and by how much, what you are doing now, and what help you need, if any. Flag risks the week you see them. A brief that is always green is a brief nobody trusts.
How is the BUAD 497 Weekly Consulting Brief graded?
In fall, the brief is due every week in Canvas and is worth 2 points a week, 20 points total. Each one is graded on three things: submitted on time, follows the brief format and gives meaningful updates rather than vague statements. In spring it continues as the Weekly Team Consulting Report.