How to Write an Investor FAQ from a Data Room Index

Investor FAQs invent burn. Answer from the index. Write NO_DATA when the folder is missing.
The matching generator is the Investor FAQ from a Data Room Index (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).
Print the not-investment-advice banner
Draft an investor FAQ from a data-room index. Answer only indexed facts. Write NO_DATA when a topic is missing. 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:
Data room index (file names/topics): [Index]
Allowed facts I may quote: [Facts]
FAQ topics I want answered: [Topics]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Banner I require: [Banner or Not investment advice]
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.
Answer each topic from Facts or Index only
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:
- Honesty ledger: Index nouns, Facts nouns, Topics, Banner, Lang.
- Banner line.
- For each Topic: answer from Facts/Index or write NO_DATA and name which index folder is missing.
- Never invent ARR, burn, headcount, or term-sheet terms.
- Source line under each answered FAQ citing Index entry or Facts quote.
- Refuse: inventing SAFE terms, inventing customers, inventing diligence outcomes.
- Open items list: Topics that returned NO_DATA.
- Compliance pass: 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.
Write NO_DATA naming the missing folder
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:
- FAQ from Index+Facts only. Not investment advice.
- NO_DATA when missing. Never invent metrics.
- Keep Banner visible.
- 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 invented ARR and SAFE terms
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 (investor faq data room index, no_data when missing investor, fundraising faq from data room) 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.