What Is a Task in Project Management? Examples and How to Manage One
A task in project management is a specific piece of work that contributes to a project’s result. Writing a homepage draft, reviewing a design and testing a contact form are all tasks.
“Launch the website” is the project. “Test the contact form on desktop and mobile” is a task within it.
A well-written task gives someone enough information to start and a clear way to know when they have finished. That makes assigning, scheduling and reviewing the work much easier.
Task, project, subtask and milestone: what’s the difference?
These terms describe different parts of the work.
| Term | Meaning | Website launch example |
|---|---|---|
| Project | A temporary effort to deliver a specific result | Launch the new company website |
| Task | An action needed to move the work forward | Test the contact form |
| Subtask | A smaller step within a task | Confirm test enquiries reach the sales inbox |
| Milestone | A significant point or event in the project | Website approved for launch |
A milestone marks a point you have reached. Tasks describe the work needed to reach it.
Tasks can also exist outside a project. Checking an enquiry inbox each morning is a recurring task. Replacing an outdated phone number on a webpage is a one-off task. Neither needs a separate project to be worth tracking.
What should a task include?
At minimum, a task should explain what needs doing, who owns it and what counts as done. Add a due date when the work has a deadline.
Here is a fictional example:
| Task detail | Example |
|---|---|
| Title | Test the contact form on desktop and mobile |
| Owner | Asha |
| Due date | 5 November, before the launch review |
| Priority | High, because visitors need the form to send enquiries |
| Status | To do |
| Instructions | Submit test enquiries, check required fields and confirm delivery to the sales inbox |
| Done when | The agreed tests pass and the results are recorded |
| Reference | Staging website link and test checklist |
The “done when” line prevents misunderstandings. Without it, one person might consider the form tested after a single submission. Another might expect checks on mobile, error messages and email delivery.
Keep the detail proportionate. “Send the approved homepage draft to the designer” may only need an owner, a deadline and a link.
Start the task name with an action
“Homepage” names a subject. “Write the first homepage draft” tells someone what to do.
Useful task names include:
- Review the pricing page for factual errors.
- Replace the old product screenshot.
- Test the signup confirmation email.
- Approve the homepage copy for design.
Keep the title easy to scan. Put the brief, references and completion requirements in the description.
Give one person responsibility for completion
Several people can contribute, but make it clear who is responsible for moving the task forward.
If Asha tests the form and a developer fixes the errors, those are separate responsibilities. Give the fixes their own tasks when they need different owners or deadlines.
Name the reviewer too, if approval is required. “Ready for review” should tell the team who needs to act next.
Separate the deadline from the effort
A due date tells someone when the result is needed. An estimate tells them how much time to allow.
A two-hour task due on Friday still needs space in someone’s schedule before Friday. Check that space exists before treating the deadline as agreed.
What is task management?
Task management is the process of organising, assigning, prioritising and tracking work through to completion.
Writing a task is only the starting point. Someone must also check whether it can begin, whether the owner has time and whether the result meets the brief.
For example, a writer may finish the homepage copy while the designer continues waiting for it. The writing is complete, but the handover has failed.
Good task management makes the next action clear: the copy is approved, the link is available and the designer can start.
How to manage tasks from start to finish
1. Break the work down where responsibilities change
Split work into separate tasks when it needs different owners, deadlines or reviews.
“Prepare the homepage” could become:
- Write the homepage copy.
- Review and approve the copy.
- Design the page.
- Build the approved design.
- Test the page before publication.
Each task produces something the next person can use.
You do not need to track every small action separately. Opening the brief and reading the references can remain part of the writing task.
2. Identify what must happen first
Some tasks depend on other work.
A designer may explore layouts before the copy is approved. Finalising the page with that copy must wait for approval.
Record the specific requirement. “Waiting for marketing to approve the homepage copy” gives the team more useful information than “Waiting”.
If the approval date moves, check the tasks that depend on it. Updating one deadline without reviewing the next steps can leave the plan unworkable.
3. Set priorities with a reason
When several tasks need attention, ask:
- Which one must be finished for the next deadline?
- Which one is stopping someone else from working?
- What happens if it waits?
Before a website launch, a broken enquiry form usually deserves attention ahead of a minor spacing adjustment. Visitors cannot send enquiries until the form works.
If urgent work arrives, decide what can move. Marking another task “high priority” does not give the owner more time.
4. Keep progress and blockers visible
Start with a simple set of statuses:
To do → In progress → In review → Done
When work stops, record the reason and the next action:
Testing is blocked because enquiries are not reaching the sales inbox. The developer needs to check the email settings before testing resumes.
A blocked task cannot move forward. An overdue task has passed its deadline. A task can be both, but each label tells you something different.
Updates should help someone act. “Three checks passed; mobile submission still fails” is more useful than “Working on it”.
5. Check the result before marking it done
Return to the completion requirements.
For the contact-form task, confirm that the agreed tests passed and the results were recorded. For a first-draft task, submitting the draft for review may be enough.
Done should describe the agreed result, not just the time someone spent working.
Why choose Skarya for team task management?
Skarya is a strong fit for teams whose tasks involve shared deadlines, handovers and project delivery. It brings project planning, task ownership, boards and time tracking into the same workspace. Teams can use Kanban boards to follow progress and Gantt charts to view scheduled work.
For a website launch, that gives you a practical way to organise the work: assign the copy, design and testing tasks, review progress on the board and check the schedule as deadlines approach.
The reason to choose Skarya here is specific: you need to manage how individual assignments contribute to a shared delivery date.
Use Kobi AI to help create tasks and summarise work
Kobi, Skarya’s built-in AI assistant, supports task creation and work summaries inside the workspace. Those capabilities address two routine parts of task management: setting up assignments and preparing progress updates.
For the contact-form task, prepare a brief with the devices to test, the expected inbox, the deadline and the completion checks. Use that detail when creating the task with Kobi, then review the result before assigning it.
As work progresses, record completed checks and unresolved errors. Those updates give a work summary useful detail for the launch review.
Have a project with several owners and a fixed deadline? Explore Skarya to see how boards, project planning and Kobi AI can support the work from assignment to completion