Workflows and checklists on any record
Attach tasks, approvals and checklists to a deal, a ticket, an employee or a tour. A won deal can spin up a whole onboarding workflow without anyone lifting a finger.
Revenue & Sales · Workflows, approvals & checklists
Work items that live on the record, not in a parallel tool
Every company that buys a project tool ends up maintaining two versions of reality: the work, in the project tool, and the thing the work is about, in the CRM or the HR system. Keeping them aligned becomes somebody's job.
Dolfin360 Task Management attaches tasks, approvals and checklists directly to the records they concern — a deal, a ticket, an employee, a tour. A won deal can generate an entire onboarding workflow without a person copying anything, and the status of that workflow is visible from the deal rather than from a board somebody has to remember to open.
Attached to any record
A task belongs to the deal, ticket, employee or visit it is about — so the work and its subject never drift apart.
Workflows that trigger themselves
A stage change, a resolved ticket or a new hire can generate a full checklist with owners and due dates, as one rule.
Approvals with a trail
Route by amount, department or type; every decision is timestamped against the record it approved.
Checklists that generate themselves
Templates fired by events in any module, with owners and due dates.
Define a checklist once — customer onboarding, new-hire setup, incident review — with owners resolved by role rather than by name, and due dates offset from the trigger. Then attach it to an event: a deal reaching closed-won, an employee record being created, a ticket crossing a priority threshold.
Because the modules share a database, the trigger and the target can live in different parts of the business without any integration. The checklist appears on the record that caused it, and its progress is visible from there.
- 01Reusable templates — owners by role, dates offset from the trigger
- 02Cross-module triggers — fired by CRM, HRMS, helpdesk or tour events
- 03Progress on the record — no separate board to remember to open
What is inside Task Management
Attach work to a deal, ticket, employee, visit or custom object.
Reusable sequences with role-based owners and offset due dates.
Fired by events in CRM, HRMS, helpdesk or tour.
Routed by value, department or type, with multi-step support.
Sequence work so a step opens when its predecessor closes.
Every approval timestamped against the record.
Approvals that finish where they started
Routing by value or department, with a timestamped decision trail.
An approval is a step in the work, not a detour into email. Route a quotation discount, an expense claim or a leave request by amount, department or type, and the approver acts on the item itself with its full context attached.
Every decision — approved, rejected, returned with a comment — is written against the record with a timestamp and an actor. When somebody asks six months later who signed off on a discount, the answer is on the deal.
- 01Value and department routing — multi-step chains where needed
- 02Decide in context — the approver sees the underlying record
- 03Timestamped decisions — actor and comment kept on the record
How work gets created and closed
Trigger
An event in any module — a won deal, a new hire, a raised ticket.
Generate
A checklist template instantiates with owners and due dates resolved.
Execute
Owners work the items in place, on the record the work is about.
Approve & close
Decisions are routed, timestamped and kept against the record.
What stops being maintained by hand
Platform facts and published rates — not customer-measured outcomes.
“Onboarding used to be a document somebody remembered to follow. Now a closed-won deal creates it, and the deal shows how far along it is.”
Attach work to the records it is about
Try Task Management free for 14 days and wire your first cross-module workflow.
Task Management questions
Any record — a deal, a ticket, an employee, a field visit or a custom object you have modelled. The work and the thing the work is about stay together instead of living in a parallel project tool.
Yes, and that is the point of sharing a database. A closed-won deal, a new employee record or a ticket crossing a priority threshold can each instantiate a checklist template with owners resolved by role and due dates offset from the trigger.
Every decision — approved, rejected or returned with a comment — is timestamped with its actor against the record it concerned. When someone asks six months later who signed off on a discount, the answer is on the deal.
Try Task Management free for 14 days
No credit card. It shares data with every other module the moment you turn it on.