{"id":"res-mgr-shipping-delay-timeline","audience":"managers","category":"research","technique":"grounding","title":"Build a sourced timeline of a shipping delay from team emails","free":false,"task":"Your director wants a timeline of last Tuesday's shipping delay at the warehouse. You want exactly 5 numbered lines in time order, each \"time - what happened (source)\", using the corrected time where someone fixed an earlier email. Use only events stated in the messages, skip guesses and rumors, and write plain text with nothing else.","materialLabel":"Messages about the delay (attached to your prompt automatically)","material":"Tues Oct 27 - messages collected for the delay review\n\nEMAIL, Rosa Diaz (shift lead), 6:52 a.m.: \"Conveyor belt 3 jammed at 6:40. Maintenance called.\"\nTEXT, Dev Patel (maintenance), 7:15 a.m.: \"On site. Belt 3 motor is burned out, need a replacement part.\"\nEMAIL, Rosa Diaz, 8:05 a.m.: \"We started rerouting outbound boxes to belt 1 at 7:30, slower but moving.\"\nEMAIL, Rosa Diaz, 8:20 a.m.: \"Correction: rerouting started at 7:45, not 7:30. Sorry.\"\nSLACK, Jamal (picker), 9:10 a.m.: \"heard the part supplier is the same one that messed up last month, typical\"\nEMAIL, Dev Patel, 11:30 a.m.: \"Replacement motor arrived at 10:50 and is installed. Belt 3 back up at 11:20.\"\nEMAIL, Carrie Wong (dispatch), 2:00 p.m.: \"Missed the 12:00 carrier pickup for 46 orders. They'll go out on tomorrow's 8 a.m. truck.\"\nSLACK, Jamal, 2:15 p.m.: \"pretty sure this happened because nobody did the weekly belt check\"","rules":[{"type":"numberedItems","count":5},{"type":"plainText"}],"mistakes":[{"title":"Using the first time given","why":"The 7:30 email comes first, and the AI may miss the correction 15 minutes later.","fix":"Say: \"Where someone corrects a time, use the corrected time.\"","checks":["r0"]},{"title":"Treating rumors as events","why":"The Slack guesses read like explanations, and the AI may add them to the timeline or a cause section.","fix":"Add: \"Only events stated as fact. Skip guesses and rumors.\"","checks":["r1"]},{"title":"Getting a full incident report","why":"The AI adds causes and fixes you didn't ask for, and the director just wants the timeline.","fix":"Say: \"Output only the 5 lines.\"","checks":["r2"]},{"title":"Not saying how many","why":"The AI decides the length itself and usually returns more lines in time order than you can use.","fix":"Be exact: \"exactly 5 numbered lines in time order.\"","checks":["numberedItems"]},{"title":"Getting markdown back","why":"AI defaults to bold labels and headings, which show up as stray symbols in an email to your director.","fix":"Ask for \"plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Handles the correction","patterns":["correct","7:45","fixed"]},{"label":"Skips rumors","patterns":["rumor","guess","speculat","only (events|facts)"]},{"label":"Asks for sources","patterns":["source","who (said|sent)","\\(source\\)"]},{"label":"Says exactly how many","patterns":["\\b(5|five)\\b.{0,25}(line|event)","exactly \\d+"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"A timeline is only useful if every line can be traced and trusted. Tell the AI to cite each message, use corrections, and leave out guesses.","rubricLabels":["Includes these events in time order: belt 3 jammed at 6:40, rerouting to belt 1 started at 7:45 (the corrected time, not 7:30), belt 3 back up at 11:20, and 46 orders missed the 12:00 pickup","Each line names its source person or message, and no line states Jamal's guesses (the supplier or the missed belt check) as events","Outputs only the 5 numbered lines: no intro, no root-cause analysis, no recommendations"]}