Skip to content
Platform

Work items, sprints, and milestones in one hierarchy

Tasks carry status, type, priority, assignee, and dates. Sprints pace the work, milestones give it a dated outcome, and timers make the hours honest enough to bill from.

  • Five statuses, fully customisable
  • Sprints and milestones
  • Timers, timesheets, billable hours
ProjectNorthwind Digital
Sprint 4New sprintDay 3 of 11 · 8 working days left
26%done
Sprint 4Active
Aug 12 – Aug 26·Payments hardening and portal

Burndown

ActualIdeal

Sprint burndown, actual against ideal

3 points behind the ideal line

Scope

19 pts

Done

5 pts

Left

14 pts

Items

1/6

Timeline

DayWeekMonthTodayTodoIn ProgressIn ReviewDone

Work item

Expired card token at checkoutPM
Portal invite emailsAR
Rate limit the status endpointDS
Timesheet export drops a row
Monthly retainer summaryKV
Portfolio componentsPM
W12
T13
F14
S15
S16
M17
T18
W19
T20
Expired card token at checkout5
Portal invite emails3
Rate limit the status endpoint3
Timesheet export drops a row2
Monthly retainer summary1
Portfolio components5
Beta launchAug 20 · 4 of 9 items done

Backlog

2 items · drag into the sprint

NWD-021Archive the legacy status subdomain2 pts
NWD-022Client-facing changelog page3 pts
How it works

From a task to a dated outcome

Structure the work once, and reporting, scoring, and client updates all read from it.

  1. 01

    Set the milestone

    A dated outcome the client is waiting on — beta launch, content migration complete — with tasks associated to it.

  2. 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.

  3. 03

    Track the hours

    Start a timer against the item. Timesheets, billable and unbilled splits, and utilisation all follow from it.

  4. 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.

Northwind Digital/Work itemsNew item
Search title or code…
Sprint 4High + CriticalDue before Aug 20Clear all6 of 42 items

The delivery primitives, not a generic ticket queue

Every field exists because reporting downstream depends on it being right.

Custom statuses

Five ship by default. Rename, recolour, reorder, archive, or add your own.

Types and priorities

Classify work so the breakdown report tells you something useful.

Views

Board, list, and per-project views so each team sees its own slice.

Comments and mentions

Discussion sits on the work item, and mentions notify the right person.

Recurring tasks

Set a recurrence rule for weekly reports or monthly maintenance instead of recreating them.

Timer security

Controls that keep tracked time trustworthy enough to invoice from.

What you get underneath

Most of this is modular — enable what your team needs under Settings → Modules and leave the rest off.

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.
WorkflowsWorkflows
Drag-and-drop automation for the repetitive parts of delivery, including signed webhook actions.
Activity logActivity log
Every state change recorded, so 'when did this move' has an answer.

Common questions

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.
Priya AnandHead of Delivery, Northwind Digital
40%
fewer missed deadlines after 90 days
12 hrs
saved per PM, per week
1
source of truth per engagement
Get started

Stop finding out about risk in the retro

Score every project, catch scope creep while it is still cheap, and give clients a seat at the table — without another status meeting.

90 days
Free, full platform
No card
Nothing to enter up front
20 min
Guided walkthrough on request