DailyWF / Workflows
Dependency Check
Confirm prerequisites, owners, dates, and downstream effects before work starts.
How to use this workflow
Dependency Check is useful when repeated work needs a visible path from request to completion. Keep it compact: the value is in clarifying ownership, next action, and evidence, not in creating a large approval artifact.
- Define the trigger that starts the workflow and the condition that ends it.
- Confirm the owner, participants, inputs, constraints, and expected output.
- Perform the steps in the order people will use during normal workload.
- Record evidence, exceptions, decisions, and unresolved follow-up.
- Review the workflow after repeated confusion, incidents, or ownership changes.
Expected output
A completed dependency check record with trigger, owner, decision, next action, and evidence.
Common failure mode
Keeping the document as a form instead of using it to make decisions visible.
Use notes
| Best trigger | Use when the work repeats, affects others, creates risk, or needs a defensible handoff. |
|---|---|
| Evidence | Keep the shortest record that proves the decision, action, owner, and result. |
| Review point | Review after incidents, repeated confusion, tool changes, ownership changes, or missed expectations. |
Related pages
- Approval FlowDefine who must review, approve, or be informed before work proceeds.
- Change Request ReviewReview a proposed change before it affects production work.
- Daily PrioritizationChoose what matters today without depending on memory.
- Meeting Follow-UpTurn meeting discussion into assigned actions and visible ownership.
- Post-Action ReviewExtract learning from completed work before context disappears.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.