{"id":"res-off-parking-survey-final-results","audience":"office","category":"research","technique":"audience","title":"Summarize final parking survey results for an all-staff email","free":false,"task":"You're writing the parking survey update for the \"Facilities Corner\" slot in Friday's staff newsletter, so it needs no subject line, greeting or sign-off. You want at most 3 sentences in plain text that give the final results (not the early count), name the top request, and mention the Nov 18 meeting. Use only the survey report, and don't promise any changes the report doesn't announce.","materialLabel":"The survey report and an early-results email (attached to your prompt automatically)","material":"EARLY RESULTS (email from Facilities, Oct 14, after 2 days):\n\"Wow, 70% say parking is a daily problem! 40 responses so far. More soon.\"\n\n-----\nFINAL REPORT - Staff Parking Survey (Facilities, Oct 31, 2026)\nResponses: 212 of 340 staff (62%)\n- Parking is a problem at least 3 days a week: 46%\n- Arrive before 8 a.m. to get a spot: 38%\n- Would use a shuttle from the overflow lot on Dalton Street: 57% (top request)\n- Would carpool if given priority spots: 29%\n- Would pay $20/month for a reserved space: 18%\nFacilities will share next steps after reviewing the results.\n\n-----\nMy notes: Lots of people are mad. Rumor is they're going to start charging for parking? Keep it short, people don't read long emails.","rules":[{"type":"maxSentences","max":3},{"type":"plainText"}],"mistakes":[{"title":"Using the early numbers","why":"The 70% figure is dramatic and appears first, so the AI may lead with it.","fix":"Say: \"Use only the final Oct 31 report.\"","checks":["r0"]},{"title":"Passing on the rumor","why":"Your notes mention a rumor about charging, and the AI may mention it to address staff concerns.","fix":"Add: \"Don't mention rumors or promise changes.\"","checks":["r1"]},{"title":"Writing a whole email","why":"The AI adds a subject line, a greeting and a sign-off, which don't belong in a newsletter slot.","fix":"Say: \"This goes in a newsletter slot: no subject, greeting or sign-off.\"","checks":["r2"]},{"title":"Leaving out what's next","why":"The AI summarizes numbers and forgets the meeting where staff can weigh in.","fix":"Add: \"Name the top request and the Nov 18 meeting.\"","checks":["r1"]},{"title":"Not capping the length","why":"The AI writes several paragraphs by default, far more than the reader will take in.","fix":"Say: \"at most 3 sentences.\"","checks":["maxSentences"]},{"title":"Getting markdown back","why":"AI defaults to bold labels and headings, which show up as stray symbols in an all-staff email.","fix":"Ask for \"plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Uses the final report","patterns":["final","oct(ober)?\\.? 31","not the early","ignore.{0,20}early"]},{"label":"Mentions what's next","patterns":["nov(ember)?\\.? 18","meeting"]},{"label":"Rules out rumors and promises","patterns":["rumor","(don't|do not) promise","no promises"]},{"label":"Caps the number of sentences","patterns":["\\d+\\s*sentences","(two|three|four|five) sentences","sentence"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"Early numbers and rumors travel fast. Tell the AI which results are final, what staff should know next, and what not to say.","rubricLabels":["Uses the final results (212 responses and/or 46% say parking is a problem at least 3 days a week), not the early 70% from 40 responses","Names the shuttle from the Dalton Street overflow lot (57%) as the top request, mentions the Nov 18 meeting, and does not promise changes or repeat the charging rumor as fact","Has no subject line, greeting (like 'Hi all') or sign-off, and no headings or bullet list"]}