Course Resources

Module 1

I have two CSV files in my workspace folder: sample-settlements-bank.csv and sample-settlements-internal.csv. The first has Settlement_Amount, the second has Recorded_Amount. They should match but some don't. Create an Excel workbook with 3 sheets: Sheet 1 - Matched transactions where amounts are equal. Sheet 2 - Variances where amounts differ, with a Difference column and conditional formatting (RED for >$500 difference, YELLOW for $100-500). Sheet 3 - Summary statistics with formulas for total count, matched count, variance count, total amounts, and net variance. Sort variances by largest difference first.

Module 1

List all files in my workspace folder. For each file, show: filename, file type, size, and number of rows (if CSV). Give me a summary at the end.

Module 1

Look at all the files in my workspace folder. Rename each file with a descriptive name based on its content (e.g., "Q3-settlement-report.xlsx" instead of "Document1.xlsx"). Create subfolders by file type (spreadsheets, documents, presentations, data). Move each file into the right subfolder. When you're done, create an index.md file listing every file, its new name, which folder it's in, and a one-line description of what it contains.

Module 1

I'm pasting notes from a team meeting below. Extract: (1) every decision that was made and who made it, (2) every action item with the owner's name and deadline if mentioned, (3) open questions that weren't resolved, (4) a draft follow-up email summarising the meeting in 5 bullet points — ready to send to attendees. Format as a clean markdown document. Save as meeting-summary.md.

[Paste your meeting notes here]

Module 1

I'm pasting messages from my inbox (emails, Slack messages, or both). For each message, categorise it as: (1) RESPOND NOW — needs a reply today, (2) SCHEDULE — needs action but not today, (3) DELEGATE — someone else should handle this, (4) ARCHIVE — informational only, no action needed. For each RESPOND NOW item, draft a 2-3 sentence reply. For each SCHEDULE item, suggest a deadline. Output as a clean action list sorted by priority.

[Paste your messages here]

Module 1

I'm going on leave. Here are my current open tasks, projects, and responsibilities:

[Paste your task list, open tickets, ongoing projects, and any context]

Create a handoff document with: (1) each item's current status and next step, (2) who to contact if something comes up (suggest based on context), (3) items that can wait vs. items that need coverage, (4) any deadlines that fall during my absence. Format it so a colleague can scan it in 2 minutes and know exactly what's going on.

Module 1

I've drafted an email but it's too long / too blunt / too vague. Here it is:

[Paste your draft email here]

Rewrite it to be: (1) half the length, (2) professional but warm, (3) with a clear ask in the first sentence, (4) no more than 3 paragraphs. If there are multiple asks buried in the email, break them into a numbered list. Keep my meaning — just make it clearer.

Module 1

I'm pasting a Slack thread that got long and messy. Summarise it in this format:

(1) **Decision** — what was actually agreed (if anything). If no decision, say "No decision reached."
(2) **Key points** — the 3-5 most important things said, with who said them.
(3) **Action items** — who committed to doing what, with deadlines if mentioned.
(4) **Open questions** — anything unresolved that still needs an answer.
(5) **One-line TL;DR** — the whole thread in one sentence.

[Paste the Slack thread here]

Module 1

I'm pasting a Jira/helpdesk ticket export (or a list of tickets with subject, status, priority, and created date). Triage them for me:

(1) **Act now** — tickets that are high priority, overdue, or have been open more than 3 days with no response.
(2) **Today** — medium priority tickets that need attention but aren't urgent.
(3) **This week** — lower priority items that can wait.
(4) **Needs info** — tickets where the description is too vague to act on. Draft a quick follow-up question for each.
(5) For each "Act now" ticket, suggest a next step based on the subject line.

Sort by urgency. Save as a triage-plan-[date].md.

[Paste your ticket export here]

Module 1

I have a list of Jira tickets that need status update comments. For each ticket I'll provide: ticket ID, current status, and what happened this week.

