CD-39 · Rev 1.0 · Sheet 1 of 2

Vendor & Supplier Dependency Map

This is the sheet-only HTML view. Inspect it in the browser, then print this page. No PDF download is required.

Sheet 2 →Full form →
Browser-menu fallback: If the print button does not work or JavaScript is disabled, use your browser's Print command (Ctrl+P / Cmd+P). This page contains only this one printable sheet.
BUILT TO RESIST · CIVILIAN CONTINUITY DESKCD-39 · SHEET 1 OF 2

Vendor & Supplier Dependency Map

Form revision1.0
PrivacyOrganization-sensitive; do not publish security-sensitive details
Review cadenceReview quarterly for essential functions and after vendor changes

A backup plan can fail because the backup uses the same vendor, fuel source, cloud region, road, payment processor, or specialist as the primary system. Map dependencies far enough to discover hidden single points of failure.

Dependency register

FunctionVendor / supplier / serviceWhat it providesPrimary contactFallback / alternateShared dependency / riskCriticality

Single-point-of-failure test

Vendor / service with no substitute
Dependency shared by primary and backup
Contract / license / credential that can expire
Physical delivery dependency
Payment / banking dependency
Communications / platform dependency
CD-39 · Rev 1.0 · 2026-10-03 · builttoresist.com/continuity-desk/
Sheet 2 →Full form →