{"id":"res-sales-rfp-must-requirements","audience":"sales","category":"research","technique":"grounding","title":"List the mandatory RFP requirements with section numbers","free":false,"task":"You're deciding whether to bid on a county RFP for staff scheduling software. You want exactly 5 numbered lines, one per mandatory requirement (the \"must\" items only, not \"should\" or \"may\"), each under 15 words and ending with its section number. Apply Addendum 1 where it changes a requirement, use only the RFP text, and output nothing else in plain text.","materialLabel":"RFP excerpt and Addendum 1 (attached to your prompt automatically)","material":"RFP #2026-114 - Workforce Scheduling System, Harlan County (excerpt)\n\n3.1 The vendor must host the system in data centers located in the United States.\n3.2 The system should integrate with the county's existing payroll provider.\n3.3 The vendor must provide 24/7 phone support for critical outages.\n3.4 The system must support at least 1,200 employee accounts.\n3.5 The vendor may offer on-site training at additional cost.\n3.6 The vendor must carry general liability insurance of at least $1 million.\n4.1 Proposals must be received by 3:00 p.m. CT on November 20, 2026.\n4.2 Proposals should not exceed 30 pages.\n\n-----\nADDENDUM 1 (issued Nov 3, 2026):\nSection 3.4 is revised: the system must support at least 1,800 employee accounts.\nSection 4.1 is revised: proposals must be received by 3:00 p.m. CT on December 4, 2026.\n\nMy notes: our system handles up to 1,500 accounts per tenant today. Pre-bid call was \"pretty relaxed.\"","rules":[{"type":"numberedItems","count":5},{"type":"plainText"}],"mistakes":[{"title":"Mixing must and should","why":"The AI lists every requirement it finds, so optional items look mandatory.","fix":"Say: \"Only 'must' items. Skip 'should' and 'may'.\"","checks":["r1"]},{"title":"Missing the addendum","why":"The changes come after the main text, so the AI often copies the original numbers and dates.","fix":"Add: \"Apply Addendum 1 where it changes a section.\"","checks":["r0","r1"]},{"title":"Getting a bid opinion","why":"The AI notices your 1,500-account limit and starts advising whether to bid.","fix":"Say: \"Output only the 5 lines, no opinion.\"","checks":["r2"]},{"title":"Not saying how many","why":"The AI decides the length itself and usually returns more lines than you can use.","fix":"Be exact: \"exactly 5 numbered lines.\"","checks":["numberedItems","r2"]},{"title":"Getting markdown back","why":"AI defaults to bold labels and headings, which show up as stray symbols in your bid checklist.","fix":"Ask for \"plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Asks for must items only","patterns":["\\bmust\\b","mandatory","not (should|may)","skip (should|may)"]},{"label":"Applies the addendum","patterns":["addendum","revis","1,?800","dec(ember)?\\.? 4"]},{"label":"Asks for section numbers","patterns":["section","\\(3\\.","sec\\.?"]},{"label":"Says exactly how many","patterns":["\\b(5|five)\\b.{0,25}(line|requirement)","exactly \\d+"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"RFPs use 'must', 'should' and 'may' on purpose, and addenda change the rules late. Tell the AI which word counts, to apply the addendum, and to cite sections.","rubricLabels":["Lists only 'must' requirements and includes the account requirement as 1,800 (Addendum 1), not 1,200","If the proposal deadline is listed, it is Dec 4, 2026 at 3:00 p.m. CT (Addendum 1); no 'should' or 'may' item (payroll integration, on-site training, 30-page limit) appears","Each of the 5 lines includes its section number (such as 3.1, 3.3, 3.4, 3.6, 4.1), and nothing else is output: no bid/no-bid opinion, no notes about the 1,500-account limit"]}