Organize work with phases and tasks

Every project breaks down into phases, and every phase holds tasks. Phases give you the big buckets of work (Discovery, Build, Cutover); tasks are the individual, assignable units of work inside them.

Every task has exactly one of four statuses, and these are the same four columns you'll see on the Kanban board:

On a PSA-synced project, a task can carry one primary resource plus one or more secondary resources — the same distinction your PSA uses, so time logged by either shows up correctly on the ticket or task. On a Current-native project, a task simply has a single assignee.

• ＋Priority is Low, Medium, High, or Urgent, and drives sort order on lists and boards.
• ＋Start and end dates drive the Timeline and the critical-path calculation — see "What is a critical path (and how Current finds it)".
• ＋Estimated hours is left blank until you set it — a blank estimate is treated differently from a 0-hour estimate, so don't zero it out just to clear it.
• ＋Two Current-only flags — Critical and Milestone — can be set directly on a task without ever touching your PSA. See "Milestones: what they are and where they show up".

Each phase has its own Due date, shown and edited right in the phase header on the Overview — click the date and pick a new one, just like a task's due date. On a PSA-synced project the new phase date is pushed straight to your PSA; on a Current-native project it lives in Current. Only project managers and admins can change it.

If you set a task's due date to a day that falls after its phase's due date, Current stops and asks before changing anything: an "Extend the phase to fit this date?" confirmation that names the phase, its current end date, and the new date it would move to. Choose to extend and the phase's end date moves out to fit the task; choose Cancel and nothing changes. On an Autotask-synced project this is what keeps you from hitting Autotask's "the phase wouldn't extend — move it in Autotask and retry" wall: Current widens the phase in Autotask for you.

Date changes made anywhere else — the task drawer, the Timeline, the Schedule grid, a bulk edit — self-heal automatically on Autotask-synced projects. After every date push, Current reads the record back to confirm Autotask really stored it (Autotask can say "OK" and quietly keep its old date when the new one falls outside its phase or project window). If the date didn't stick, Current widens the window the same way Autotask's own UI would — project end first, then the phase — pushes the date again, and verifies. The toast tells you when a window was extended. When Autotask still won't store a date, the toast names the real cause: an Autotask predecessor drives the task's schedule, or the task is marked complete there — and the project's sync badge turns red so it isn't forgotten. ConnectWise pushes are verified the same way: every date write is read back, and a date the PSA didn't store is reported rather than silently assumed.

On a long project, click the little arrow at the left of any phase header to collapse it — that phase's tasks fold out of view so the Overview stays scannable, while the phase name, task count, and progress stay visible. Click again to expand. Current remembers which phases you've collapsed for each project, and that preference follows you across browsers and devices.

Click any task to open its drawer. From there you can change status, assignee(s), priority, dates, description, estimated hours, and checklist items (each item can carry a link to a supporting document). You can also add or remove dependencies and log time without leaving the drawer.

1. 1
   Open the task

   Click it from the board, list, or timeline.
2. 2
   Make your edits

   Changes stage locally as a draft — nothing saves until you click Save, and closing without saving discards the draft (Current asks first).
3. 3
   Watch for the cascade-confirm prompt

   If you move a start or end date and other tasks depend on this one, Current asks whether to move those downstream tasks too, before saving anything.
4. 4
   Save

   Your changes write to Current and, for PSA-synced projects, push to your PSA on the next sync pass.