{"id":"exec-calendar-triage-priority-table","audience":"executive-assistants","category":"leadership-work","track":"leadership","level":"intermediate","technique":"constraints","title":"Triage meeting requests against your executive's rules in a table","free":false,"task":"Apply your executive's calendar rules to the six requests below. Output a markdown table with columns Request, Priority (P1, P2 or P3), Action (accept, decline or propose time) and Reason (under 10 words, naming the rule). Mark every decline as \"draft only - needs approval\" in the Action column. Use only the rules and the facts given.","materialLabel":"Rules and requests (attached to your prompt automatically)","material":"Executive: Rhea Okafor, CFO. Week of Nov 11.\n\nRULES (Rhea's, updated Nov 4)\nR1. Board and audit committee items are P1, always accept.\nR2. No meetings Tuesday mornings (deep work) or after 4 pm Fridays.\nR3. External vendor pitches are P3; decline unless a contract expires within 60 days.\nR4. Direct reports' 1:1s are P2; keep them weekly.\nR5. Max 4 meetings per day.\n\nREQUESTS\na. Audit committee prep, Wed Nov 13 at 10:00.\nb. Vendor pitch from DataLynx (current contract ends Mar 31), Thu Nov 14 at 2:00.\nc. 1:1 with Jorge (direct report), Tue Nov 12 at 9:00.\nd. Sales kickoff dinner, Fri Nov 15 at 5:00 pm. The CEO will attend.\ne. Vendor pitch from FormFlow (no current contract), Wed Nov 13 at 3:00.\nf. Rhea's calendar already has 4 meetings on Thu Nov 14. Request b would be the fifth.\n\n(Old rule R3 said 90 days; it was shortened to 60.)","rules":[{"type":"maxWords","max":190}],"mistakes":[{"title":"Wrong table","why":"The AI invents columns or skips the priority labels.","fix":"Say: \"Columns exactly: Request, Priority, Action, Reason.\"","checks":["r0"]},{"title":"Using the old 90-day rule","why":"The AI accepts DataLynx because 90 days applies.","fix":"Say: \"The vendor rule is 60 days.\"","checks":["r2"]},{"title":"Acting without approval","why":"The AI says 'declined' as if sent.","fix":"Say: \"Mark every decline as 'draft only - needs approval'.\"","checks":["r1"]},{"title":"Missing a rule","why":"The AI misses the Tuesday-morning or Friday rule.","fix":"Say: \"Check every request against R1 to R5.\"","checks":["r2"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each reason: \"each reason under 10 words.\"","checks":["maxWords"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each part instead, for example: \"each line under 12 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Names columns","patterns":["request","priority","action","reason"]},{"label":"Gives the choices","patterns":["p1","p2","p3","accept"]},{"label":"Flags approvals","patterns":["needs approval","draft only"]},{"label":"Cites rules","patterns":["rule","r\\d"]},{"label":"Uses updated rule","patterns":["updated","60 days","latest"]}],"hint":"Name the columns and allowed values, the approval label, and ask it to cite the rule.","rubricLabels":["The output is a markdown table with columns Request, Priority, Action and Reason, with rows a to e","Row a is P1 accept, row c proposes another time (Tuesday morning rule) and row e is a P3 decline marked \"draft only - needs approval\"","Row b (vendor with a contract ending in more than 60 days) and row e (no contract) are declines, and every row whose Action is a decline is marked \"draft only - needs approval\"; row d (Friday after 4 pm) is not simply accepted"]}