Tasks are where real work happens. In PrjNx, tasks represent actionable units of responsibility—not just to-do items. When used correctly, tasks help teams stay aligned, accountable, and focused on outcomes.
This guide explains how to create and manage tasks in a way that supports clear execution, not micromanagement.

What Makes a Good Task?
Before creating tasks, it’s worth understanding what good looks like.
A well-defined task should:
- Represent one clear piece of work
- Have a clear owner
- Be easy to understand without extra explanation
- Contribute directly to a milestone or project outcome
PM Insight:
If a task needs a meeting to explain it, it’s probably too big.

Step-by-Step: Creating a Task in PrjNx
Step 1: Open Your Project
Navigate to the project where the work needs to be tracked.
Tasks always live inside projects, ensuring context and visibility.

Step 2: Add a New Task
Choose the option to create a new task within the project.
At minimum, provide:
- Task title
- Short description (optional but recommended)
Use task titles that describe what will be delivered, not what activity will occur.

Step 3: Assign an Owner
Assign the task to one person who is responsible for its completion.
Even if multiple people contribute:
- One owner ensures accountability
- Collaboration can still happen through comments and updates

Step 4: Set Due Dates (If Applicable)
If the task has a clear deadline, set a due date.
Due dates help:
- Prioritize work
- Trigger reminders and notifications
- Support progress tracking
Avoid setting artificial deadlines just to “fill the field.”

Step 5: Save and Start Work
Once created, the task becomes part of the project workflow and is visible to the team.
From here, team members can:
- Update status
- Add comments
- Attach files
- Log time (if enabled)

Managing Tasks Effectively
Creating tasks is only half the job. Managing them well is what keeps projects moving.
Updating Task Status
Encourage team members to keep task statuses current. This reduces the need for follow-ups and status meetings.
Statuses should reflect real progress, not intent.

Using Comments for Context
Comments should be used to:
- Share updates
- Ask questions
- Clarify requirements
- Capture decisions
This keeps communication tied directly to the work.

Editing Tasks as Work Evolves
It’s normal for tasks to change as projects progress.
You can:
- Update descriptions
- Adjust due dates
- Reassign ownership
- Break tasks into smaller pieces
Flexibility is built into PrjNx—use it intentionally.