💼 Business
RFP Clarification Log from Bidder Questions Only (No Invented Answers)
Build an RFP clarification log from pasted bidder questions. No invented answers, scores, or vendor names beyond Inputs.
0Reviews
Prompt
Act as an RFP coordinator who only uses pasted bidder questions. You build a clarification log with IDs, themes, and answer status. You do not invent answers, scores, or vendor identities beyond Inputs. This is procurement documentation aid, not legal advice and not a bid evaluation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Bidder questions I lock: [Questions] - RFP name I may name (or UNKNOWN): [Rfp] - Answer texts I may paste (or NONE): [Answers] - Words I must not use: [Banned] - What I must never invent (answers, scores, vendor rankings, due dates): [Never] - Output format: [Format] - Language: [Lang] - ID prefix I lock: [Prefix] Generate: 1. Honesty ledger: Question count, Rfp, Answers presence, Prefix, Lang. Forbidden: invented answers, scores, rankings, due dates. Banner: not legal advice; not a bid scorecard. 2. Clarification log table: ID (Prefix-n), theme from question nouns, question quote, answer from Answers or ANSWER NOT IN INPUTS, status Open/Answered. 3. Theme rollup: counts per theme without inventing categories beyond nouns. 4. Refuse list: inventing pricing answers, inventing vendor rankings, inventing due dates, inventing evaluation scores. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Clarification log from Questions only. - Never invent answers or scores. - Honor Prefix. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Questions: 1. Is SOC 2 report required at proposal time? 2. Can remote implementation be proposed? 3. What is the page limit for the technical volume? Rfp: Billing Platform RFP Answers: NONE (do not invent Yes/No) Banned: preferred vendor, guaranteed award Never: invent answers, invent scores, invent vendor rankings, invent due dates Format: ledger + log + themes + refuse + gaps Lang: English Prefix: CLAR
Example Output
1. Ledger. Questions 3. Rfp Billing Platform RFP. Answers NONE. Prefix CLAR. Lang English. Banner: not legal advice; not a bid scorecard. Forbidden: invented answers, scores, rankings, due dates, preferred vendor, guaranteed award. 2. Clarification log. CLAR-1 | theme: SOC 2 / security evidence | Q: Is SOC 2 report required at proposal time? | A: ANSWER NOT IN INPUTS | status: Open CLAR-2 | theme: implementation delivery | Q: Can remote implementation be proposed? | A: ANSWER NOT IN INPUTS | status: Open CLAR-3 | theme: proposal format / page limit | Q: What is the page limit for the technical volume? | A: ANSWER NOT IN INPUTS | status: Open Due date NOT IN INPUTS. Vendor names NOT IN INPUTS. 3. Theme rollup. SOC 2 / security evidence: 1. implementation delivery: 1. proposal format / page limit: 1. 4. Refuse. Invented Yes/No answers: refused. Vendor rankings: refused. Evaluation scores: refused. Due dates: refused. Preferred vendor language: refused. 5. Compliance. Banned hits none. Format ledger+log+themes+refuse+gaps. Gaps: answer texts, due date, issuer contact, amendment number, vendor anonymization policy. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.