Alongside screenshots, the client portal summarizes where your team’s clocked-in time went in two views: URLs (the websites they visited) and Applications (the desktop apps they used). Both are built from samples the desktop tracker records while a contractor is clocked in — nothing is collected off the clock.
The URLs view
Time tracking → URLs lists the websites your team visited while clocked in, grouped by domain. The Top sites table shows each site with its share of activity, the number of samples recorded, and when it was last seen. Above the table, three summary tiles give you the totals at a glance: samples recorded, domains touched, and the share of activity that landed on work tools.
A By category card then buckets those same domains by site type — work tools, communication, reference and docs, and other — so you can see the shape of a week without reading the whole table. The categories are a grouping of the real domains recorded; no extra data is collected to build them.
The Applications view
Time tracking → Applications works the same way for desktop software: the apps your team used while clocked in, grouped by app, with activity share, sample counts, and last-seen times. Summary tiles show total samples, how many apps were used, and the top app for the view.
Here the privacy boundary is the application name only. Window titles, document names, and content are never captured or shown — you’ll see that a contractor was in a spreadsheet application, not which spreadsheet.
Reading the numbers
Both views count samples — periodic observations taken while a contractor is clocked in — rather than a continuous recording. That has two practical consequences:
- Shares are proportions of sampled time. A site with 40% activity took roughly 40% of the sampled clocked-in time in the view, which is a good signal of where attention went.
- Short visits may not register. A page opened for a few seconds can fall between samples. Treat the tables as a picture of where time concentrated, not an exhaustive browsing history.
If a view is empty, no samples have been recorded yet — activity appears once your team browses or uses apps while clocked in.
Using activity data well
This data is most useful as context for your weekly review, next to screenshots and evidence:
- Sanity-check a week before approving. If hours look high, a glance at the top sites and apps usually confirms the time went into the tools the role actually uses.
- Spot drift early. A falling work-tools share across weeks is worth a conversation about scope or blockers — well before it becomes a dispute.
- Keep it proportionate. Domain and app names tell you where time went, not whether the work was good. Judge quality from the work itself and the evidence attached to timesheets.