Timely
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Memory AS · timelyapp.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Timely at a glance
- Vendor
- Memory AS
- Headquarters
- Incorporated in Norway source, captured 16 Nov 2026
- Data hosting
- Default not stated; pages mention Europe source, captured 15 Sep 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Starting price
- “$9 usd/mo per user per mo. billed yearly” (vendor’s words) source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Timely 2/5, the mean of 6 judges. Timely is an automatic time-capture product: the opt-in Memory tracker records page titles and timestamps of active apps across web, Windows, macOS, iOS and Android, with a manual timer and admin audit of entries. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Timely is an automatic time-capture product: the opt-in Memory tracker records page titles and timestamps of active apps across web, Windows, macOS, iOS and Android, with a manual timer and admin audit of entries. Scoring peaks at project and billing, 6-7, where clients, nested projects, billable and cost rates, budgets, a time-money-cost-profit view, invoicing and a QuickBooks integration carry an agency's billing chain; pricing transparency follows at 5-6, three tiers publicly priced on both billing periods. Weakest are working time law and absence and planning at 2-3: no statute is named, no break, rest or retention rules appear, and absence is hours on non-billable projects, divided by an average workday to count days. Payroll export scores hold at 3: scheduled CSV, XLS and PDF, with no named payroll format shown. Sovereignty scores 4-5 — Timely AS contracts under Norwegian law, EEA rather than EU, hosting is stated on ISO 27001-certified AWS servers in Europe with EU-based data residency, and the sub-processor list's contents are not shown. Time capture spans 3-5 because the evidence covers desk staff, not site crews.
Speaks for it
- Automatic background capture of page titles and timestamps of active apps across web, Windows, macOS, iOS and Android, with a manual timer, idle detection and admin audit of entries
- Client, project and task tracking with billable and cost rates, budgets, a time-money-cost-profit view, invoicing by budget or hours worked and a QuickBooks integration
- Starter, Premium and Unlimited are publicly priced per user on both billing periods — $9, $16 and $22 USD per user per month billed yearly — with plan limits stated and a Tasks add-on at $5 per person
- Report exports as CSV, multi-sheet XLS or PDF timesheets with customisable columns, saved defaults, export history and scheduled email delivery
- Privacy controls documented: no screenshots or keystroke logging, private timelines shared only with user approval, and AI-drafted entries never shared without review
Held against it
- No statute is named for working-time compliance, and we found no public information on the German recording duty, break rules, rest periods or statutory retention
- Absence is a workaround of non-billable projects, with absence days computed by dividing logged hours by an average workday
- The payroll handoff is a report file, with no public information on a named payroll system such as DATEV or on night, Sunday and holiday surcharges
- Capture evidence covers desk work, with no public information on shared terminals, offline capture, badge options or geofenced check-in for site crews
- Unlimited+ appears in a plan list with no captured price, Enterprise is contact sales, and the captured pages give different statements on whether API access sits in Starter or Unlimited+
Best for
- Your desk-based agency or client-services team wants automatic capture of web and desktop app time feeding clients, rates, budgets and invoicing
- You want per-user pricing computable from public pages for a team inside the stated limits — Starter caps at 5 users and 20 projects, Premium at 50 users
- Your payroll or bookkeeping team can work from scheduled CSV and XLS report exports rather than a named payroll format
- You want automatic tracking with documented privacy limits — no screenshots or keystrokes, private timelines, AI entries shared only after review
Avoid if
- Your crews clock in at shared terminals, with badges or offline on site — the documented capture runs as apps on web, Windows, macOS, iOS and Android devices for desk work
- You must evidence the German working-time recording duty — ask the vendor: the public pages we read do not show it
- You need vacation approval workflows, entitlement balances or shift rosters — absence is booked as hours on non-billable projects with days divided out by an average workday
- Your payroll run needs a named format such as DATEV or night, Sunday and holiday surcharge handling — the documented handoff is a CSV, multi-sheet XLS or PDF report
The scores
| Criterion | Panel median |
|---|---|
| Capture in the real workplace | 2 of 5 |
| Working-time law & audit record | 1.5 of 5 |
| Absence & shift planning | 1.5 of 5 |
| Project, cost-centre & billing | 3.5 of 5 |
| Payroll handoff | 1.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
Capture in the real workplace
Show reasoningHide reasoning
How this is scored
How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
0 — Not a time-recording tool; working time cannot be captured in the product.
3 — Clocking in and out or a timer in the browser or an app, with manual entries; offline use, shared terminals and corrections are basic or not described.
5 — Web and mobile apps for clocking in and out, a shared kiosk, terminal or badge option or offline capture that syncs, and corrections requested by the employee and approved by a manager.
8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.
10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.
The Operations Lead
Automatic background capture across web, Windows, macOS, iOS and Android plus a manual timer, idle detection and editable entries is real capture for my desk staff. We found no public information on shared terminals or kiosks, offline capture that syncs, geofenced check-in with stated limits, or corrections requested by the employee and approved by a manager — the things my workshop and field crews actually clock in with. 2 7 6 1
The Payroll Officer
Automatic background capture across web, Windows, macOS, iOS and Android, with a manual timer, planned time, bulk editing and admins able to audit entries, is a real capture story — but it is a desk worker's story. We found no public information on shared terminals, badge options, offline capture or geofenced check-in with stated limits, and corrections are described as editing or deleting entries rather than a requested-and-approved flow with a trail of who changed what. 2 7 6 3
The Works Council Advocate
Automatic capture runs quietly in the background across web, Windows, macOS, iOS and Android — opt-in, storing only page titles and timestamps of active apps, no screenshots or keystrokes, the private timeline staying private until the user approves sharing and AI-drafted entries never shared without review — which is the privacy shape I want on paper. But it serves a desk workforce: we found no public information on kiosks, terminals, badge options or offline capture, corrections are documented as editable with no approval trail or audit of who changed what, and location tracking appears in a feature list with nothing said about what it stores or who can read it. 1 3 2 7
The Agency Owner
Automatic capture of every web and desktop app across web, Windows, macOS, iOS and Android is exactly what I want for forty desks: Memory runs in the background, entries can be edited or annotated, AI-populated entries only go out after review, and admins can audit entries. But this is desk capture — a shared kiosk, terminal, badge option and offline handling are not described, and corrections are admin-audited rather than an employee-request, manager-approval workflow. Field and site crews are someone else's problem in this product. 2 1 7 3 6
The Field Supervisor
Automatic background tracking of every web and desktop app, a manual timer, apps for web, Windows, macOS, iOS and Android, and entries that can be edited, deleted, bulk-edited or logged by an admin for contractors — that's a decent spread for desk staff. But for a site crew I found no public information on offline capture, a shared kiosk or terminal, badge readers, or a correction that runs from employee to manager for approval, and location tracking appears only as a word in a feature list with no limits stated. 2 7 6
The Skeptic
Automatic background capture is the whole pitch: the opt-in Memory tracker records page titles and timestamps of active apps across web, Windows, macOS, iOS and Android, with a manual timer, idle detection, bulk editing and admin audit of entries. We found no public information on shared terminals or badges, offline capture, or geofenced check-in with stated limits, so the capture described is for desk work and we found no public information on how it reaches field, site or shift crews. 2 7 3 6
Working-time law & audit record
Show reasoningHide reasoning
How this is scored
Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.
0 — A project or task timer that keeps no attendance record of working time (start, end, breaks).
3 — Start, end and break times recorded per day with a working-time report per employee; ArbZG checks and retention are basic or not described.
5 — Start, end and breaks recorded for the recording duty (BAG 2022 or ArbZG named), automatic break rules, warnings on the daily maximum or the rest period, and overtime balances.
8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, a change log on entries, and an export built for an inspection.
10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.
The Operations Lead
The pages show hour timestamps per entry, overtime and undertime reporting with weekly capacity and individual capacity for part-timers, anomaly flags on excess hours, and a claim of accurate records for audits and regulatory requirements. We found no public information on break and rest-period rules, ArbZG daily limits, retention of the working-time record for the German recording duty, or a change log on entries — the overtime material is framed around capacity and employee support, not statutory limits. 9 9 8 14 8
The Payroll Officer
The pages show per-person hours, overtime and undertime against a weekly capacity, and a general claim of accurate records for audits and regulatory requirements — but no statute is named anywhere. We found no public information on the German recording duty, break rules, rest periods or statutory retention, and entries can simply be edited or deleted with no change log described. 9 9 8 7
The Works Council Advocate
Hour timestamps per entry, overtime and undertime against a weekly capacity set individually for part-timers, ready-made overtime reports and a claim of accurate records for audits and regulatory requirements are documented; we found no public information on break or rest-period rules, a change log on entries, or retention that would satisfy the German recording duty. The terms state all content is immediately deleted upon cancellation and inactive accounts go after 90 days — deletion behaviour a works council would have to negotiate around before signing anything. 4 9 14 9
The Agency Owner
The record is activity-based — the Memory tracker logs timestamps of active apps — with overtime measured against a weekly capacity, overtime reports generated without manual calculation, and a generic claim of accurate records for audits and regulatory requirements. We found no public information naming the German recording duty (BAG 2022, § 3 ArbSchG) or ArbZG, and no break or rest-period rules, statutory retention or change log on entries are described. As the compliance floor for a German office this is thin. 3 9 9 8
The Field Supervisor
Hour timestamps are kept on entries, overtime and undertime are measured against a weekly workspace capacity with individual capacity for part-timers, and the vendor claims accurate records for audits and regulatory requirements. On the captured pages I found no public information on the German recording duty, break or rest-period rules, statutory retention, or a change log on who altered an entry — the overtime view is a capacity tool, not a Working Hours Act model. 9 14 9
The Skeptic
The compliance language is generic — "accurate records for audits and regulatory requirements" — with no statute named, and we found no public information on the BAG recording duty, break rules, rest periods, daily maximum hours or record retention. What exists is a weekly workspace capacity with individual capacity for part-timers, an anomaly flag when someone logs too many hours against it, and ready-made overtime reports — a weekly-hours guardrail, not working-time law modelled. 9 9 8 3
Absence & shift planning
Show reasoningHide reasoning
How this is scored
Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.
0 — Neither absence handling nor shift planning is part of the product.
3 — Vacation requests with approval and an absence calendar, or a basic shift plan; entitlement rules and rostering are basic or not described.
5 — Absence management with entitlement balances, sickness recording and an absence calendar, plus shift or duty planning with templates or employee availability.
8 — Public-holiday calendars per location, pro-rata entitlement and carry-over, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.
10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.
The Operations Lead
Absence is handled by booking hours to non-billable 'Sick Leave', 'Vacation' and 'National Holiday' projects, reportable per user and visible in a weekly company view of who is off, with absence days worked out by dividing logged hours by an average workday such as eight, plus planned time entries for team members. We found no public information on vacation requests with approval, entitlement balances and carry-over, substitution or swap workflows, or shift templates with rest checks — this is a visibility workaround, not a roster. 10 10 11
The Payroll Officer
Absence is modelled as non-billable projects for sick leave, vacation and national holidays, shown in a weekly company view of who is away, and absence days are counted by dividing logged hours by an average workday. We found no public information on entitlement balances, request-and-approval workflows or shift rosters; the planning side is planned-time entries for teams, not a duty roster with coverage checks. 10 10 11
The Works Council Advocate
Absence is booked as hours on non-billable admin projects named "Sick Leave", "Vacation" and "National Holiday", visible in a weekly Company view showing who is off sick, and absence days are computed by dividing logged hours by the average workday such as 8 — a workaround, not an entitlement system. Planned hours can be scheduled for team members; we found no public information on a vacation request and approval workflow, entitlement balances, carry-over or a shift roster. 10 11 10
The Agency Owner
Absence is a do-it-yourself construct: you create non-billable projects named Sick Leave and Vacation, add all users, and compute absence days yourself by dividing logged hours by an average workday. Company view gives a weekly overview of who is away and lets managers plan and log hours for others, which covers the calendar half. Vacation requests with approval, entitlement balances, holiday calendars and shift templates with rest checks are not described, so the leave year and any roster stay outside the product. 10 10 11
The Field Supervisor
Absence is a make-do: you create non-billable projects named Sick Leave, Vacation and National Holiday, add all users to them, and work out absence days by dividing logged hours by your average workday. The Company view does give a weekly picture of who is off sick or on vacation and lets managers plan hours for the team, but I found no public information on vacation request approvals, entitlement balances, holiday calendars or shift templates. 10 10 11
The Skeptic
Absence is a construction project: create non-billable projects called "Sick Leave" and "Vacation", add all users, and to count absence days divide logged hours by an average workday of e.g. 8. Company view gives a weekly overview of who is on vacation or off sick and lets managers plan hours for others, but we found no public information on vacation requests with approval, entitlement balances, holiday calendars, or shift templates and rostering. 10 10 11
Project, cost-centre & billing
Show reasoningHide reasoning
How this is scored
Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.
0 — Attendance only; the product records time without any project, task or cost-centre dimension.
3 — Time booked to projects or clients with a report per project; rates and billable status are basic or not described.
5 — Projects and tasks with a billable flag, hourly rates, reports per project and client, and an export or integration toward invoicing.
8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.
10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.
The Operations Lead
Clients nested to projects with a Tasks add-on, billable and non-billable hours, billable and cost rates, a 'marked as billed' status, budget totals with project health monitoring, time, money, cost and profit per client and project, invoicing by budget or hours worked, and a QuickBooks Online integration take this well past basic project time. We found no public information on rate cards by role, cost centres, or budget warnings described explicitly, so I stop short of the higher band despite the strong reporting. 12 14 13 7 2
The Payroll Officer
Clients, projects and tasks with billable and non-billable hours, billable and cost rates, budgets, a money-cost-profit view per client and project, invoicing by budget or hours, a marked-as-billed status and a QuickBooks integration take this deep into an agency's billing chain. We found no public information on rate cards by role, budget overrun warnings or how rates behave when changed mid-project. 12 12 13 14 2
The Works Council Advocate
Time carries client, project and task dimensions with billable flags, billable and cost rates, budget totals and a Clients & Projects view reporting time, money, cost and profit, all exportable as customizable CSV or multi-sheet XLS with scheduled email delivery. Native invoicing by budget or by hours worked plus a QuickBooks integration takes this past the basic level; we found no public information on rate cards per person or role, or on budget warnings. 13 14 12
The Agency Owner
This is the strong half for an agency: clients with nested projects, a billable flag, billable and cost rates feeding money, cost and profit per client and project, budget total and budget control, billed-status marking, invoicing by budget or by hours worked, and a QuickBooks integration. Rate cards by role or project, cost centres as such, and budget overrun warnings as explicit alerts are not described — though notifications do mention timesheet approvals, and tasks only come as a paid add-on. I could run client reporting on this; I'd have to test whether a rate change mid-project revalues cleanly. 12 14 13 6 6
The Field Supervisor
Time books to clients, nested projects and tasks with flexible tagging, and a Clients & Projects view shows time, money, cost and profit across the portfolio, alongside billable rates, cost rates, budget control, an invoices feature that bills by budget or hours worked, and a QuickBooks integration. That clears the bar for agency billing; I found no public information on rate cards by person or role or cost centres, and the clients-and-projects overview itself offers no export — you build a custom report template for that. 12 13 14 2
The Skeptic
Time carries client, project and task dimensions (task as a "$5 per person" add-on), billable and cost rates, budget totals and a billed-status flag; the Clients & Projects tab reports time, money, cost and profit, and the invoices feature plus the QuickBooks integration reaches toward accounting, invoicing by budget or by hours worked. We found no public information on cost centres, rate cards by role, or how a rate change mid-project is handled. 12 13 14 2
Payroll handoff
Show reasoningHide reasoning
How this is scored
How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.
0 — Payroll is outside the product: it records client or project time only and prepares nothing for payroll.
3 — An export (CSV, Excel or PDF) of hours and absences for the payroll office; named formats and surcharges are basic or not described.
5 — A named payroll integration or a documented export format for at least one major system (e.g. DATEV LODAS/Lohn und Gehalt), covering hours, absences and overtime.
8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.
10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.
The Operations Lead
Exports come as CSV, a multi-sheet XLS or a PDF timesheet carrying logged hours, hour timestamps, billable and non-billable hours, and saved reports can be scheduled by email weekly, bi-weekly, monthly or yearly — a payroll office could work from that. But we found no public information on a named payroll format such as DATEV covering hours, absences and overtime, or on night, Sunday and holiday surcharges; QuickBooks Online is the named integration and it sits on the accounting side. 14 2 13
The Payroll Officer
The recorded month leaves the product as a CSV, a multi-sheet spreadsheet or a PDF timesheet, with scheduled email delivery and hour timestamps among the export columns — a handoff, not a payroll run. We found no public information on a named payroll system, night, Sunday and holiday surcharges, time-account transfer, or any lock step before transmission. 14
The Works Council Advocate
The documented handoff is a generic file: CSV for a single table, multi-sheet XLS for several, or a PDF timesheet, with saved default export settings and scheduled delivery on weekly to yearly cadences. We found no public information naming a payroll system, a DATEV or Lohn und Gehalt format, or surcharge handling for night, Sunday and holiday hours. 14
The Agency Owner
What exists is a report export, and a good one: CSV or multi-sheet XLS plus a PDF timesheet, customisable columns including logged and planned hours, billable hours, timestamps and a user external ID, saved defaults, export history and scheduled email delivery. We found no public information on a named payroll system, a DATEV or Lohn und Gehalt format, or night, Sunday and holiday surcharge handling; the QuickBooks integration sits on the invoicing side. My bookkeeper gets a spreadsheet, not a handoff. 14 13
The Field Supervisor
Exports come as CSV or a multi-sheet XLS with a column picker that includes user and project external IDs, a clean PDF timesheet, and scheduled email delivery on weekly to yearly cadences. That is a file you can hand to the payroll office; I found no public information on a named payroll system or format such as DATEV, surcharge handling for nights, Sundays and holidays, or a lock step before transmission. 14 13
The Skeptic
Exports are CSV, XLS and PDF of logged hours with timestamps, tags, notes and external IDs, schedulable weekly, bi-weekly or monthly by email — material a payroll office can retype. We found no public information on a named payroll system such as DATEV, on night, Sunday or holiday surcharges, or on a lock step before transmission; QuickBooks is presented as an accounting integration. 14 13 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; the subprocessor list is not published in full or includes non-EU providers without a stated safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, the full subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.
The Operations Lead
The contracting entity is Timely AS at Hausmannsgate 16, 0182 Oslo under Norwegian law and Oslo city court jurisdiction, data sits on ISO 27001-certified AWS servers in Europe with EU-based data residency, and a data processing agreement and a list of sub-processors exist as documents. Card payments run through Stripe, and the captured pages do not show the sub-processor locations or a stated safeguard for non-EU processing, so the chain is proven only partway even though an EEA vendor with EU hosting is workable from my seat. 4 5 3
The Payroll Officer
The contracting entity is Timely AS in Oslo under Norwegian law — EEA rather than EU — with hosting stated on Amazon Web Services in EU data centres and a data processing agreement linked, though its full text is not among the captured pages. A sub-processor list is named as a document and Stripe is cited for card processing, but the locations of the rest of the chain are not shown. 4 5 3
The Works Council Advocate
The contracting entity is Timely AS at Hausmannsgate 16, Oslo, under Norwegian law and Oslo city court's exclusive jurisdiction, hosting on ISO 27001-certified AWS servers in Europe with a GDPR data processing agreement and a sub-processor list published as a document whose contents we could not read, while card payments run through Stripe. The privacy terms speak my language — no data sale, consent required before backend engineers access customer data, deletion rights at any time — but the chain is EEA rather than EU and only partly evidenced on the pages we read. 4 5 3 7
The Agency Owner
Timely AS contracts from Oslo under Norwegian law with Oslo city court as venue, data sits on ISO 27001-certified AWS servers in EU-based data centres with EU-based residency stated, and a data processing agreement plus a list of sub-processors exist as documents. Norway is EEA rather than EU, the sub-processor locations are not shown in the captured excerpts — card payments run through Stripe with the detail living in the agreement — and no on-premises or private-cloud option is described. Adequate for me, not sovereign end to end. 4 5 7 3
The Field Supervisor
The contracting entity is Timely AS of Oslo under Norwegian law, hosting is stated as ISO 27001-certified AWS servers in the EU with EU-based data residency, and a data processing agreement is offered alongside a named List of Sub-Processors document — though the contents of that list were not among the pages I read, and card payments run through Stripe. Norway is EEA rather than EU, and I found no public information on an on-premises or private-cloud option, so the chain is proven only partway. 5 4 3 7
The Skeptic
The contracting entity is Timely AS in Oslo under Norwegian law and Oslo courts — EEA rather than EU — and the security page states AWS data centres in the EU region with ISO 27001 certification, alongside a Data Processing Agreement and a "List of Sub-Processors" among the related documents. The sub-processor list's contents are not among the captured pages, so where Stripe processes card payments and under which safeguard remains unshown, and we found no public information on an on-premises or private-cloud option. 5 4 7 3
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price per user or one priced tier; how cost scales with modules, hardware or minimum seats is unclear.
5 — Per-user prices public for the main tiers with the billing period stated and the main inclusions given; some pieces (terminal hardware, planning module, payroll export) may be unpriced.
8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.
The Operations Lead
Starter, Premium and Unlimited are priced per user for both billing periods — $9 billed yearly and $11 monthly, $16 and $20, $22 and $28 — with plan limits, a Tasks add-on at $5 per person, fees stated as exclusive of all taxes, and prices changeable on 30 days notice. The top tier is 'contact sales' and gates features like API access and Azure AD, so a full invoice for every configuration is not computable, and we found no public information on a minimum term. 2 4
The Payroll Officer
Starter, Premium and Unlimited are priced per user for both monthly and yearly billing with project and user limits stated, the tasks add-on carries a price of "$5 per person", and the terms state billing in advance with fees exclusive of taxes. The Unlimited+ tier and Enterprise give no figure in the captured pages, so the full annual invoice is not computable from public pages alone. 2 4
The Works Council Advocate
Three tiers are publicly priced per user per month in USD — Starter $9 billed yearly and $11 monthly, Premium $16 and $20, Unlimited $22 and $28 — with plan limits such as 5 users and 20 projects on Starter and max 50 on Premium, a Tasks add-on at $5 per person, billing in advance monthly or yearly, and fees stated as exclusive of taxes. Enterprise is contact-sales, and we found no public price for the Unlimited+ level or a stated minimum term. 4 2
The Agency Owner
The main tiers are fully public with both billing periods — Starter at $9, Premium at $16 and Unlimited at $22 per user per month billed yearly, with monthly prices, project and user limits, a Tasks add-on at $5 per person, advance billing, fees exclusive of taxes and a 30-day price-change notice. The captured pages give no figure for the Unlimited+ tier and Enterprise is contact sales, so the top of the range is a sales conversation. Good enough to compute a forty-seat annual invoice for the tiers that matter. 2 4 12
The Field Supervisor
Starter, Premium and Unlimited are priced publicly per user on both billing periods — "9", "16" and "22" USD per user per month billed yearly, higher billed monthly — with plan limits spelled out, a Tasks add-on at "5" USD per person, taxes stated as exclusive of all taxes, and a free trial. Unlimited+ and Enterprise are contact-sales, so a bigger crew cannot compute its full annual invoice from public pages alone, and I found no public information on minimum contract terms. 2 4 2
The Skeptic
Three tiers are priced publicly per user in both billing periods — Starter "9", Premium "16" and Unlimited "22" USD per user per month billed yearly — with user and project caps stated, a Tasks add-on at "$5 per person", and terms stating fees are exclusive of taxes and prices change on 30 days' notice. But Unlimited+ appears in a plan list without a captured price, Enterprise is contact sales, minimum term is not described, and the captured pages give different statements on whether API access sits in Starter or Unlimited+. 2 12 4 2
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in NO | 2/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The pages only link to the DPA; its full text is not among the excerpts, so whether a customer can conclude it online is not shown. |
1/1 pts | 5 Report an error |
| Transfer impact assessment |
Not needed, no transfer outside the EU/EEA
unverified
Why unverified?The claim covers AWS-hosted data, while sub-processor locations (e.g. Stripe for card payments) are only detailed in the Data Processing Agreement. |
1/1 pts | 5 Report an error |
Questions about Timely
Is Timely European?
Yes, though not from the EU. whats-best.ai classifies Timely as UK / wider Europe. Its vendor, Memory AS, is incorporated in Norway, per the vendor’s page captured 16 Nov 2026.
Where does Timely store data?
The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention Europe as hosting location, per the vendor’s page captured 15 Sep 2026.
Does Timely have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Timely?
As of 18 Nov 2026, the panel rates TimeTac (3.5/5), clockodo (3/5) and ZEP (3/5) highest among the other 32 Time Tracking & Attendance products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is TimeTac (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Timely alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The pages only link to the DPA; its full text is not among the excerpts, so whether a customer can conclude it online is not shown.
- Weak sourcing — Transfer impact assessment. The claim covers AWS-hosted data, while sub-processor locations (e.g. Stripe for card payments) are only detailed in the Data Processing Agreement.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 42 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 16 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage timelyapp.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 2 Pricing timelyapp.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 3 Privacy policy timelyapp.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Terms of service www.timely.com Checked 16 Nov 2026 Details →
- 5 Security / trust page www.timely.com Checked 16 Nov 2026 Details →
- 6 Capture in the real workplace — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 7 Capture in the real workplace — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 8 Working-time law & audit record — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 9 Working-time law & audit record — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 10 Absence & shift planning — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 11 Absence & shift planning — found from sitemap www.timely.com Checked 16 Nov 2026 Details →
- 12 Project, cost-centre & billing — found from sitemap www.timely.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 13 Project, cost-centre & billing — found from sitemap www.timely.com Checked 16 Nov 2026 Details →
- 14 Payroll handoff — found from sitemap www.timely.com Checked 16 Nov 2026 Details →