weekly-reportlisted

# Weekly report Produce a one-page report a manager can read in two minutes and act on. ## Inputs - A CSV or XLSX file. Typical columns: date, person or team, client or project, a numeric measure (hours, amount, units), optional status or category. - Optional: the previous week's file, targets or budgets. If the columns are ambiguous, state your interpretation in one line under **Assumptions**. Do not stop to ask unless no numeric column exists. ## Steps 1. **Load and check the data.** Report the row count, date range and any rows you excluded (empty values, duplicates, dates outside the week). Never silently drop rows. 2. **Compute with code, not by eye.** Use a script to calculate totals by person, by client or project, and by day. If a previous week is provided, compute changes in absolute and percentage terms. 3. **Find anomalies.** Flag: - any person or project more than 25% above or below its usual share or target - days with no records - single entries larger than 3x the median entry - billable versus non-billable imbalance, if that column exists 4. **Write three insights.** Each one states what happened, why it matters (money, time or risk), and one concrete next step with an owner if known. 5. **Write the report** using the template below. Keep it to one page. ## Template ```markdown # Weekly report · [week dates] ## Summary [Two sentences: the headline number and the most important change.] ## Totals | Measure | This week | Previous | Change |