{"id":"cx-p1-comms-clock-table","audience":"operations","category":"support-work","technique":"constraints","track":"support","level":"advanced","title":"Build a P1 communications timetable from the incident clock","free":false,"task":"The P1 was declared at 14:20. Output a table with the header \"Time | Action | Owner\", one row per required communication in time order, using the rules below and 24-hour clock. Cover only the first 3 hours (until 17:20). Then add a last line \"Next due: HH:MM\". Plain text, under 110 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"P1 COMMS RULES\n- Support lead briefs the agents within 10 minutes of declaration.\n- Executive ping (one message to the exec channel) within 15 minutes of declaration.\n- First public status post within 30 minutes of declaration.\n- After the first post, a public update every 60 minutes while the incident is open, even if there is nothing new.\n- Key accounts (the 12 on the VIP list) get a direct email within 45 minutes of declaration, from their account manager.\n\nOWNERS\nSupport lead: agent brief. Incident commander: exec ping and public posts. Account managers: VIP emails.\n\nINCIDENT STATE AT 15:45\nStill open. All items due up to 15:45 are done except the VIP emails, which are in progress.\n\nNOTE: the first public post went out at 14:48.","rules":[{"type":"plainText"},{"type":"maxWords","max":110}],"mistakes":[{"title":"Timing updates from declaration","why":"The AI uses 15:20 and 16:20 for hourly updates.","fix":"Say: \"Hourly updates count from the first public post at 14:48.\"","checks":["r1","r2"]},{"title":"Missing a communication","why":"The AI forgets the VIP emails or the agent brief.","fix":"List all five rules and ask for one row each.","checks":["r0"]},{"title":"Wrong next due","why":"The AI picks 15:20 or lists a done item.","fix":"Say: \"Next due is the next item after 15:45.\"","checks":["r2"]},{"title":"Table plus chatter","why":"The AI adds explanatory prose.","fix":"Say: \"Table and the last line only.\"","checks":["maxWords"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]}],"promptHints":[{"label":"Gives the table header","patterns":["time \\| action \\| owner"]},{"label":"Counts hourly updates from the first post","patterns":["14:48","first (public )?post"]},{"label":"Asks for a Next due line","patterns":["next due"]},{"label":"Limits the window","patterns":["17:20","3 hours","three hours"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"Give the header, tell it which clock the hourly updates run from, and ask for the last line.","rubricLabels":["The table has the header \"Time | Action | Owner\" and rows in time order including the agent brief (14:30), exec ping (14:35) and VIP emails (15:05)","Public updates are timed from the actual first post at 14:48, giving 15:48 and 16:48 as the hourly updates (the first post itself at 14:48 may be listed), and nothing after 17:20","The last line is \"Next due: 15:48\" (the hourly update after the 15:45 time of the state)"]}