For each ticket, draft a professional Jira comment that: (1) states the current status clearly, (2) explains what was done since the last update, (3) lists next steps or blockers, (4) tags anyone who needs to act (I'll fill in the @mentions). Keep each comment under 5 sentences. No corporate fluff.

[Paste your ticket list: ID, status, what happened]

Module 2

I'm pasting a report generated by AI. Review it critically and identify: (1) math errors — re-calculate all totals, (2) classification errors — verify codes match descriptions, (3) overconfident claims — flag assertions not supported by data, (4) missing context — note what additional data is needed. Be thorough and skeptical.

Module 3

I have two CSV files with settlement data. File 1 has Settlement_Amount, File 2 has Recorded_Amount. Create an Excel workbook with 3 sheets: Matched (amounts equal), Variances (amounts differ, with Difference column, RED for >$500, YELLOW for $100-500), Summary (formulas for totals, counts, net variance). Sort variances by largest first.

Module 3

Create a chargeback tracking Excel workbook from my CSV. Add dropdown validation for Card_Scheme and Status columns. Conditional formatting: RED for past deadline, YELLOW for due within 3 days, GREEN for Won, GRAY for Lost. Summary sheet with auto-calculating formulas for totals, win rate, cases by scheme.

Module 3

I'm disputing a chargeback. Here are the details:
- Reason code: [e.g., Visa 10.4 - Fraud, Card Present]
- Transaction amount: [amount]
- Transaction date: [date]
- Evidence I have: [list what you have — receipt, delivery confirmation, AVS match, 3DS authentication, merchant-cardholder communication]

Draft a dispute rebuttal summary (max 1 page) that: (1) states which evidence addresses the reason code, (2) argues why the transaction was legitimate based on the available evidence, (3) identifies what additional evidence would strengthen the case, (4) flags if the evidence is likely insufficient to win. Write it as if it's going on the front page of an evidence PDF submitted to the card scheme.

Be direct. Schemes read hundreds of these — get to the point.

Module 3

Read team notes or process docs. Create a "New Starter Guide" with: what the team does, key processes, tools, jargon glossary, who to ask, first-week checklist. Write like a helpful colleague, not a policy document. Save as DOCX.

Module 3

Read summary data CSV. Create an 8-10 slide quarterly business review: executive summary, trends, breakdown by category, top issues, recommended actions. Speaker notes on every slide. The deck should tell a story, not just show numbers. Save as PPTX.

Module 3

I have receipt photos in my workspace folder (screenshots or photos of receipts). Read each image. For each receipt, extract: date, vendor name, amount, and category (travel, meals, office supplies, software, other). Create an Excel expense report with: Sheet 1 — all expenses sorted by date, Sheet 2 — summary by category with totals, Sheet 3 — any receipts where the amount was unclear or the image was hard to read (flag for manual review). Use formulas for the totals.

Module 3

I have a CSV file with contact details (Name, Company, Email, and a few custom fields) and an email template below. For each row in the CSV, create a personalised version of the template — replacing placeholders with the actual values, and adjusting the opening line to reference their company name naturally. Save all 50 emails as a single Word document with clear separators between each one, ready for me to review and send manually.

[Paste your email template here with {{Name}}, {{Company}} placeholders]

Module 3

I'm pasting this month's chargeback data (or attaching a CSV). Create a scheme compliance report with: (1) chargeback ratio per card scheme (Visa, Mastercard, AMEX) — calculated as chargeback count / total transaction count, (2) comparison vs. previous month (include a Trend column: UP, DOWN, FLAT), (3) threshold breach warnings — flag any scheme where the ratio exceeds: Visa 0.9%, Mastercard 1.5%, (4) breakdown by reason code category per scheme, (5) a 3-line executive summary stating whether we're compliant, which schemes need attention, and recommended actions. Create as an Excel workbook with a Summary sheet and a Detail sheet.

[Paste or attach your chargeback data]

Module 3

I have a list of merchants stuck in onboarding. For each merchant, I'll paste: merchant name, current stage, days waiting, and what's missing (if known).

For each merchant, draft a professional follow-up email that: (1) addresses the merchant by name, (2) states their current onboarding stage in plain English (not internal jargon), (3) lists exactly what they need to submit or do next, (4) gives a clear deadline, (5) offers a contact point for questions. Keep the tone helpful, not bureaucratic. Save all emails in a single Word document, one per page.

[Paste your merchant list here]

Module 3

I'm pasting my team's current workload: each person's name, their current assignments, deadlines, and estimated hours remaining.

Create a capacity analysis with: (1) a heat map view — who's overloaded (>40h/week committed), who has bandwidth (<30h), who's at capacity, (2) deadline conflicts — tasks due the same week that share a person, (3) items at risk of slipping based on hours remaining vs. time available, (4) suggested rebalancing — which tasks could shift to someone with bandwidth. Create as an Excel workbook. Be honest if the data is too vague to draw conclusions.

[Paste your team workload here]

Module 3

I'm pasting a Slack thread (or email chain, or voice note transcript) where someone explained how a process works. It's informal and scattered, but the knowledge is in there.

Turn this into a formal Standard Operating Procedure (SOP) document with: (1) Purpose — what this process achieves in one sentence, (2) Scope — who does this and when, (3) Prerequisites — what you need before starting, (4) Step-by-step instructions — numbered, specific, no ambiguity, (5) Decision points — where judgment is needed and what to consider, (6) Escalation — when to stop and ask someone, (7) Common mistakes — things that go wrong based on what was mentioned.

Format as a Word document. Flag any steps where the original explanation was vague — mark them with [NEEDS CLARIFICATION] so the team can fill in the gaps.

[Paste the informal explanation here]

Module 3

I have a messy CSV (or spreadsheet data) with inconsistent formatting. Clean it up:

(1) **Names** — standardise capitalisation (Title Case for company names, consistent format for person names).
(2) **Dates** — convert all dates to YYYY-MM-DD format regardless of input format.
(3) **Phone numbers** — standardise to international format (+44..., +1...).
(4) **Duplicates** — flag rows that look like duplicates based on name + email (or name + company). Don't delete them — just add a "Possible_Duplicate" column.
(5) **Blanks** — flag rows with missing critical fields (email, company name, or whatever I specify as required).

Create a clean CSV and a separate "Cleaning Report" listing every change made, so I can verify nothing was mangled.

[Paste or attach your messy data]

Module 3

I need a market research brief on: [topic / market segment / competitor / trend].

Create a structured research document with: (1) Overview — what is this market/topic and why it matters, (2) Key players — the main companies or products in this space with a one-line summary of each, (3) Trends — what's changing right now (last 12 months), (4) Opportunities — where there might be gaps or underserved needs, (5) Risks — what could go wrong or what to watch out for, (6) Relevance to us — how this connects to a payments/FinTech business specifically.

Use publicly available information only. Flag anything you're uncertain about with [VERIFY]. Keep it under 3 pages — this is a brief, not a thesis.

Module 4

Read jira-export-sample.csv and merchant-risk-profiles.csv from my workspace. Cross-reference: for each Jira issue mentioning a merchant, add the merchant's Risk_Level and Alert_Count from the risk profiles. Create an Excel output sorted by Risk_Level descending. Flag HIGH/CRITICAL merchants with open issues.

Module 4

Read jira-export-sample.csv. Group issues by Status and Priority. Show: total count, blocked issues (with what's blocking them), critical/high priority items needing attention. Format as a scannable briefing.

Module 4

I have a meeting in 30 minutes. Below are: (1) the agenda, (2) notes from the last meeting on this topic, and (3) any relevant data or context. Create a 1-page pre-meeting briefing with: key context I need to remember, decisions that need to be made in this meeting, suggested positions on each decision with brief reasoning, questions I should ask, and any risks or concerns to raise. Keep it scannable — I'll read this in the lift on the way to the meeting room.

[Paste agenda, previous notes, and context here]

Module 4

I'm pasting a chat thread where our team discussed a process change. It got messy. Extract the following: (1) What was ultimately decided — the final outcome, not the debate. (2) Who made the final call (or if it was a group consensus). (3) What alternatives were considered and why they were rejected. (4) Any caveats or conditions attached to the decision. (5) Next steps and who's responsible. Format as a clean "Decision Record" document with date, participants, and a clear structure. Save as decision-log.md.

[Paste the chat thread here]

Module 4

I'm pasting notes from a meeting. Extract three things:

(1) **Decisions made** — what was agreed, stated as facts.
(2) **Action items** — who owns what, with deadlines if mentioned.
(3) **Draft Jira tickets** — for each action item, draft a ticket with: Title (imperative verb + what), Description (context from the meeting + acceptance criteria), Priority (suggest based on urgency language used), and Assignee (from the action item owner).

Format decisions and action items as a summary at the top. List draft tickets below, ready to copy-paste into your issue tracker.

[Paste your meeting notes here]

Module 4

I have merchants with incomplete CDD/KYC documentation. For each merchant below, I'll list: name, what documents are missing, and how many days overdue.

For each merchant, draft a follow-up email that: (1) addresses them by name, (2) explains which documents are still needed in plain language (not compliance jargon), (3) states the consequence of not submitting (e.g., settlements remain on hold), (4) provides a clear deadline, (5) keeps a professional but firm tone — this is a compliance requirement, not a request. Save as a Word document, one email per page.

[Paste your merchant list: name, missing docs, days overdue]

Module 4

I'm pasting a policy document (compliance policy, HR policy, security policy, or similar). It's dense and nobody on my team will read the whole thing.

Create two outputs: (1) A **1-page plain-English summary** — what the policy requires in simple language. No jargon. Written for someone who needs to follow the rules but doesn't need to know the legal reasoning. (2) A **Quick Reference Card** — a bullet-point checklist of the 5-10 things my team actually needs to DO differently because of this policy. Format as: "DO: [action]" and "DON'T: [action]."

Flag anything in the policy that's ambiguous or could be interpreted multiple ways — mark it [ASK COMPLIANCE].

[Paste the policy document here]

Module 4

I'm evaluating tools/vendors for [purpose]. Here's what I know about each option:

[Paste info about each vendor: name, pricing, features, pros, cons, notes from demos]

Create an Excel workbook with: (1) Sheet 1 — Comparison matrix: rows = criteria (price, features, integrations, support, security, scalability), columns = vendors. Score each 1-5 with a brief justification. (2) Sheet 2 — Pros/cons summary per vendor in plain English. (3) Sheet 3 — Recommendation: rank the vendors with reasoning. Flag any criteria where I don't have enough info to score — mark as [NEED MORE INFO].

Be honest — if two vendors are basically the same, say so.

Module 5

Read my chargeback export CSV. For each open case, match to reason code category and draft a rebuttal outline with required evidence types. Flag URGENT deadlines. Create Excel with cases, outlines, and priority recommendations.

Module 5

Read 50 resolved helpdesk tickets. Identify the top 10 recurring questions. Draft a knowledge base article for each with title, steps, and when to escalate. Flag contradictory resolutions. Estimate ticket deflection per article.

Module 5

Read CRM deals export. For each competitor, create a 1-page battle card: strengths, weaknesses, common objections, suggested opening lines. Rank competitors by total deal value at stake.

Module 5

I'm about to call a merchant who wants to cancel (or reduce their plan). Here's what I know:
- Monthly transaction volume: [amount]
- Current pricing: [rate]
- How long they've been a customer: [months]
- Reason for cancellation request: [stated reason]
- Competitor they're considering: [if known]

Create a 1-page save-call brief with: (1) 3 retention talking points based on their usage and tenure, (2) what pricing flexibility I might have (based on their volume tier), (3) competitor comparison points (publicly known differences), (4) suggested opening line that acknowledges their frustration without being defensive. Keep it practical — I'm reading this 2 minutes before the call.

Module 5

Cross-reference AML alerts with merchant profiles. Pre-categorise as FALSE POSITIVE, NEEDS REVIEW, or ESCALATE. Draft escalation summaries. Calculate false positive rate and risk statistics.

Module 5

I have a file with customer feedback (survey responses, NPS comments, or support feedback). Read all entries. Identify: (1) the top 5 most common themes — what are people actually talking about? (2) the top 3 things customers love — direct quotes where possible, (3) the top 3 complaints or frustrations — with frequency count, (4) any emerging issues mentioned by 3+ people that weren't in previous reports, (5) a 1-page executive summary with recommended actions. Create a Word document. Include a "quotable quotes" appendix with the most vivid customer comments (anonymised).

Module 5

I'm pasting our team's list of software subscriptions and tools (name, cost per month, number of users, what it's used for). Analyse the list and identify: (1) tools with overlapping functionality (e.g., two project management tools), (2) tools with very few active users relative to licences paid for, (3) tools that could potentially be replaced by features in other tools we already have, (4) estimated annual savings if we consolidated or cancelled the flagged items. Create an Excel workbook: Sheet 1 — full audit with recommendations per tool (keep/review/cancel), Sheet 2 — savings summary. Be specific about which tools overlap with which.

[Paste or attach your subscription list]

Module 5

I'm pasting the Slack thread (or incident log) from a recent incident. Create a structured post-mortem document with:

(1) **Timeline** — what happened, when, in chronological order.
(2) **Root cause** — what actually broke (be specific, not "human error").
(3) **Impact** — who was affected, for how long, what was the business impact.
(4) **What went well** — response actions that worked.
(5) **What didn't go well** — where the response was slow, confusing, or wrong.
(6) **Action items** — specific fixes to prevent recurrence, with suggested owners.

Keep it factual, not blame-y. Format as a Word document ready for team review.

[Paste the incident thread here]

Module 5

I have a sales call in 30 minutes. Here's what I know about the prospect:
- Company: [name]
- Industry: [sector]
- Size: [employees or revenue range]
- Current provider: [competitor, if known]
- Deal stage: [where we are in the pipeline]
- Notes from previous contact: [any context]

Create a 1-page call prep brief with: (1) company context — what they likely care about based on their industry and size, (2) 3 qualifying questions I should ask (tailored to their situation, not generic), (3) likely objections and how to handle them, (4) competitive positioning vs. their current provider (based on publicly known differences), (5) suggested call agenda (keep it to 3 items max). Write it so I can scan it in 2 minutes.

Module 5

I have a 1:1 with a team member in 30 minutes. Here's what I know about their recent work:

[Paste: their completed tickets/tasks this week, any blockers mentioned, feedback from others, upcoming deadlines]

Create a 1:1 prep sheet with: (1) **Wins to acknowledge** — specific things they did well (be concrete, not generic), (2) **Check-ins** — things to ask about based on their current workload, (3) **Growth areas** — one development topic to raise based on patterns in their work, (4) **Blockers to unblock** — anything I can help clear, (5) **One question to ask** — something that shows I'm paying attention.

Keep it to half a page. I'll read this walking to the meeting room.

Module 5

I'm interviewing for this role: [title, team, level]. The key competencies we need are: [list 3-5 skills or traits, e.g., "cross-team collaboration, attention to detail under pressure, experience with regulated environments, clear written communication"].

Generate 10 behavioral interview questions that: (1) target these specific competencies (2-3 questions per competency), (2) use the "Tell me about a time when..." format, (3) include a follow-up probe for each question to go deeper, (4) avoid generic questions that any candidate could answer with a rehearsed story. Include a scoring rubric: what a strong answer looks like vs. a weak one for each question.

Module 5

I'm describing how my team currently handles [process name]. Here's how it works today:

[Describe the process: who does what, in what order, using which tools, how long each step takes, where things get stuck]

Audit this process and identify: (1) **Manual steps** that could be automated or eliminated, (2) **Bottlenecks** — steps where work piles up or waits, (3) **Redundancies** — places where the same information is entered/checked twice, (4) **Handoff risks** — where work passes between people/teams and context gets lost, (5) **Quick wins** — 3 things that could be improved this week with minimal effort. For each finding, explain WHY it's a problem and suggest a specific fix.

Module 5

I need to announce the following to my team / department / company:

[Describe: what's changing, why, who's affected, when it takes effect, what people need to do]

Draft an internal announcement that: (1) leads with what's changing and why (not background/history), (2) clearly states what people need to DO (if anything), (3) acknowledges concerns people might have, (4) provides a contact point for questions, (5) keeps a [professional / warm / direct / reassuring] tone. Keep it under 300 words. People will skim this — make the first sentence count.

Module 6

Check my Jira board and create a Monday morning briefing. For each issue assigned to me or updated since last Friday: list key, summary, status, priority. Group into URGENT, IN PROGRESS, UPCOMING, COMPLETED. Save as monday-briefing-[date].md.

Module 6

Check the chargeback cases file. Create a deadline alert: OVERDUE (past deadline), URGENT (0-2 days), THIS WEEK (3-7 days). Include case ID, merchant, amount, days remaining. Save as chargeback-deadlines-[date].md.

Module 6

Read screening-alerts-export.csv from my workspace (this week's exported alerts). Create a compliance briefing: (1) alerts by category (sanctions, PEP, adverse media) with counts, (2) merchants approaching periodic review deadlines in the next 30 days, (3) any ESCALATE-level items from last week still unresolved, (4) a 3-line summary of this week's risk landscape. Save as compliance-weekly-[date].md.

Module 6

Query Jira: issues completed this week, still in progress, blocked, and new. Show counts and lists. Format as stakeholder update for Slack/email. Save as sprint-summary-[date].md.

Module 6

Read the helpdesk export CSV from the past 30 days. Identify: (1) merchants whose ticket volume increased significantly vs the previous period — early warning signs, (2) merchants whose ticket volume dropped to zero — possible churn risk or happy customer, (3) the top 3 emerging issue types that weren't in the top 10 last month — new problems brewing, (4) merchants with zero tickets for 6+ months who suddenly filed 3+ — something changed. Create a 1-page trend report as a Word document with recommended actions for each finding.

Module 6

I have an export of our wiki pages (title, last updated date, author, page views). Analyse the list and identify: (1) pages not updated in over 6 months — likely stale, (2) pages with very similar titles that might be duplicates, (3) pages with zero views in the last 90 days — probably forgotten, (4) pages by authors who have left the company — may need a new owner. Create an Excel workbook: Sheet 1 — full audit with a recommended action per page (keep, update, archive, merge, delete), Sheet 2 — priority cleanup list (top 20 pages to fix first). Save as wiki-audit.xlsx.

Module 6

I'm pasting my calendar for this week (or exporting it as CSV). Analyse it and tell me: (1) total hours in meetings vs total working hours — what percentage of my week is meetings? (2) back-to-back meetings with no break — flag these, (3) longest block of uninterrupted focus time available, (4) meetings that could potentially be async (status updates, FYI-only topics), (5) suggested reschedule plan to protect at least 2 hours of focused work per day. Format as a 1-page "Calendar Health Check" document.

[Paste or attach your calendar export]

Module 6

Read merchant-activity-export.csv from my workspace (this week's transaction and support data per merchant). Create a merchant health report with:

(1) **Volume changes** — merchants whose transaction volume changed by more than 20% vs. the previous period (up or down). Flag direction and magnitude.
(2) **Gone quiet** — merchants with zero transactions in the last 7 days who were previously active. Possible churn risk.
(3) **Support spikes** — merchants who filed 3+ support tickets this week when their average is 0-1. Something may have broken.
(4) **New and thriving** — merchants onboarded in the last 30 days who are already transacting above average. Good news worth knowing.

Save as merchant-health-[date].md. Keep it scannable — one section per category, sorted by severity.

Module 6

I'm pasting my team's standup notes and Slack highlights from this week. Create a "Weekly Wins" report with:

(1) **Shipped** — things that went live or got completed this week.
(2) **Unblocked** — issues that were stuck and are now moving again.
(3) **Key numbers** — any metrics mentioned (tickets resolved, deals closed, cases processed) — pull them into a summary table.
(4) **Shout-outs** — anyone mentioned positively by name for going above and beyond.
(5) **Next week** — carry-over items and upcoming deadlines.

Format as a clean document I can paste into Slack or email to my skip-level. Keep it under 1 page.

[Paste this week's standup notes and highlights]

Module 6

I'm pasting a process document / policy / runbook that my team needs to know. Create a training quiz with:

(1) 10 multiple-choice questions that test understanding (not just recall — include scenario-based questions).
(2) For each question: the correct answer and a brief explanation of WHY it's correct.
(3) 3 "what would you do?" scenario questions where the person has to apply the knowledge to a realistic situation.
(4) An answer key at the end.

Make the questions tricky enough that someone who just skimmed the document would get some wrong. The goal is learning, not easy passes.

[Paste the document here]

Module 6

Here's my context for next quarter's goal-setting:
- Last quarter's results: [what we achieved, what we missed, key metrics]
- Company/department priorities for next quarter: [themes, focus areas, strategic bets]
- My team's capacity: [team size, any hiring/departures, major projects already committed]

Draft 3-5 quarterly goals (OKRs or equivalent) that: (1) connect to the company priorities, (2) are specific and measurable (not "improve quality" — what metric, by how much?), (3) are realistic given the team's capacity, (4) include one stretch goal that's ambitious but not impossible. For each goal, suggest 2-3 key results that would prove it's been achieved.

Module 6

Read the following files from my workspace: [list your weekly exports — e.g., jira-export.csv, tickets-resolved.csv, team-updates.txt].

Create a weekly status report with: (1) **Highlights** — top 3-5 things accomplished this week, (2) **Metrics** — key numbers in a summary table (tickets resolved, cases closed, deals progressed — whatever applies), (3) **Blockers** — anything stuck and what's needed to unblock, (4) **Next week** — top priorities for the coming week, (5) **Risks** — anything the reader should know about.

Format for Slack (scannable, with bold headers). Keep it under 20 lines — if someone can't read it in 60 seconds, it's too long. Save as weekly-status-[date].md.