Tasks & recurring work

Tasks are where the work actually happens: assignees, status, planned hours, journals, checklists, and the time log all live on the task.

Anatomy of a task

Every task belongs to a project and carries:

• Assignees — the people doing the work. Assignment controls visibility for members and drives the calendar.
• Status and priority — where it stands and how urgent it is.
• Planned hours and schedule — how much effort, laid out across specific dates.
• A journal — running notes that keep context with the work instead of in someone’s inbox.
• A time log — the recorded hours, entry by entry.

Client and contact links are project-scoped, so a task can only reference people who actually belong to that engagement — one of many small guardrails that keep data coherent.

Recurring work, done right

Most tools model a weekly duty by cloning a task fifty-two times, and the clutter buries your board within a month. PMOlikePRO models recurring work as one task, worked over time: a single entity with a schedule that materializes hours onto the dates it recurs.

That means:

• One place for the journal, the checklist and the full time history.
• Progress and cost accumulate on one record instead of being scattered across clones.
• Extending the schedule is an edit, not another batch of copies.

Scheduling hours

A task’s planned effort is distributed across dates — visible both on the task and on the team calendar. When lifecycle changes happen (a project pauses, a task is cancelled), the schedule follows the lifecycle rule: hours already worked stay, future plans are cut.

Logging time

Hours are logged directly on the task, and each entry lands in the organization’s append-only time ledger. Time tracking covers how the ledger works and why it is built to survive an audit.