Work Management Templates: Projects, Campaigns, and Meetings

A template saves time when it reminds the team to ask important questions. It cannot replace understanding the work. Copying old tasks, names, and dates without review can carry old mistakes into a new project.

Copy these three text templates into a working document or project description, then turn actions into tasks on a shared board. These are editorial templates within the article; they do not imply an automated template library in the platform.

A short project plan template

Apply the campaign template with the agency delivery guide, and keep meeting decisions accessible using task decision records.Agree on these details with the people doing the work and approving delivery before assigning tasks.

• Project name: describe the desired outcome.

• Goal: the problem and result you want to achieve.

• Final deliverable: the output, acceptance criteria, and approver.

• Scope: what is included and what is deferred.

• Milestones: intermediate deliveries, owners, and expected dates.

• Dependencies: inputs and decisions needed before execution.

• Risks and blockers: early signals, actions, and follow-up owners.

• Review: when the plan is updated and where decisions are recorded.

Example: launch a service page with client-approved copy and links that work on mobile. Include one page and a contact form, while deferring the rest of the website redesign. Create separate tasks for writing, design, development, and testing.

A marketing campaign template

Connect each asset to the campaign goal and approval process, instead of treating every design as an isolated request.

• Campaign goal: the desired result and how it will be checked.

• Audience and message: who you address and the main idea.

• Channels and deliverables: required assets, sizes, and formats.

• Inputs: approved brief, copy, images, and references.

• Responsibilities: writing, design, review, approval, and publishing.

• Dates: first draft, consolidated feedback, approval, and launch.

• Prelaunch checks: links, copy, approved versions, and agreed requirements.

• Postlaunch review: what happened and the next decision.

Example: a campaign needs three assets, a landing page, and an email. Settle the message before final design and choose one approver to consolidate feedback. Review the scope and timing before adding another asset.

A progress meeting template that produces decisions

Start with issues that need a decision, and make status updates available beforehand. A written review may be enough when there are no shared blockers or decisions.

1. Meeting goal: the decision or outcome needed.

2. Completed work: accepted deliverables and links.

3. Blocked work: the obstacle, impact, and person able to resolve it.

4. Decisions: options, chosen decision, reason, and owner.

5. Actions: a clear task, owner, and deadline for each action.

6. Changes: revised scope or timing, deferred work, and who needs an update.

7. Next follow-up: when to review actions or revise estimates.

Turn meeting actions into tasks and link the minutes or decision when needed. Collaboration around tasks preserves context for people who were absent.

Adapt the template to your team

Remove fields that do not affect a decision. Add only what the work needs, use familiar terms, and check access before sharing files. Verify old customer details and owner names before copying them into a new project.

Try the template in one project. Ask what information was missing and which fields went unused. Update it based on practice so it remains useful and easy to maintain.

Frequently asked questions

Are these ready-to-import files?

They are text templates to copy and adapt. Check current platform options for importing or automatically reusing projects.

When should we update a template?

When a recurring gap affects delivery or the workflow changes. Add fields for exceptional cases only when the impact justifies them.

How should we write the resulting tasks?

Give each task a clear output, owner, and completion criteria.