Work items, sprints, and milestones in one hierarchy
Tasks, sprints and milestones in one hierarchy, with timers you can bill from.
- Five statuses, fully customisable
- Sprints and milestones
- Timers, timesheets, billable hours
Burndown
ActualIdeal
3 points behind the ideal line
Scope
19 pts
Done
5 pts
Left
14 pts
Items
1/6
Timeline
Drag bars to reschedule · edges to resize
Work item
Backlog
2 items · drag into the sprint
- / fewer missed deadlines after 90 days
- 40%
- / saved per PM, per week
- 12 hrs
- / source of truth per engagement
- 1
From a task to a dated outcome
Structure it once. Everything reads from it.
- 01
Set the milestone
A dated outcome the client is waiting on — beta launch, content migration complete — with tasks associated to it.
- 02
Pace it in a sprint
A fixed window with work in it, for teams that care about throughput over time. Velocity is derived from status categories.
- 03
Track the hours
Start a timer against the item. Timesheets, billable and unbilled splits, and utilisation all follow from it.
- 04
Automate the repetition
Workflows handle the when-this-then-that: status changes, assignments, notifications, and webhook calls.
Filter down to the work that actually needs you
Every list filters on status, type, priority, assignee, sprint, milestone, and start or due date range, plus a triage flag for anything that arrived without an owner. Select an item and the panel carries its subtasks, dependencies, labels, SLA clock, and logged time.
The delivery primitives, not a generic ticket queue
Every field feeds reporting downstream.
- 01
Custom statuses
Five ship by default. Rename, recolour, reorder, archive, or add your own.
- 02
Types and priorities
Classify work so the breakdown report tells you something useful.
- 03
Views
Board, list, and per-project views so each team sees its own slice.
- 04
Comments and mentions
Discussion sits on the work item, and mentions notify the right person.
- 05
Recurring tasks
Set a recurrence rule for weekly reports or monthly maintenance instead of recreating them.
- 06
Timer security
Controls that keep tracked time trustworthy enough to invoice from.
What you get underneath
Modular: switch on only what you need.
- SprintsSprints
- Timeboxed cycles with velocity derived from status categories, so throughput is comparable sprint to sprint.
- MilestonesMilestones
- Dated checkpoints that work rolls up to, and that delivery confidence scores against.
- TimesheetsTime tracking
- Per-person timesheets with billable and unbilled splits, feeding utilisation and invoicing.
- Capacity and utilisationReports
- Tracked hours against capacity per person — who is stretched and who has room.
- SLA targetsSLA Management
- Response and resolution deadlines per task, aware of business hours and holidays, with breach alerts before you miss.
The modules behind this page.
Worksynk ships as modules a workspace owner switches on under Settings → Modules. Most are off by default even when your plan covers them; pricing shows what each plan includes.
- Plan and track01ProjectsThe unit of delivery — status, team, dates, and the settings that drive reporting.Read the guide ↗ for Projects (opens the docs)
- Plan and track02TasksStatuses, types, priorities, and the settings that make reporting trustworthy.Read the guide ↗ for Tasks (opens the docs)
- Plan and track03SprintsTimeboxed cycles for pacing the team's work.Read the guide ↗ for Sprints (opens the docs)
- Plan and track04MilestonesDated delivery checkpoints that work rolls up to.Read the guide ↗ for Milestones (opens the docs)
- Plan and track05Recurring tasksWork that repeats on a schedule.Read the guide ↗ for Recurring tasks (opens the docs)
- Plan and track06WorkflowsDrag-and-drop automation for delivery operations.Read the guide ↗ for Workflows (opens the docs)
Common questions
Is Worksynk an agile project management tool?
Yes. It has sprints with velocity and a burndown, board and list views, and milestones for dated outcomes, so a team can run Scrum-style sprints or a continuous Kanban flow in the same task management system.
Can we keep our own workflow states?
Yes. Five statuses ship by default and you can rename, recolour, reorder, or archive any of them and add your own under Settings → Statuses. Velocity and reporting read from status categories, so the numbers keep working after you change the labels.
Do we have to use both sprints and milestones?
No. Sprints suit teams working to a cadence who care about throughput; milestones suit dated outcomes a client is waiting for. Plenty of teams use one and not the other — both are modules you can leave off.
Is tracked time good enough to invoice from?
That is the intent. Timers run against the work item, timesheets split billable from unbilled, and timer security settings exist specifically to keep the hours honest enough to bill.
What happens to work that repeats?
Set a recurrence rule instead of recreating the task. The next instance appears on schedule, and editing the rule changes future instances rather than the history.
Work items, milestones and sprints finally live in one structure. Our PMs stopped maintaining the spreadsheet that shadowed the tool.
Where to go next.
/ Get started
Stop finding out about risk in the retro.
Score every project and catch scope creep early, without another status meeting.
- Free, full platform
- 90 days
- Nothing up front
- No card
- Guided walkthrough
- 20 min