Help Centre - AffiniTask
AffiniTask Validation Process
1 Introduction
Before AffiniTask goes live, you'll have a chance to review every obligation we've captured—before it becomes a task on the platform.
This is validation. It's your opportunity to verify accuracy, adjust assignments, and ensure AffiniTask is set up exactly how you need it.
This guide walks you through the validation process.
2 When Validation Happens
After we've extracted obligations from your contracts, you'll have a validation window to:
- Review captured obligations before they become tasks
- Provide any Defined Dates you already know (see our guide: AffiniTask and Defined Dates)
Validation is a one-time process. Access is permission-based and time-limited.
Recommendation: Grant access to 2–3 users in your organization for thorough review.
3 How to Access Validation
- From the homepage, click the Tasks icon (top-right menu bar)
- Select Obligation Finder
- Choose your project
- Click Open List in the Obligations List box
4 What You'll See: The Review View
When you open validation, you'll see the Review view by default. This shows all captured obligations and their details:
Column guide:
- Name – link to see full captured obligation
- Book – link to the contract containing the clause
- Chapter – link to the specific clause
- Extraction Session – the document group being reviewed
- Responsible party – who must action the task
- Type – Task type - Calendar or Event Notice
- Date / Event – The Target Date of when the task is due (or Defined Date placeholder)
- Repeat – repeating schedule (if applicable)
- Action instruction – AI-generated guidance on what to do
- Created and Modified details – details of who created and/or modified the task with corresponding dates and times.
5 Other views:
-
Dates & Deadlines – groups obligations by due date, recurrence, and end date
-
Assignment – shows who's assigned to each task (Assignee, Verifier, Collaborators)
6 What to Do During Validation
Validation gives you confidence that we've captured the right obligations.
You don't need to read every detail—spot-check as you see fit using the links provided. But do review obligations tied to unknown Defined Dates, since these will become tasks automatically once you provide the date later.
7 Validation Actions
How actions work:
You can act on individual obligations or multiple obligations at once. Select rows by ticking the checkbox, or use filters and select all matching results.
8 Remove an Obligation from Tasking
By default, all captured obligations are set to become tasks (green tick in the "Taskable" column). To prevent an obligation from becoming a task:
- Switch to Assignment view
- Select the row(s) by ticking the checkbox on the left
- Click Set Taskable
- Select Mark as Not Taskable
- Click Apply to Selected
9 Assign Users to Tasks
You can assign one user per role (Assignee or Verifier):
- Switch to Assignment view
- Select the row(s)
- Click Set Assignee or Set Verifier
- Choose a user from the dropdown (or search by name)
- Click Apply to Selected
10 Add Collaborators
Collaborators can view tasks. We recommend assigning Collaborators at the user group level (you can select multiple groups):
- Switch to Assignment view
- Select the row(s)
- Click Set Collaborators
- Choose an allocation mode: Add, Replace, or Remove
- Select user groups by ticking the group name
- Click Apply to Selected
11 What Happens After Validation
Once validation ends, we upload tasks for:
- Event-triggered obligations (all)
- Date-triggered obligations (where the date is known)
- Defined Date obligations (where you've provided the date)
Obligations tied to Defined Dates you haven't provided yet remain captured. Tasks will be created automatically when you enter the date.
12 Adding Tasks Later
When a Defined Date becomes known, update it in the Defined Date User Interface. We'll create the related task automatically and notify you.
13 Need Help?
Contact our support team: support@affinitextgroup.com
For a printable version of this guide, download the PDF attached at the end of this article.
Document Version Control
Article Number: AFHC01032
Authors: Jem Fennell
Creation Date: 1 March 2026
Document Owner: Jem Fennell
Approved by: Affinitext Board of Directors
Date of last review: 31 March 2026
Reviewed by: Jem Fennell
Date of next review: 1 March 2027
Comments
0 comments
Please sign in to leave a comment.