Hello, How can we help?

What this does

Makes a task automatically recreate itself on a schedule — daily, weekly, monthly, or on a custom cron-like pattern. Use this for the work that repeats: closing the till every evening, monthly reporting, quarterly audits, and so on.

Current access and functionality

• Verified against the current impact-web, impact-client, and impact-marketplace code on 2026-05-07.
• In impact-web, users must be signed in and working in an active workspace. Navigation and write actions are role-, permission-, and entitlement-aware; unavailable modules are hidden or disabled instead of being universally visible.
• In impact-client, the mobile app covers day-to-day work such as tasks, checklists, projects, surveys, members, dashboards, and marketplace template usage. Administrative setup and some advanced configuration remain web-first.
• Project creation and management are available to company admins, owners, project coordinators, and project managers according to the permission matrix. Project members may only see assigned or permitted project content.
• Task access is scoped by workspace, project, team, and assignment. Users can act on tasks they are assigned to or permitted to manage; project managers and team leaders have broader controls for their areas.

Before you start

• You need permission to create tasks in the project where the template lives.
• Recurring tasks require a parent project. Standalone recurring tasks (outside any project) are not supported — create a "Standing Work" project if you need a catch-all.

The two models

Template-based is simpler; per-instance adds merge fields.

Steps — template-based

Creating the template

1. Open the project → Tasks → New recurring task.
2. Fill the normal task fields: title, description, assignee, due-date offset (e.g., "due 2 days after spawn").
3. Add any checklist items. They are copied verbatim into each new instance.
4. Under Recurrence, pick the pattern:
   • Daily — every day at a time you pick, optionally excluding weekends.
   • Weekly — pick one or more days of the week.
   • Monthly — pick day-of-month (e.g., 1st, 15th, last).
   • Custom cron — advanced; admin-only. Helpful tooltip explains the five-field format.
5. Pick End — "Never", "After N occurrences", or "On a specific date".
6. Save. The template is now active — the next spawn happens at the next scheduled time.

Verifying the schedule

1. The template page shows Next spawn and Recent spawns.
2. Click any recent spawn to see the actual task that was created.
3. If the next spawn is not what you expected, edit the recurrence — changes apply from the next spawn, not retroactively.

Pausing / resuming

1. Open the template.
2. Click Pause. No new instances spawn; existing ones continue.
3. Click Resume to restart. IMPACT does NOT back-fill missed spawns during pause — it picks up from the next scheduled time.

Steps — per-instance copy with merge fields

Merge fields available

• {{period}} — e.g., "April 2026" for monthly, "Week 16 of 2026" for weekly.
• {{spawn_date}} — the date the task was created.
• {{due_date}} — the computed due date (spawn_date + offset).
• {{assignee_name}} — resolved at spawn time.

Using them

1. In the template's title or description, embed merge fields (e.g., title: Payroll for {{period}}).
2. Each spawn substitutes the field with the resolved value.
3. Checklist items support merge fields too.

Steps — reassigning on the fly

Round-robin assignment

1. Instead of a single assignee, pick Round robin and a team.
2. Each spawn rotates to the next person on the team.
3. Team members get notified with "You're next" 24 hours before spawn.

Follow the role

1. Pick Role: Finance lead (or any role) instead of a specific person.
2. IMPACT resolves the current Finance lead at spawn time, so if someone changes role, the task lands with the new lead automatically.

Tips

• Start with weekly. Most recurring tasks should be weekly or monthly. Daily becomes noise quickly.
• Use checklists inside the template, not separate tasks. A weekly close-out with 8 checklist items is cleaner than 8 sibling tasks.
• Test the template by triggering a manual spawn before the real schedule kicks in. The Spawn now button creates one instance immediately so you can verify the substitution and assignment work.

Common issues

• Issue: No instances spawning — Fix: Check the template is Active (not Paused) and the End condition has not been hit. The Next-spawn time tells you when the next one is expected.
• Issue: Merge fields show as literal {{period}} — Fix: The template was saved without a recurrence pattern (so IMPACT cannot compute the period). Set a recurrence and resave.
• Issue: Round-robin skipped someone — Fix: Likely they were on leave when it was their turn — IMPACT skips anyone with an active leave status and assigns the next person in line. Check the assignment log on the spawned task.

Related

• How to create and assign tasks
• How the task workflow works