How to Build an RFI Response Matrix with NO_DATA

RFI matrices mint SSO and ISO. Status NO_DATA when the facts pack is blank.

The matching generator is the RFI Response Matrix from a Facts Pack (NO_DATA When Missing) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Extract every question first

Build an RFI response matrix from a facts pack. Use NO_DATA when a fact is missing. Never invent capabilities. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

RFI questions: [Questions]
Facts pack: [Facts]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Owner I may assign (or UNKNOWN): [Owner]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

YES NO or NO_DATA per row

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: question count, Facts nouns, Owner, Lang. Forbidden: inventing SSO, inventing certifications.
2. Matrix rows: Question ID, status YES/NO/NO_DATA, evidence pointer from Facts or NO_DATA, owner.
3. Draft stubs only for YES rows using Facts wording.
4. NO_DATA rows: do not invent compensating controls.
5. Refuse: fake ISO cert dates, fake uptime %.
6. Open questions list for the user.
7. Owner column: UNKNOWN if Owner unknown.
8. Compliance pass: quote Banned and Never. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Stub answers only for YES

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• RFI matrix from Questions+Facts only. NO_DATA when missing.
• Never invent capabilities.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Refuse fake cert dates

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (rfi response matrix, no_data when missing, no invented capabilities) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.