Skip to content

GuidesRolling out

Rolling out a desktop time tracker to a remote team: the first week

Updated · about 2 min

Roll Ruwad Connect out in one week: create the workspace and set capture policy on day one, invite people and let them install the tracker on day two, track for three days, approve the first timesheets on day five, and generate the first payroll run and invoice from those approved hours. Decide the capture cadence, blur and webcam policy before anyone installs anything.

The short answer. The rest of the page explains it.

Day 1: decide the policy, then create the workspace

Register on the web. Before anyone else is invited, open Capture settings and Verification settings and decide:

  • Cadence. The plan sets the cap; you can run below it. Start at the cap and lower it if the team finds it heavy.
  • Blur. On, if reviewers only need to know that work was happening; off, if they need to read what was on screen.
  • Webcam checks. Off unless you have a reason, consent and, for a team in several countries, advice.

These decisions are on the consent screen every person sees on first launch. Change them later and people are asked again, so it is better to settle them once.

Then create the projects (with a billing rate and a budget each) and the first tasks. Set each member's hourly rate on their membership so payroll can be computed.

Day 2: invite people, install the tracker

Invite each person by email with a role. They accept on the web, then download the tracker for their computer from the Download page (on Windows, the MSI if your IT team deploys software centrally), sign in with the invited account and choose the workspace.

Add your clients separately. A client is the company you bill: their projects carry the billing rate, invoices and receipts reach them by email, and they never see captures. Clients do not sign in.

Days 3 to 5: track

Ask everyone to punch in on a project and a task from their first hour. Time that belongs to a task is what approvals, budgets and invoices are built on; time punched in with no task still counts, but it cannot update a task's actual hours.

Managers can watch the Live page to see who is punched in and what they are on, and the Captures page for each person's day.

Day 5: approve

Open Timesheets for the week. Each session shows its project, breaks and work time. Select the entries that look right and approve them together; reject the one that does not. Approval updates task hours and project budgets on the spot.

Day 5, later: pay and bill

On Payroll, generate the period from approved hours. Check one person's line against their timesheet, approve the run, mark it paid, and download the payslips.

On Invoices, generate an invoice for a client and project from approved billable hours. Download the PDF or email it from the app. When it is paid, mark it paid and a receipt PDF is issued.

What to expect in week two

Fewer pending entries, because people punch in on the right task from the start; a Live page that is actually used; and reports by member and by project that export in the format your books need (CSV, XLSX, JSON, or the ClickUp and Zoho Projects layouts).

Questions

Asked about this

Do people need a workspace account before installing the tracker?

Yes. They accept the invitation on the web first, then sign in to the desktop app with that account and choose the workspace.

What does an employee see on first launch?

The consent screen, listing what the workspace records, then the project and task pickers and the timer.

Can a team member belong to two workspaces?

Yes. One sign-in can belong to several workspaces with a different role in each, and the desktop asks which one to work for.

See it on your own team.

Create a workspace and install the desktop tracker. The Free plan holds ten people and three projects.