Start with the decision the plan needs to support
A one-page plan is not a shortened version of every project document. It is a shared reference for the decisions people are most likely to face: What are we making, who is it for, what matters most, and when is it ready to hand over? It works well for projects such as a poster, a short video, a landing page or a small set of illustrations. If the work has many dependencies or approval stages, the page can serve as an overview with links to more detailed materials.
Before choosing a template, write a working project name and a two-sentence brief. The first sentence should describe the intended outcome, not just the task: “Create a landing page that helps visitors understand the workshop and sign up.” The second can identify the audience and an important constraint: “It is for first-time visitors and must use the existing visual identity.” These sentences give the rest of the plan a purpose.
Define the output and draw a boundary around the work
Use the next part of the page to list the deliverables. Name the actual items someone expects to receive, including format where it matters: for example, one page design, mobile and desktop layouts, and final image assets. Then add a brief “not included” line. That line might rule out new logo design, copywriting or ongoing updates. Boundaries make it easier to discuss a new request without treating it as something that was always part of the job.
Add two or three priorities to guide trade-offs. A student making a short film might prioritize a clear story and clean audio over elaborate effects. A freelancer designing a poster might prioritize legibility at print size and consistency with a client’s existing materials. These priorities are more useful than a long list of vague qualities because they help you choose what to improve when time is limited.
Turn the deadline into a few checkpoints
A final due date alone does not show when decisions need to happen. Divide the work into a few meaningful checkpoints, such as brief agreed, first draft ready, feedback received, revisions complete and files delivered. Put an owner beside each checkpoint if more than one person is involved. For a solo project, the owner can simply be you; writing it down still makes the sequence visible.
Leave room for feedback rather than placing the first review immediately before delivery. Record who gives consolidated feedback, where they will leave it, and when you need it. A small team could use comments in its shared design file, while a freelancer might ask one client contact to collect responses in a single document. This does not guarantee quick decisions, but it reduces the chance of chasing conflicting notes across messages.
If a date or dependency is uncertain, say so plainly. “Draft starts after copy is approved” is more useful than a schedule that assumes the copy will appear on time. The page should reveal what might block progress, not hide it.
Record decisions, risks and what “done” means
Reserve a small area for open questions and decisions. Keep it selective: a question belongs on the plan if its answer could change the scope, schedule or direction. For a workshop landing page, examples might be “Who supplies the final event details?” and “Is registration handled on this page or through an existing form?” Once answered, replace each question with the decision and its owner. Longer notes can live elsewhere.
Include a simple definition of done. It could read: “Approved copy is in place; layouts have been checked at agreed screen sizes; links work; final files are in the shared delivery folder.” Adapt the checks to the project rather than copying a generic list. If approval is required, name who provides it. This gives a student, freelancer or small team a practical stopping point and makes handover less dependent on memory.
Keep the page visible and revise it deliberately
Arrange the plan so someone can scan it quickly: brief and audience at the top, deliverables and boundaries in the middle, then checkpoints, responsibilities and completion checks. Short labels and compact sentences are enough. If details no longer fit comfortably, move reference files, research notes or task-by-task tracking into separate documents and link to them from the plan.
Share the page before substantial work begins and ask the people involved to confirm the goal, scope and first checkpoint. Revisit it when a decision changes, a dependency slips or a new deliverable is requested. Note the change in plain language so everyone can see what the current agreement is. The value of a one-page plan is not that it predicts every step; it gives a small project a clear starting point and a reliable place to return when the work changes.
