Agiled Docs

Productivity templates help teams repeat common delivery patterns.

Use templates to standardize work that already has a repeatable process. Do not turn an unclear process into a template until the team agrees on the steps, owners, and timing.

Template Types

The productivity template page has two tabs:

Project templates for reusable project structures and delivery patterns.
Task templates for repeatable individual tasks with default status, priority, and due-date timing.

Use project templates when several tasks, milestones, or delivery steps repeat together. Use task templates when one task repeats often but does not need a full project structure.

Create a Project Template

Open Templates.
Go to Productivity templates.
Open the Project Templates tab.
Select New project template.
Enter the template name and description.
Save the template.

Use project templates for repeatable client onboarding, service delivery, implementation, content production, internal operations, or monthly work cycles.

Before saving a project template, confirm the structure is reusable. Avoid including one customer's private details, temporary due dates, or one-off instructions that future projects will need to remove.

Add default task names, owners, priorities, and relative timing only when those defaults are useful for most generated projects. Leave one-off customer details for the actual project.

Create a Task Template

Open Templates > Productivity templates.
Open the Task Templates tab.
Select New task template.
Enter the template name and description.
Choose the default status.
Choose the default priority.
Set default due days when the task should be due a fixed number of days after creation.
Save the template.

Use default due days for relative timing, such as two days after task creation. Do not use a task template for fixed calendar dates unless the same real date should apply every time.

Edit or Delete Templates

Each template row includes an edit action and a delete action. Edit a template when future projects or tasks should use the new defaults. Delete templates that are outdated or no longer match your delivery process.

If existing projects or tasks were created from an old template, editing the template does not automatically rewrite those active records. Update active work separately when the process change matters.

Before deleting a template, check whether teammates still use it in onboarding, delivery, operations, or monthly routines. Rename old templates as archived if you need a short transition period.

Good Template Names

Use names that explain the repeatable workflow, such as Client onboarding, Website launch checklist, Monthly reporting task, or Invoice follow-up.

Review Template Quality

Review productivity templates every time your delivery process changes:

remove outdated tasks or statuses
update priorities and due-day timing
check descriptions for old policy, pricing, or service language
archive templates that are no longer used
create a test project or task from the template before rolling it out

If the team keeps editing every generated project or task the same way, update the template instead of repeating manual cleanup.

Rollout Checklist

Before telling the team to use a new productivity template:

Create a test project or task from it.
Confirm statuses and priorities match the real workflow.
Check relative due dates.
Remove customer-specific sample text.
Assign an owner for future template updates.

Productivity Templates