What this does

Understand IMPACT's three-stage task workflow. Every task moves through Action, Verify, and Accept stages, ensuring work is executed, reviewed, and approved before it is considered complete.

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.
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.

The three stages

1. Action

Who: The Action SME (the person assigned to do the work).
What happens: The assignee executes the task — completes the work, fills in checklists, and attaches any required files.
When it ends: The Action SME marks the action stage as complete, moving the task to Verify.

2. Verify

Who: The Verify SME (the reviewer).
What happens: The reviewer checks that the work meets requirements. They review checklists, deliverables, and any attached evidence.
Two outcomes:
- Approved — the task moves to the Accept stage.
- Rework requested — the task returns to Action. The rework count is incremented so you can track how many times a task was sent back.

3. Accept

Who: The Accept SME (the final approver).
What happens: The approver gives final sign-off on the completed and verified work.
Two outcomes:
- Accepted — the task is marked as Completed with an actual end date recorded.
- Rework requested — the task returns to an earlier stage. The accept rework count is incremented.

Why three stages?

This workflow separates execution from quality control:

The doer focuses on getting the work done.
The reviewer ensures the work meets standards.
The approver confirms it aligns with project goals.

This prevents situations where the same person marks their own work as complete without oversight.

Tips

Not every task needs all three stages. For low-risk tasks, you can assign the same person to multiple roles or leave Verify/Accept unassigned.
Track rework counts to identify recurring quality issues. High rework counts on a task may signal unclear requirements or skill gaps.
Checklists are your friend. Attach checklists to each stage so the Action SME knows exactly what to deliver and the Verify SME knows exactly what to check.
On mobile (impact-client), team members can update their assigned tasks and complete stages on the go.

Common issues

Issue: Task is stuck in Verify but the Verify SME has not been assigned — Fix: Edit the task and assign a Verify SME. Without one, no one can progress the task.
Issue: Rework count keeps increasing — Fix: Review the task requirements and checklists. Frequent rework usually means the acceptance criteria are unclear or the Action SME needs guidance.
Issue: Task shows as complete but the Accept stage was skipped — Fix: If no Accept SME is assigned, the task may complete after Verify. Assign an Accept SME if final approval is required.

Hello, How can we help?

Topics

How the task workflow works (Action, Verify, Accept)