Logged Time Isn't Showing Up

Time you log flows to three places: the task it was logged against, the person’s timesheet, and the Labor figure on that task’s project. If it isn’t appearing somewhere you expect, one of the two causes below is almost always why.

Where time can be logged

From a task — on the task’s own activity, against that task.
From the calendar, against a task — you pick one of your tasks and log against it.
From the calendar, with no task — the task field is optional, so you can record real work that isn’t a task.

All three produce the same kind of entry. The difference is what they’re attached to.

Cause 1 — the time was logged without a task

A time entry with no task never reaches any project. A project’s Labor cost is built from time logged on that project’s tasks; with no task there’s no project to attribute it to.

Entries like this still count as your time and still appear on your timesheet — they simply cost nothing to any job. If a project’s Labor looks too low, check whether the work was logged from the calendar without picking a task.

Cause 2 — the person has no hourly rate

Labor cost is logged hours multiplied by that person’s hourly rate, taken from their compensation record.

Someone with no compensation record, or no hourly rate on it, is priced at zero. Their hours are recorded correctly and show on their timesheet, but they add nothing to any project’s cost. This is the most common reason Labor stays at zero on a busy project.

A task’s time spent is a total, not a field

You never type how long a task took. The figure shown on a task is the sum of the time entries logged against it — to change it, add or correct an entry.

Rates change history

Labor uses the newest rate on someone’s record, not the rate in force when the work was done. Giving someone a raise re-prices all of their past logged time across every project. See A project’s margin looks wrong.