In PPM Express, team members record time against the tasks they are already working on, and those hours feed straight into resource views next to planned effort. Project managers get actuals without chasing anyone. Resource managers finally see planned against real, which is where estimating problems surface. Timesheets move through a defined cycle, from draft to in progress to pending approval, then approved or rejected, with administrative time going to a person's direct manager and project time to the project manager. There is an API if you need the data elsewhere.
.avif)
Capacity from real work weeks, so over-allocation surfaces before you commit.
Product
Portfolio dashboards and Power BI datasets built from live delivery data.
Product
Plan, schedule and track delivery without leaving your existing tools.
Product
Last updated 20 August 2026
Time Tracking, answered.
Because planned effort alone tells you what someone was asked to do, not what the work took. Actual hours turn resource planning from an estimate into a measurement, and they are what makes the next plan more accurate than the last one.
Administrative time is approved by the person's direct manager. Project time is approved by the project manager assigned to that project. One thing to know before you plan around it: timesheet approvals are available on the Enterprise Ultra plan, not on Enterprise.
Draft, in progress, pending approval, and then approved or rejected. Having explicit statuses matters mostly for the awkward cases, when something is submitted late or sent back, because everyone can see where it actually sits rather than asking.
Time is recorded against tasks in PPM Express, including tasks that came in through a connection. So a team working in Jira or Azure DevOps does not need a separate mapping exercise for their work to be time-trackable.
Actual hours appear on the resource dashboard alongside planned, capacity and availability, viewable in hours, percent or FTE. The comparison between planned and actual sits in one place instead of requiring an export and a spreadsheet.
Yes, there is a time tracking API, plus a time report pack for the standard views. Finance teams generally want the API, because time data usually has to reach a system that was chosen long before anyone thought about project reporting.
No. It is a module, not a prerequisite. Plenty of organizations run portfolio management, resource planning and reporting without ever turning it on, and add it later when they want actuals rather than estimates behind their capacity numbers.
You configure reporting periods along with the wider time tracking settings, so submission cycles match how your organization already runs. Getting this to line up with the payroll or finance calendar is usually what determines whether people submit on time.
.svg){kind=small}
