Use the risk checklist for fact cleanup, the template for packet shape, the scorecard for readiness, the starter pack for one-answer routing, the answer bank for repeat review, and the framework map for governance coverage.
The due diligence route now has more than four jobs. The risk checklist is the fastest fact-cleanup pass. The template is the fastest packet outline. The scorecard is the fastest way to see whether the facts are actually ready. The starter pack keeps buyer-language due diligence context attached when the live blocker shrinks back down to one answer. The answer bank is the repeat-review branch once the same diligence prompts keep coming back. The packet builder and evidence map handle the heavier packet-assembly and proof-gap branches. The framework map is the right branch when procurement, security, privacy, or counsel wants NIST AI RMF, ISO/IEC 42001, ownership, controls, and monitoring notes instead of a lighter buyer packet.
Use this page to choose the shortest NoticeKit path for the buyer thread. Procurement, security, privacy, and legal reviewers still decide the final packet and contract language.
Which route solves the blocker?
Due diligence risk checklist
Use it when the buyer already wants due diligence coverage but the vendor chain, scope, owner, proof, or open-risk notes are still unstable.
Due diligence template
Use it when the buyer wants one practical packet that names the vendor chain, workflow, customer scope, owner, proof, and open issues without turning the thread into a framework exercise yet.
Due diligence scorecard
Use it when the operating facts are still uneven and you need a readiness score, gap list, and next-step route before drafting the packet or sending the answer.
Framework map
Use it when the buyer already asked for governance coverage shaped around NIST AI RMF, ISO/IEC 42001, controls, monitoring, owner path, or improvement notes.
Due diligence starter pack
Use it when the broader packet work is done enough, but the live blocker has shrunk back down to one questionnaire row, one buyer email, or one repeat-review source file.
Due diligence answer bank
Use it when the buyer-language diligence work now repeats across deals and you need one reusable file with approved wording, proof links, owner notes, and framework-ready variants.
Evidence map
Use it when the packet mostly works but one claim still needs proof assets, owner metadata, review date, or escalation notes behind it.
Comparison table
| Question | Risk checklist | Due diligence template | Due diligence scorecard | Framework map | Starter pack | Answer bank | Evidence map |
|---|---|---|---|---|---|---|---|
| Best for | Cleaning up unstable facts | Shaping the review packet | Scoring how ready the packet is | Answering framework-shaped governance asks | Routing a due-diligence thread back into one answer | Preserving one reusable due-diligence source file across repeated reviews | Shoring up one weak claim inside a mostly coherent packet |
| Primary output | A tighter fact and risk checklist | A copy-ready diligence outline | A readiness score, gap list, and review brief | A governance brief mapped to NIST AI RMF and ISO/IEC 42001-style prompts | A buyer-language bridge into the shortest one-answer, proof, repeat-review, or audit route | A reusable repeat-review file for due-diligence answers, proof notes, owner paths, and variants | A proof-backed claim with owner, review date, and escalation notes attached |
| Typical trigger | "These facts still feel weak." | "Send the diligence packet." | "Are these facts ready yet?" | "Map this to a framework." | "This is really one answer now." | "We keep answering this diligence question." | "This one claim still feels unsupported." |
| What it prevents | Sending a buyer packet with missing scope, owner, or proof facts | Overwriting the same buyer-language packet from scratch | Sending a weak packet with missing owner, scope, or proof details | Pretending a light template answers a framework-specific buyer request | Dropping the due-diligence context when the packet shrinks back down to one live blocker | Rewriting the same due-diligence answer from scratch across deals or segments | Rebuilding the full packet when only one proof branch still needs work |
| Best next step | Open risk checklist | Open due diligence template | Open scorecard | Open framework map | Open starter pack | Open due diligence answer bank | Open evidence map |
Use these sequences in practice
- If the buyer already said "send your AI due diligence" but the facts are still unstable, start with the risk checklist.
- If the packet shape is obvious after the checklist, move into the template.
- If the facts are still uneven after the checklist or template, drop into the scorecard before writing the final packet.
- If the reviewer names NIST AI RMF, ISO/IEC 42001, governance controls, or monitoring expectations, branch into the framework map.
- If the packet is coherent but the buyer still doubts one claim, move into the evidence map instead of expanding the whole file again.
- If the live blocker shrinks back down to one answer, route into the due diligence starter pack or the answer builder instead of keeping the whole packet open.
- If the same due-diligence prompts keep returning after the packet is already coherent, branch into the due diligence answer bank instead of rebuilding the same answer from scratch.
How to tell when you are overbuilding
Stay with the risk checklist
If the owner path, downstream providers, customer scope, or proof links are still changing, do not jump straight to a polished packet.
Stay with the template
If the reviewer mostly wants the packet shape and the owner or proof details are already known, do not force a score or framework map first.
Stay with the scorecard
If the owner path, customer scope, proof links, or downstream providers are still changing, do not jump to framework language before the facts are stable.
Stay with the framework map
If the reviewer is explicitly asking for governance structure, monitoring, or control narratives, do not answer with only a lighter buyer packet and hope it lands.
Choose the lightest artifact that still matches the buyer ask.
The risk checklist keeps weak facts from leaking into the packet, the template keeps the packet practical, the scorecard checks readiness, and the framework map only comes forward when the buyer really wants governance coverage shaped like a formal framework request.
Still not sure which route is shortest?
Use the route chooser if the blocker is still fuzzy, the evidence map if one proof claim is weak, or the audit if the real missing piece is judgment about what to fix first.