TimerOS documentation

TimerOS is a time-management platform for teams and freelancers. What each surface does — the Windows desktop app, web app, admin dashboard and client portal.

The TimerOS desktop app is the only place your work time is tracked — an always-on-top timer bar plus a dashboard window. Install it on Windows in four steps.

Register, pick a plan, then build your structure — departments, roles and invited members — and define the shifts that turn out-of-shift work into overtime.

Your first tracked day starts once onboarding is done and the timer bar is running. How every second is attributed to a state, and how to correct a wrong label.

Sign in to the Windows desktop app, work as you normally would, and watch the hours land on your dashboard. A two-minute walkthrough of your first tracked time.

Open the transparency view in Settings, see why your current activity was labelled productive or idle, and teach the on-device model when it gets one wrong.

Create your first client, then a billable project attached to them — name, budget structure, milestones and team — in about two minutes, on any TimerOS plan.

Turn tracked work into money: create an invoice for a client, mark it sent so it reaches their portal, and record the payment when it lands. In three minutes.

Add a contact to a client record, set their per-area portal permissions, and send the branded invitation that lets them set their own password and sign in.

Send an email invite from the website dashboard, pick a dashboard role and placement, and watch your seat count. Inviting teammates needs Startup or above.

Create a shift template, assign it across your team calendar, then follow a time-off request from submission through approval and the leave-balance deduction.

Read a week of tracked time: how it split across activity states, where per-project effort and per-client money live, and how to export the week as CSV or PDF.

TimerOS decides productive vs idle on your own device — a scored rule engine first, a small on-device model as fallback. No cloud AI, no LLM, no screenshots.

Every second the desktop timer runs lands in one of six states — productive, idle, break, overtime, off-work, offline. What each means and how a day is stored.

Shifts define when each person is expected to work and shape how time is labelled — productive inside a shift, overtime outside it — and they anchor leave.

Projects are how you organise work in TimerOS: milestones, tasks and subtasks, budgets and burn-rate, tracked time, and what clients see in the client portal.

Company and team goals, an awards leaderboard earned from completed goals on Startup and above, and the personal Achievements page solo Freelancer users get.

Shape your workspace into departments and teams, place people into roles, and control what each person can see and do — with depth of control scaling by plan.

Payroll turns assigned shifts and approved leave into salaries, deductions and payslips, per pay period and per team. An Enterprise capability, in early access.

Bill clients, log expenses, watch profit move in real time and let clients pay invoices online — plus managing your own subscription on the website dashboard.

A per-tenant branded web app where your clients sign in to follow projects, pay invoices, raise incidents, approve change requests and accept your notices.

TimerOS turns tracked time into per-state breakdowns you can read, compare across periods and export as a CSV or PDF. Reporting is role-aware and plan-aware.

Per-workspace data isolation, role-based permissions, TOTP two-factor, and on-device activity classification that never sends raw window titles off-device.

Connect Claude to your TimerOS account over one hosted MCP URL. It acts as you, sees only what you see, and every change it makes is logged with its undo call.

A public API, personal access tokens and webhooks are on the TimerOS roadmap, not yet released. The one shipped integration is the AI assistant connector.

Open a support ticket from the dashboard, email support@timeros.ai, or check the changelog, roadmap and status page. Response targets come from our SLA.