Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Organize work into projects, break it into tasks and subtasks, assign it to real employees, and drive it across a Kanban board. Every task can link straight to the purchase order, invoice, customer, asset, stock transfer or vendor it moves — so delivery and operations stay one system.
Structure
Projects → tasks → subtasks
Ownership
Assigned to employees
Flow
Kanban board & my tasks
Context
Back-links to operations
What's shipped
These are the capabilities in your hands right now, not a roadmap.
A project has a status lifecycle (planning → active → on hold → completed / cancelled with guarded transitions), an owner (an employee), a department, dates and a code. Progress is derived live from its tasks — never a stale number you maintain by hand.
Tasks carry a status, priority, dates and description, and can nest one level into subtasks so a parent shows real done/total progress. Tasks can also stand alone, with no project at all.
Assignment targets an active employee — a person, not a login seat. A terminated assignee is flagged, and their open work surfaces in a reassignment queue.
Drag cards across columns per project; the board respects each project’s own status set when you customize it.
Every user sees the work assigned to their employee record, grouped into overdue, due-soon, open and done — with saveable filter views.
Select many tasks and set status, reassign, or move them to another project in one go.
Discuss on the task; @mention a colleague by name and they get an in-app notification.
Attach files to a task through the shared Document Vault — checksum-verified, access-logged and previewable in-app.
Link a task to a PO, invoice, customer, asset, stock transfer or vendor; that record shows the related work back on its own page.
Assignment, status changes, @mentions and due-soon reminders ride the platform’s in-app notification rail — plus a daily reminder for work due soon or overdue.
View, add, edit, delete and assign are separate permissions on your existing roles; “my tasks” has its own view-own permission.
Soft-delete captures who archived a task and keeps it restorable — nothing is lost.
Project lifecycle
Status changes are explicit and only permitted transitions are offered — so a completed project reopens deliberately, and a cancelled one is revived on purpose.
Planning
Being scoped
Active
In delivery
On hold
Temporarily paused
Completed
Delivered
Cancelled
Stopped
The difference
A standalone tracker forgets why a task exists. Here, a task links to the exact operational record it moves — and that record shows the related work in return. No copy-pasting IDs between tools.
Illustrative. Each link is clickable both ways.
Questions
Yes. Tasks can be standalone or belong to a project; standalone tasks still appear in “my tasks” and can be moved into a project later with a bulk action.
An active employee in your organization. Assignment is to a person, not a login — someone with no account still owns work, and a terminated assignee is flagged for reassignment.
One level. A task can have subtasks, but a subtask can’t have its own subtasks — a deliberate limit that keeps the tree readable and progress meaningful.
It is derived live from task completion (excluding cancelled tasks) — never a number you maintain by hand, so it can’t drift out of date.
Type @ and a colleague’s first name in a comment; matching employees with a login get an in-app notification. You never notify yourself.
Task Management is the live core, alongside Planning & Gantt, Agile Delivery, and Time, Budget & Flexibility — see the Projects & Tasks overview.
Help Center
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.