Map RFP sections to existing capability notes first

RFPs tempt blank-page writing. Mapping first prevents rewriting capabilities you already documented.

This hack: twenty-five minutes, map sections to existing notes. Write later.

When to use it

• An RFP or questionnaire landed.
• You have past proposals, capability docs, or security answers.
• Go/no-go is leaning go.

When not to

• You already decided no-go. Don't map theater.
• You have zero reusable material. Then the map will show red; use that for no-go.
• Deadline is tonight and mapping steals writing time - write critical sections first.

Do this (timer on)

1. 1. List RFP section headers.
2. 2. Match each to an existing internal doc or mark GAP.
3. 3. Score: reuse / light rewrite / net-new.
4. 4. Hand the map to whoever writes.

Prompt (copy)

Map RFP sections to existing materials.

Output table:
| RFP section | Best internal source | Reuse level | Gap notes | Owner suggestion |

Reuse levels: paste / light rewrite / net-new
Do not invent sources.

RFP SECTIONS:
[paste]

AVAILABLE INTERNAL DOCS (titles + snippets OK):
[paste]

After you send

If every RFP is net-new prose, knowledge reuse is broken. Operations Efficiency when briefing never compounds.

Start free assessment (Operations Efficiency) at https://faisalrizvi.com/ - See where we're wasting hours. 3 minutes. Score + prioritized roadmap. Shareable report. No login.

Book a free 30-min call only if you want a walkthrough after the roadmap.