DDailyWF

Vendor Comparison Template

Compare vendors without hiding assumptions or decision criteria.

Purpose

Vendor work should make external dependency visible: access level, data exposure, contract owner, support path, review cadence, and exit plan. The risk is not only the vendor; it is forgotten dependency.

Copy-ready structure

# Vendor Comparison

Owner:
Date:
Status:

## Purpose
Describe why this document exists and what decision or action it supports.

## Scope
Included:
Excluded:
Deferred:

## Details
- Key fact:
- Dependency:
- Risk or constraint:
- Required approval:

## Evidence
Record where the result, approval, or supporting material is stored.

## Review
Next review date:
Update trigger:

When to use

  • When the work repeats often enough that memory is no longer reliable.
  • When more than one person may request, perform, review, or inherit the work.
  • When risk, approval, evidence, or handoff needs to be visible later.

Common failure modes

  • A vendor account remains active after support ends.
  • Data handling is not checked before use.
  • No owner knows how to terminate or replace the service.

Review guidance

Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.

External guidance

These resources are references for terminology, control thinking, or review design. DailyWF adapts the ideas into lightweight operating pages rather than reproducing full standards.