Review deliverables
Client launch / Northstar
PLETOX / TASKS & PROJECTS
Your team. Your work.
A clear way forward.
Bring tasks, projects, and client work into one shared workspace. Connect the brief, the owner, and the next step so everyone knows what needs attention.
Acme Industries Work workspaceCLIENT LAUNCH / PROJECT WORKSPACE
A shared plan. A visible next step.
To do1
In progress2
Prepare launch plan
Client launch / Northstar
Collect reference files
Client launch / Northstar
Completed1
Confirm client brief
Client launch / Northstar
Client launch / All tasks4 tasks / 1 completed
| Task | Owner | Due date | Status |
|---|---|---|---|
| Confirm client brief | Asha Shah | 21 Sep | Completed |
| Prepare launch plan | Rohan Patel | 24 Sep | In progress |
| Collect reference files | Riya Desai | 23 Sep | In progress |
| Review deliverables | Meera Rao | 27 Sep | To do |
THE EVERYDAY DETAILS OF GETTING WORK DONE
Plan it. Own it.
Keep it moving.
Give the work structure without separating it from the people, clients, and conversations around it.
Tasks & ownership
Keep task briefs, assignees, priorities, and due dates together.
Projects & phases
Group related tasks into projects and organize delivery stages.
Subtasks
Break larger tasks into smaller actions with clear context.
Client-linked work
Connect tasks to the relevant customer or lead for better follow-ups.
List, board & calendar
Review the same work through the view that suits the moment.
Files & reference material
Keep task and project files available alongside the work.
Worklogs & time context
Connect enabled activity and time records with delivery progress.
Members & followers
Include the people who need visibility into a project or task.
Task acceptance
Make the assignee response visible before assuming work has started.
Hierarchical approvals
Bring configured department-level oversight into eligible task assignments.
Task activity updates
Keep progress notes, authors, and timestamps with the task.
Completion visibility
Review task status and completion reports to guide follow-ups.
MAKE THE NEXT ACTION CLEAR
A task with context.
An owner who can act.
Give each piece of work a clear brief, a responsible person, and a due date so the next step is easier to follow.
Start with a clear brief
Keep the task description, priority, and dates with the work instead of scattered across messages.
Assign responsibility
Give tasks an owner and include the relevant team members or followers.
Break down the work
Use subtasks to separate smaller actions while keeping the parent task in view.
Task visibility and actions follow your configured permissions and workflow.
RP
Prepare launch planRohan Patel / Client launch
In progressThe brief
Prepare the delivery plan, confirm the handoff dates, and collect team feedback before the client review.
- Due date
- 24 September
- Priority
- High
- Project phase
- Planning
- Client context
- Northstar
Subtasks1 of 3 completed
- Review the approved briefCompleted / Rohan Patel
- Outline delivery datesIn progress / Rohan Patel
- Collect team feedbackTo do / Project team
TASK ACCEPTANCE
Assigned is a start.
Acceptance makes it clear.
Let the assignee acknowledge the task before the team assumes the work is underway.
Review the assignment
Check the brief, due date, and expected outcome before accepting the work.
Make the response visible
Keep acceptance or rejection visible so the person assigning the task can follow up.
Separate acceptance from progress
An accepted task can still be not started. Update progress as the work actually moves.
Available acceptance actions follow your configured workflow and permissions. Acceptance is not completion.
RP
Prepare launch planAssigned to Rohan Patel / Due 24 Sep
Assignment acknowledged
Rohan has accepted responsibility for preparing the launch plan.
- Assigned by
- Asha Shah
- Assignee
- Rohan Patel
- Response
- Accepted
- Work status
- Not started
- Assignment receivedBrief and due date available to the assignee.
- Responsibility acknowledgedResponse is visible for follow-up.
- Work has not started yetProgress is updated separately.
HIERARCHICAL TASK APPROVAL
The right reviewer.
Before work moves forward.
Bring department-level oversight into task assignments where your organization requires hierarchical approval.
Respect department ownership
Route eligible cross-department assignments through the receiving department's HOD when enabled.
Keep the decision visible
Show whether the task is awaiting approval, approved, or rejected instead of hiding the review state.
Distinguish approval from completion
Approval authorizes the task to proceed through its workflow; task progress remains a separate record.
Approval routing depends on company settings, department relationships, and authorized reviewers. Not every task requires HOD approval.
Review launch deliverablesCross-department task / Example review
Pending HODReceiving department / Design
HOD approval is enabled for this cross-department assignment.
- ASAsha Shah / Task creatorOperations requests a deliverable review.
- VKVikram Kapoor / Design HODReviews the assignment before it proceeds.
- MRMeera Rao / Proposed assigneeDesign team member assigned to the work.
- Approval decision
- Awaiting reviewer
- Task progress
- Not started
Illustrates department-level routing, not an assumed unlimited approval chain.
TASK ACTIVITY UPDATES
The status tells you what.
The update tells you why.
Keep progress notes and task activity together so the team can understand what changed and what needs attention.
Add context to the status
Share an update alongside the task's progress so a label is not the whole story.
See who updated the work
Review activity with the author and timestamp attached to each recorded update.
Follow up with the full picture
Use earlier notes to understand blockers, decisions, and the next action without rebuilding the conversation.
Activity visibility and editing follow permissions. Task updates are working records, not an immutable compliance audit.
RP
Prepare launch planActivity / Illustrative update sequence
In progress- RPRohan Patel / 22 Sep, 09:30 AMIn progress
Reviewed the brief. Drafting the delivery dates and team handoffs.
- ASAsha Shah / 22 Sep, 11:10 AMProject update
Please include the client review before the final handoff.
- RPRohan Patel / 22 Sep, 02:15 PMIn progress
Added the review step. Waiting for the design team's estimate.
Next follow-up
Confirm the design estimate before finalizing delivery dates.
FROM THE BRIEF TO THE FINISH
One project.
A shared plan for delivery.
Organize related tasks into projects and phases, with team members and dates that give the work a common direction.
Give the work a home
Group tasks under the project and keep its description, owner, and timeline together.
Organize around phases
Separate stages of delivery so teams can follow what is being prepared, worked on, or completed.
See progress in context
Review open and completed tasks without assuming every completed task means the project is ready to close.
Project progress reflects recorded task status. Confirm scope and acceptance with your team before closing work.
Client launchProject lead / Asha Shah
In progress- Start date
- 21 September
- Due date
- 30 September
- Team members
- 4 people
- Recorded completion
- 1 of 4 tasks
Task completion25%
- Discovery / 1 taskClient brief confirmed
- Planning / 2 tasksLaunch plan and reference files in progress
- Review / 1 taskDeliverable review still to do
Task counts show recorded progress, not final client acceptance.
CLIENT CONTEXT BESIDE THE TASK
Remember the client.
Keep the next promise visible.
Connect tasks to the customer or lead they concern, so follow-ups carry the context your team needs.
Link the work to the relationship
Keep the relevant customer or lead associated with the task.
Make follow-ups owned
Assign the next action and due date instead of leaving a client commitment in a message thread.
Coordinate the handoff
Keep the project, task, and responsible team aligned as work moves between people.
Client-linked work is not automatic external access. Visibility follows the permissions configured for your team.
NS
NorthstarSample client / Launch project
Internal viewNext client commitment
Prepare the launch plan for review on 24 September. Rohan owns the task; Asha coordinates the project.
- Linked task
- Prepare launch plan
- Task owner
- Rohan Patel
- Project lead
- Asha Shah
- Due date
- 24 September
- Brief confirmedDiscovery task completed
- Plan being preparedNext follow-up stays with the assigned task
Customer context does not grant external access to this workspace.
UPDATES THAT STAY WITH THE WORK
Less catching up.
More moving forward.
Keep supporting files and work updates close to the task or project they belong to.
Keep reference files accessible
Use task and project file views so the team can find the material behind the work.
Connect activity with delivery
Use enabled worklogs and time records to add context to progress, not just another status label.
Bring the right people along
Use project members and task followers to include the people who need visibility.
Recorded time and work updates provide context. They are not automatic proof of completion, billable time, or payroll eligibility.
Client launchReference material and team updates
Project files2 sample files
- Client brief.pdfReference / Added by Asha Shah
- Launch checklist.xlsxPlanning / Added by Riya Desai
Recorded workIllustrative activity
- RPRohan Patel / 1h 30mReviewed the brief and drafted delivery dates.
- RDRiya Desai / 45mCollected reference files for the launch.
Time entries provide work context; billing and payroll treatment require separate rules.
A VIEW FOR THE WORK IN FRONT OF YOU
See the detail.
Keep the bigger picture.
Move between task views to review priorities, progress, and upcoming dates without losing the underlying work.
Scan work in a list
Compare owners, dates, priorities, and statuses when reviewing a set of tasks.
Follow progress on a board
Group work by status to see where tasks are moving and where follow-up is needed.
Plan around the calendar
Review dated work alongside project timelines and use completion reports to look back.
Views reflect saved task dates and statuses. They do not automatically balance capacity or guarantee delivery dates.
Upcoming project workClient launch / September
- To do
- 1
- In progress
- 2
- Completed
- 1
- 23SEPCollect reference filesRiya Desai / In progress
- 24SEPPrepare launch planRohan Patel / In progress
- 27SEPReview deliverablesMeera Rao / To do
Follow up on the work, not a guess.
Review the owner, date, and current status before changing the plan.
WORK CONNECTED TO YOUR PEOPLE
The plan and the people.
Part of the same platform.
Connect planned work with employee records, daily activity, and the tools your team uses throughout the day.
BEFORE YOUR NEXT PROJECT
Your work questions,
answered.
See how tasks, projects, and client work fit together in Pletox.
Book a demoYes. Use projects for internal initiatives and client delivery, with related tasks, team members, dates, and phases. Tasks can carry customer or lead context where relevant.
Yes. Tasks support an assigned owner, priority, start and due dates, and a description. Larger tasks can be broken into subtasks. Available actions follow your team permissions.
Tasks have list, board, calendar, and file views. Projects also have views for their related work. Each view presents saved records; it does not automatically assign capacity or resolve scheduling conflicts.
Phases organize related tasks into delivery stages within a project. Your team defines the structure and updates task progress. Completion counts help review progress but do not replace project acceptance.
Yes. Task and project file views help keep reference material accessible in context. Access depends on the permissions and sharing settings enabled for your organization.
Tasks and projects describe planned work, ownership, and delivery. Worklogs, visits, and time records describe activity and outcomes. Use the enabled workflows together to compare the plan with recorded work.
Linking a task to a customer or lead does not automatically grant external access. Confirm internal visibility, project membership, and any client-facing access requirements during setup.
The assignee can acknowledge the task through the enabled acceptance workflow. The response helps the assigning team follow up, while work status tracks progress separately. Acceptance does not mean the task has started or finished.
When cross-department approval is enabled, eligible assignments can require approval from the receiving department HOD. Pending, approved, and rejected decisions remain visible. Routing depends on company settings, departments, and reviewer permissions; not every task requires the same approval path.
Yes. Task activity includes written updates with the author, timestamp, and recorded status or approval context. Use updates to explain progress and blockers. Visibility and modification follow the configured permissions.
Use task dates, status views, filters, and available completion reports to review progress and identify follow-ups. Keep owners and due dates current so the views reflect how your team is working.