Project Intake
Capture a proposed project before committing time or budget.
Purpose
Project work should turn an idea into controlled delivery: purpose, boundary, owner, stakeholders, assumptions, risks, dependencies, milestones, acceptance criteria, and closeout obligations.
Project use
Use this page before project momentum makes assumptions hard to correct. It should make the work easier to approve, pause, adjust, or close.
| Decision supported | What does this document help decide? |
|---|---|
| Owner | Who is accountable for updating it? |
| Boundary | What is included, excluded, deferred, or assumed? |
| Evidence | What confirms completion, acceptance, or handoff? |
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
- Scope grows without a decision record.
- Benefits are assumed but not reviewed.
- Operational handoff is delayed until launch.
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.
- ISO quality management principlesProcess approach, evidence-based decisions, improvement, and relationship management.