How to Create Tasks in an ERP: Owners, Due Dates, Dependencies and Work That Repeats
For project leads, agency owners and operations heads: create tasks that people can act on, in the right order, without chasing them on WhatsApp.
Knowing how to create tasks in an ERP sounds simple until a project slips because nobody knew a task was waiting on another. A task is only useful when it says what to do, who owns it, when it is due and what must finish first.
In many Indian firms tasks live in a WhatsApp group and a whiteboard. The owner of a job changes in conversation, due dates are implied, and monthly chores are remembered by whoever remembers them. Follow-up becomes the manager's full-time job.
This guide sets out how to write and structure tasks, an illustrative example at a Kolkata interior design studio, and how Apragya's project management app handles them.
How to create tasks, step by step
A task is a single piece of work that one person can finish. A good task has an action title, a short description of what done looks like, one owner, a due date, a priority and an estimate of the effort involved.
Structure matters as much as wording. Break any task longer than a few days into subtasks. Link a task to the ones it waits for, so it cannot start early. Group tasks under a milestone or sprint so progress can be read at a higher level.
Work that happens on a rhythm, such as weekly client updates or monthly reports, should be a recurring task. When one is completed, the next is created with its own due date, and nobody has to remember.
- Write the task title as an action, such as Approve kitchen drawings.
- Describe what done looks like in one or two lines.
- Assign one owner, and add others only if they must act.
- Set a due date, priority and effort estimate.
- Add subtasks and link dependencies on other tasks.
- Make rhythmic work recurring and review overdue tasks daily.
What loose task lists cost
Chasing in chats
Managers spend the day asking who is doing what.
Work in the wrong order
A job starts before the one it depends on is done.
Forgotten repeats
Monthly and weekly chores slip when the one person who remembers is away.
Unclear ownership
Two people do the same task, or nobody does.
An example: a Kolkata interior design studio
Take an illustrative studio fitting out a three-bedroom flat in Salt Lake. Carpentry started before the client had signed off the laminate, and two site visits were wasted.
One room's tasks, in the order they must run
Measure the room
Owned by the site supervisor, due Monday.
Drawings approved
Waits for measurements; designer owns it.
Laminate signed off
Client sign-off, with the designer watching.
Carpentry starts
Blocked until the laminate task is done.
Weekly site photos
Recurs each Friday until handover.
On the next flat the carpenters could not be scheduled until the sign-off task was closed, so no visit was wasted. The weekly photo task created itself every Friday, and the client received updates without anyone setting a reminder.
How task management in ERP works in Apragya
Step 1 of 5
Create
Title, description, type, priority, due date and an estimate of effort.
- Create: Title, description, type, priority, due date and an estimate of effort.
- Assign: One primary owner plus more assignees; watchers follow changes.
- Connect: Subtasks, dependencies, a milestone and a sprint where needed.
- Repeat: Daily, weekly or monthly tasks create the next one when marked done.
- Follow up: Overdue flags, response and resolution times, and a daily digest.
Task dependencies and subtasks, compared with a chat group
A chat group can hand out work. It cannot stop a job starting too early, break a big job into parts, or create next month's task when this month's is finished. Those are the structures that take follow-up off the manager's desk.
A chat group and whiteboard, compared with Apragya
| Feature | Chat and whiteboard | Apragya tasks |
|---|---|---|
| Owner | Implied in messages | Named on the task |
| Order of work | Remembered | Dependencies checked |
| Big jobs | One vague line | Subtasks |
| Monthly chores | Remembered by someone | Recurring tasks |
| Overdue work | Found when asked | Flagged the next morning |
| Views | One list | Board, list or tree |
Checked against public information on 16 September 2026.
A recurring task setup that runs itself
AI priority
A ready-made agent suggests priority for new tasks.
AI assignee
Owners suggested from skills, load and past speed.
From tickets and forms
Support tickets and public web forms can create tasks.
Timers
Start a timer on a task and log the hours when you stop.
Phone-friendly
Team members update tasks from the web app on their phones.
Access by role
People see the projects and tasks their role allows.
Tasks sit inside projects and roll up to milestones. Read tasks software, and for what can run on its own, how to automate tasks.
Getting started
- Pick one live project and list its work as tasks.
- Give each task one owner and a due date.
- Link the tasks that must wait for others.
- Turn repeating chores into recurring tasks.
- Review overdue tasks in a short daily stand-up.
Keep task titles as actions a person can finish. Vague tasks stay open for ever.
What it costs to start
Creating tasks, answered
Can a task have more than one assignee?
How do recurring tasks work?
Can we stop work starting in the wrong order?
Can outsiders raise tasks?
What does it cost to start?
Stop chasing and start assigning
Put one project's work into tasks with owners, due dates and dependencies.