Tracked work

#What Tracked work does

Two views of the same hours — a timeline of what happened, and editable weekly timesheets per person.

• Timeline. Logged and planned work over time, across the whole workspace, so a week is something you can look at rather than reconstruct.
• Editable timesheets. Hours per person per day, each day measured against a standard working day. Fix it now, not at invoice time.
• Filter to the question. By person or by project — the difference between a list and a tool once you have twenty projects running.
• Read without write. A viewer role can read tracked time but not change it, which is exactly what a client or a finance contact should have.

#Why it exists

Time is logged in a dozen places and reassembled at month end, from memory. What you invoice is a reconstruction, and everyone knows it.

Every hour logged against a project shows up here immediately — as a timeline across the workspace, and as weekly timesheets you can correct while you still remember.

#Two views of the same hours

• Timeline. Logged and planned work over time, across the workspace — a week you can look at rather than reconstruct.
• Timesheets. Hours per person per day, editable, each day measured against a standard working day.

Filter by person or project, or clear the filters to see everything. Correct the week while you still remember it — that is the whole point of having it here rather than at invoice time.

#On the MCP surface

Hours are the raw material for invoices — your AI reads the same logged time that Billing pulls from, so a question about what a project has cost has one answer, not two.

#Works with

• Projects. Milestones, time logs and budget — per project.
• Billing. Quotes and invoices, PDF-ready, OCR-numbered.
• Tasks. Status, priority, project and sub-tasks.