Tally
Mitarbeiter-Aktivitätsmessung ohne verdeckten Modus: sichtbarer Windows-Agent, kategoriebasierte Berichte, Stundenzettel aus aktiver Zeit, und Mitarbeitende sehen, wer ihre Daten angesehen hat.
What is collected is visible, and hidden from no one
Tally is an employee activity and timesheet tool that measures the day a team spends at the computer. The Windows agent sits openly on the employee's machine with a tray icon; it collects which application was used for how long, which domain the browser went to and when the computer sat idle. Everything collected is sorted into categories, active time turns into a timesheet, and a manager sees the report for their own team.
We built the product out of our own team's need and never changed the first decision: monitoring is not covert. The agent cannot be hidden, keystrokes are not recorded, camera and microphone are never touched, the full address of a visited page is not kept. On first launch the employee sees, item by item, what is and is not collected, and not a single record reaches the server before they consent.
The second decision that sets the product apart follows from the first: the person being monitored sees too. Every employee follows their own report card, their own activity and who looked at their data and when, from their own panel. Every look a manager takes lands in an immutable access log. Measurement stops being something the parties have to trust each other about and becomes something that can be proven.
- A visible Windows agent: the tray icon cannot be removed, no data leaves without consent
- Application, window title and domain only; never keystrokes or full addresses
- Active, idle and locked time are counted separately; the timesheet comes from active time only
- The employee sees their own data and who looked at it
The screens a manager and an employee live in
The same data is read from two sides. A manager asks who did what today, which device went quiet and what the timesheet says at month end; an employee asks about their own day, their own timesheet and who looked at their data. Both sides work on a single record.
Manager dashboard
Today's summary, a two-week trend, category distribution, the most used applications and devices that need attention on one screen.
Activity
Who used which application for how long: start, duration, application, window title and domain; date, person, device and type filters; CSV export.
Devices
Agent health: last seen, version, operating system, pending queue and last error; revoking and restoring access.
Timesheet
Monthly total and day-by-day detail; in-hours and out-of-hours in separate columns; leave, holidays and shifts taken into account; CSV and a printout with a signature line.
Access log
Who looked at whose data, from which screen, with which filter: an immutable record. Looking at your own data is not logged.
Compliance report
Devices missing consent, retention overruns and the never-collected list on one read-only page; this is the page you take to an audit.
Categories and rules
Rules that match on process name, domain or title; productive, neutral and unproductive labels; whatever no rule matches waits in the classification queue.
My report card
The employee's own panel: their own day, their own activity, their own timesheet, their own devices and who looked at their data.
The heart of the flow
How a work day is measured
At short intervals the agent looks at the foreground application: its name, the window title if that setting is on, and only the domain if it is a browser. After a period without interaction the interval counts as idle; locked when the screen locks, off when the agent is off. None of the four interval types is hidden and none blends into another. When the connection drops no record is lost; the agent holds them and sends them in order once the connection returns.
- Foreground application, window title, domain only
- Active / idle / locked / agent off: four intervals, all visible
- A dropped connection loses no record
- Sampling and send intervals are managed from the server
From time to timesheet
Worked time is calculated from active time only; idle and locked time never enter the timesheet. A work profile states workdays and hours, the holiday calendar states public holidays, leave records state a person's own days off. A day's type is decided in a fixed order: leave if there is leave, otherwise public holiday, otherwise weekend, otherwise a workday. A day without data is written as no data, not as zero. When the month ends the employee approves the timesheet or disputes it with a reason; approval is a snapshot, and if the figure changes later a warning appears.
- In-hours and out-of-hours time in separate columns
- Work profiles, holiday calendar, leave types
- Approval and dispute: mandatory reason, mandatory resolution note
- CSV and a landscape printout with a signature line
Team scope
Visibility narrows by team. A team lead sees only their own team's activity, devices, timesheets and access log, and cannot enter the settings and rules screens. A company manager sees every team, a super admin sees the system as well. The same person can belong to several teams; removing someone from a team is not deletion, the history stays. Scope is enforced on the server, not in the menu: going to a hidden screen by address returns no data either.
- Roles: super admin, company manager, team lead, employee
- The team lead is deliberately narrow: own team only, no settings screens
- Matrix organisation: one person in several teams
- Scope is enforced server-side
Consented screenshots
The screenshot feature exists, but it is off by default and there is no such thing as an unannounced capture. A manager opens a request with a written reason; the request is asked in the employee's agent; if the employee accepts they preview it first, then send it. A refusal is reported to the server too. A request expires if left unanswered, the viewing link is short-lived, the retention period is the shortest of all data types, and looking at a frame lands in the access log as well.
- Off by default; an organisation turns it on deliberately
- Double consent: the request is asked, sent only after preview
- Expiring requests, short-lived links, the shortest retention
- Viewing a frame is logged
Collect proportionately, and prove it
The legal side of employee monitoring is patched on later in most products. In Tally it is built into the architecture. What gets collected is decided on one screen: inside or outside working hours, whether window titles are kept, whether domains are collected, whether screenshots are on, and how many days raw data, screenshots and the access log are retained. The setting propagates from the server to the agents; every change is written to the admin action log with its old and new value.
The disclosure text is versioned. Every save opens a new version and the old one is never deleted; who consented to which version, with which agent version, from where and from which address is kept. When the text changes or the collection scope widens, the affected devices fall back into re-consent. An agent waiting for consent keeps collecting but does not send.
The employee's rights are inside the product too. A person downloads their own data in one click and opens an information, deletion or objection request. Even when a deletion request is accepted the data is not removed by itself: the manager previews the number of affected records and applies it with written confirmation. On audit day you hold a single page: devices missing consent, retention overruns and the never-collected list, which cannot be changed.
- Collection limits and retention on one screen, propagated to agents from the server
- Versioned disclosure text, per-device consent records, re-consent
- Data download, information / deletion / objection requests; deletion previewed and confirmed in writing
- The never-collected list cannot be changed from settings
The capability catalogue
- Visible Windows agent with an unremovable tray icon
- Process name, window title (configurable), domain only
- Active / idle / locked / agent-off intervals
- Pause and resume: break, meeting, field, phone, note
- Works offline: records are sent when the connection returns
- Tray status screen: today's time, pending records, last send
- Installation without admin rights; silent deployment package
- New-version notification
- Manager dashboard: today, trend, category distribution
- Activity list, day summary, application breakdown
- Monthly timesheet: day by day, in-hours / out-of-hours
- Timesheet approval and dispute
- Work profiles, holiday calendar, leave records
- CSV export (Turkish Excel compatible)
- Printout with signature line
- Weekly summary email and alerts
- Productive / neutral / unproductive categories
- Rule types: process name, domain, title contains
- Classification queue and bulk assignment
- Undeletable system categories
- My report card: the employee's own panel
- Who looked at my data
- My own activity and notes
- The right to revoke my own devices
- Download my data (JSON)
- Information / deletion / objection requests
- Collection settings and retention periods
- Versioned disclosure text and consent records
- Immutable access log
- Admin action log
- Compliance report (read-only)
- Previewed deletion with written confirmation
- Teams and leads, matrix membership
- Four roles: super admin, company manager, team lead, employee
- Team scope enforced server-side
- Bulk user onboarding from CSV
- Offboarding: device, token, team and role in one action
- One identity: sign in with Vosetu Passport, no separate password
- Device health: last seen, version, queue depth, last error
- Installation report: not installed, outdated version, clogged queue
- Personal API tokens (read / write scope)
- Stride integration: a weekly active-time card on the personal dashboard
- Module market: the parts you do not use stay off
- Turkish and English, light / dark theme
Setup and packages
Tally runs in the cloud on a subscription: the panel and the server are with us, the agent is on the employee's computer. The agent installs in user scope and asks for no admin rights; for IT teams there is a silent deployment package with an integrity file. The employee signs in from the tray icon with their Passport account, accepts the disclosure text, and measurement starts from that moment.
Packages are sized by team and billed monthly per user and per device. The entry package includes the agent, activity reports, device management, timesheets and shifts and the compliance report; the team package adds teams, categories, consented screenshots, email alerts and the audit trail; the enterprise package comes with a wider quota. Every package starts with a free trial that asks for no card; the current list and prices are on the product's own pricing page.
Authentication goes through Passport, our central sign-on service: no password is stored in Tally, no separate account is created, and the employee signs in with the identity they use across Vosetu products. The agent uses the same flow; the employee's password is never stored on the machine.
- Cloud subscription; the agent in user scope, no admin rights
- Silent deployment package and integrity file
- Monthly per user and device; free trial without a card
- One identity through Passport, no password in Tally
Your first timesheet in five steps
1 · Open the organisation
Sign in with Passport, enter the organisation name, verify with the code sent to your email.
2 · Draw the limits
In collection settings decide what is collected and for how many days it is kept; write your disclosure text.
3 · Set up the team and the hours
Add users in bulk from CSV, define teams and leads, enter the work profile and the holiday calendar.
4 · Roll out the agent
Hand the installer to employees or deploy the silent package; each employee signs in from the tray and accepts the text.
5 · Settle the rules
At the end of the first week look at the classification queue and attach frequent applications to categories; at month end the first timesheet goes out for approval.
Technology
- Windows, .NET 9
- Single-file install, no extra runtime needed
- No browser extension needed
- .NET 9 Web API
- PostgreSQL
- Personal API tokens
- Angular 20
- Turkish and English, light / dark theme
- Docker containers, continuous delivery with Jenkins
- Passport single sign-on
A monitoring tool is not measured by how much it collects, but by whether it can prove to the person being monitored what it does not. When an employee looks at their own data and sees exactly what the manager sees, that is the shortest path to that proof.
Frequently asked
What is Tally and what is it for?
Tally is a monitoring tool that measures employee activity on Windows computers and turns it into a timesheet. A visible agent collects usage at the level of application, window title and domain; active, idle and locked time are counted separately; a manager sees team reports, and an employee sees their own data and who looked at it.
Does Tally record keystrokes or the screen secretly?
No. Keystrokes, camera and microphone recording, the full address of a visited page, file contents and unannounced screenshots are not collected; this list cannot be enabled from settings. The screenshot feature is off by default, and even when it is on, no frame is sent without the employee's consent and preview.
Does the employee know they are being monitored?
Yes, it cannot run without their knowledge. The agent sits in the tray with an icon that cannot be removed, and no record reaches the server until the disclosure text showing what is and is not collected has been accepted on first launch. The employee also sees from their own panel who looked at their data, when and from which screen.
How is the timesheet calculated?
Worked time is calculated from active time only; idle and locked time are excluded. The work profile sets workdays and hours, the holiday calendar sets public holidays, leave records set personal leave; time is shown in separate in-hours and out-of-hours columns. At month end the employee approves the timesheet or disputes it with a reason.
Is Tally compliant with personal data law?
Proportionality is built into the product: collection limits and retention periods are set on one screen, the disclosure text is versioned and every consent is recorded per device, the employee can download their data and open an information, deletion or objection request. Every access lands in an immutable log; the compliance report shows devices missing consent and retention overruns on one page. Establishing the legal basis and the wording of the disclosure text remain the organisation's responsibility.
Is data lost when the internet drops?
No. While there is no connection the agent holds the records on the machine; when it returns they are all sent in order, and no record is counted twice.
Does installing the agent require admin rights?
No. The agent installs in user scope and asks for no admin rights. For IT teams there is a silent installation package with an integrity verification file. When a new version is released the agent notifies; the decision to install stays with the user or the IT team.
Can a team lead see everyone's data?
No. A team lead sees only their own team's activity, devices, timesheets and access log, and cannot enter the settings and rules screens. Scope is enforced on the server, not in the menu. A company manager sees every team, and a super admin sees the system settings as well.
Try transparent monitoring with your team
Tell us the size of your team and what you want to measure; we will set up the collection limits, the work profile and the team scope together with you. You will be talking to the team that wrote the product, not a sales team.
Machen wir heute den ersten Schritt
Beschreiben Sie Ihren Bedarf in einer Nachricht; wir melden uns innerhalb von 24 Stunden.