A full day of work. Only some hours recorded.
Friday arrives and the timesheet is incomplete. No one can reliably explain how much effort each project needed.
Key facts
- Approval
- Manual time tracking is included in every plan; manager approvals start with Core.
- Where hours land
- An hour belongs to a task, the task to a project and client, so time reaches the cost report without re-entry.
- Not available yet
- Private desktop capture is in development.
The next step becomes clear.
Record time, review it and link it to the work. Follow the effort behind each project without relying on memory.
See the next connection
Workspace / Website launchNWebsite launch
This week’s workload
8—12 SepWhat stays connected.
The details behind the workflow, including what is available and what is still planned.
THE CONNECTION
Capture, personal review and approved work time are separate steps. Application names, domains and duration help a person reconstruct their working day. Reviewed entries can then be linked to the relevant work. Confirm device support and the workspace review process before introducing capture to a team.
Read about access boundaries Connect time and cost
App names, domains and duration
The capture policy covers application names, domains and duration. It excludes screenshots, keystrokes, page contents and document titles.
The person controls capture
The planned capture experience includes consent, pause, exclusions and deletion. Managers do not receive a raw browsing-history feed.
Private activity becomes approved time
Time Intelligence is being developed to suggest task and client allocations. A person reviews each suggestion; approved time can then inform management and finance.
Also in the system
Desktop and browser capture, private timeline, task allocation, timesheets and capacity. Desktop distribution and AI allocation are release-dependent.
How time becomes approved time
Time tracking and timesheets are available today. Private desktop and browser capture is in development and keeps three separate steps: capture, personal review and approval.
Log time against the work
Record hours on the task or client they belong to, or complete a timesheet for the week.
Review before sharing
In the planned capture flow, the person first sees their private activity (app names, domains and duration) and decides what to share.
Approve the hours
Management and finance reports use approved time, not raw activity.
Use it for cost and capacity
Approved hours explain the delivery cost of a project and show how much time the team really spends on each client.
Who uses it
- Team members
- Keep control of private activity. Nothing from capture is shared before they review it.
- Managers
- See approved hours by task and client, not a raw browsing feed.
- Finance
- Uses approved time to explain what delivery cost.
Available today and in development
| Time tracking, timesheets and attendanceAll plans | Available |
|---|---|
| Approved time linked to tasks and clients | Available |
| Desktop and browser captureConfirm the rollout for your workspace and devices. | In development |
| Time Intelligence: allocation suggestions | In development |
| Additional Time Intelligence | Planned |
| Screenshots, keystrokes, page contents and document titlesNever recorded by design. | Not included |
What it replaces
Time is usually rebuilt at the end of the week from memory, calendars and browser history, or not recorded at all. That leaves project cost as a guess. PLYNTUM links reviewed time to the work and keeps private activity private until the person shares it.
- Standalone timer apps
- Timesheets in a separate file
- Monitoring tools that take screenshots
Your first week
- Agree with the team which work should carry time and who approves it.
- Log one week of time against tasks and clients.
- Review the approved hours for one project and compare them with the plan.
Connected areas
Common questions
Start with the work that keeps getting stuck.
Bring one project into a connected workspace. See the work, the people and the cost together.