Hello, How can we help?

What this does

Use this guide to create reusable project templates and playbooks that save setup time without locking teams into stale or over-complicated plans.

Current access and functionality

• Verified against the current impact-web, impact-client, and impact-marketplace code on 2026-05-07.
• Project template and playbook setup is primarily web-first.
• impact-client can show project and template-related content where supported, but deep project setup remains better in impact-web.
• Marketplace templates can be reviewed or imported where the user owns the item and has permission for the destination feature.
• MPP import is available in impact-web when the deployment feature is enabled.

When to create a template

• The project pattern repeats at least three times.
• The workflow has stable phases, milestones, or deliverables.
• Checklist expectations are consistent enough to reuse.
• The template saves more time than it costs to maintain.

Template structure

1. Start with phases or milestones.
2. Add only the tasks that happen in most projects.
3. Add checklist items that define quality and evidence.
4. Add dependencies only when they are generally true.
5. Leave customer-specific work as placeholders or optional tasks.
6. Review the template after every few uses.

Avoid over-templating

• Do not add every possible exception.
• Do not turn templates into policy manuals.
• Do not include outdated owners or dates.
• Do not force teams to delete half the template every time.

Common issues

• Issue: Teams ignore templates. Fix: Shorten them and keep only reusable work.
• Issue: Imported projects have incorrect dates. Fix: Review baseline dates, dependencies, and project calendar assumptions before execution.
• Issue: Marketplace templates do not fit the workspace. Fix: Import into a review workspace or copy, then adapt before assigning to live teams.

Related

• How to create project templates
• How to import a Microsoft Project MPP file
• How to import marketplace templates