DailyWF / Reference
Reference
Short explanations, comparisons, glossaries, and practical notes.
Plain-language explanation
Reference is a practical concept page. Use it to align language before writing a workflow, policy, or review record.
How to apply it
- Keep definitions operational rather than academic.
- Tie the term to decisions people actually make.
- Use examples and counterexamples when confusion is likely.
Expected output
A plain-language reference note that helps users choose the right workflow, policy, or template.
Common failure mode
Keeping the document as a form instead of using it to make decisions visible.
Use notes
| Use with | Link this note from workflows and policies where the term affects decisions. |
|---|---|
| Avoid | Do not turn definitions into rules unless a policy page owns the requirement. |
| Review point | Revise when repeated questions show the explanation is still ambiguous. |
Related pages
- Access ReviewDefine how access is reviewed, changed, approved, and removed.
- Access Review ChecklistConfirm account ownership, appropriateness, and removal actions.
- Access Review LogTrack access review findings, approvals, removals, and exceptions.
- Dependency TrackerTrack decisions, inputs, vendors, systems, people, and approvals that can block delivery.
- New User OnboardingGive a new user access, context, and operating expectations.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.