SAMPLE DATA. FICTIONAL COMPANY. NOT REAL.

A real Claude reply to the clean-up prompt (ps-prompt-021), after the interview, with late-po-tally-week-46.xlsx attached. Your wording will differ. The answer and the reasons should not.

I read the tally (week of 11/9). It replaces your guess of 30 a week: **12 chases, 235 minutes (3.9 hours)**. The file is labeled "SAMPLE DATA", so I treated it as your count. It also shows that **5 of the 12 chases (80 minutes, 34%) did no good**:
- 3 chases (50 minutes) were for material already on the dock.
- 2 chases (30 minutes) were repeats with the same date.

## What I decided, step by step

| Today's step | Decision |
|---|---|
| 1. Hector asks where it is | **Move.** The morning past-due report starts the work, not a person asking. 10 of 12 chases started with someone asking. |
| 2. Look up PO in ShopLine | **Keep.** The report lists it, so no one looks it up. |
| 3. Open hot list | **Combine.** The shared chase log is the work list, so there is no separate check. |
| (new) Check the dock first | **Add, before any chase.** This catches the 3 wasted chases. |
| 4. Email supplier | **Keep.** The wording and the contact are written down. |
| 5. Wait for a reply | **Keep.** The wait is a written rule, not a memory. |
| 6. Call the supplier | **Keep.** The call rule is written per supplier. |
| 7. Type the date into the hot list | **Drop.** The date lives in ShopLine only. The log holds chase history, not dates. |
| 8. Email Hector the date | **Drop.** He reads ShopLine. |
| 9. Update ShopLine (skipped on 40207) | **Move up and merge into the call.** The chase isn't done until the date is in ShopLine. This is the fix for the miss. |
| 10. Tell Ray on Teams | **Drop.** He reads ShopLine. |
| 11. Nobody says it arrived | **Fix.** Receiving enters the receipt the same day, so the PO leaves the report. |

Other fixes:
- **Repeat chases:** the log has a "next chase day" column, so a PO isn't chased twice for the same date.
- **Unknown Red Creek address:** the contact list is kept with the log.
- **Three jobs slipped while you were out:** the backup runs the same morning report from the same log.

# The fixed version

**Starts when:** the morning past-due report in ShopLine lists a PO.
**Done when:** the material is on our dock, or ShopLine shows a new date the planner can see.

**Steps**
1. **Dana** runs the past-due report in ShopLine each morning.
2. **Dana** checks the chase log (not chased since the promised date?) and the dock (already here?). If it's here, she marks it received in ShopLine and stops.
3. **Dana** chases by the rules below, by email or phone, and logs the day, the person, and the way.
4. **Dana** types the new date into ShopLine before the next PO, then marks "ShopLine updated" in the log.
5. **Hector and Ray** read the date in ShopLine. Nobody emails or messages dates.
6. **Receiving** enters the receipt in ShopLine the day material lands, and the PO drops off the report.

**What we dropped, and why**
- Walk-ups and Teams as the trigger: the report starts the work.
- Hot list date and email to Hector: the date has one home, ShopLine.
- Teams replies to Ray: he reads ShopLine.
- Re-asking with no new date: it was 2 of 12 chases.
- Chasing material on the dock: it was 3 of 12 chases.

**Rules, written down**
- Chase when the PO is on the report and not chased since its promised date. Chase once per promised date. Chase again the morning after a new date passes.
- Message: PO number, part, quantity, date we needed it.
- **Red Creek:** email. No reply by noon the next day, call Marco at the order desk.
- **Cedar Flats:** call the counter.
- **Panhandle:** email, and copy their salesman on the follow-up. Don't call, they never pick up.
- Other suppliers: blank. Dana adds each one as she chases it.
- *Proposed, Dana to confirm:* POs with a job waiting go first, then oldest promised date.
- *Proposed:* no date by the second morning, tell the planner "no date yet."

**Who covers when the owner is out:** Kevin, who covered in October. He gets the log, the contact list, and these rules, plus ShopLine access. He runs steps 1 to 4 each morning.

**Before and after**

| | Before | After |
|---|---|---|
| Steps | 11 | 6 |
| Handoffs (information moves person to person) | 6 | 2 |
| Places the new date is kept | 4 (ShopLine, hot list, email to Hector, Teams to Ray) | 1 (ShopLine) |
| Places chase history is kept | 2 (hot list, your head) | 1 (shared log) |

**Open items:** who at receiving enters receipts, who at Red Creek gets the email, whether Hector and Ray can open ShopLine, and whether ShopLine has a notes field. If it does, the log can live there too.

# Automation check

1. **Still needed after the clean-up? Yes.** Late material still holds up jobs, and three slipped in October.
2. **Information has one home? No.** The date is in four places today, and ShopLine still showed 11/6 on 40207.
3. **Clear trigger? No.** 10 of 12 chases began with someone walking over or messaging.
4. **Rule written down? No.** The supplier rules live in your head and on your desktop.
5. **One named person owns it? No.** You do the work, but no one has been named owner or backup.
6. **Often enough to be worth it? Yes.** It happens 12 times a week and takes 3.9 hours. That is one week's count, so a second tally would firm it up.

**Automate now: no.** The to-do list is checks 2, 3, 4, and 5:
- Move the date to ShopLine only.
- Start using the morning report.
- Put the rules in writing.
- Have the person who assigns the work name an owner.

The new version doesn't count until it has run for two weeks. If you start Monday 11/23, run the check again **Monday 12/7**, and keep a second tally so you can compare it to 12 chases and 235 minutes.
