T.A.L.Q.T.
  • overview
  • features
  • specs
  • the markdown
  • manual
  • guides
  • blog
  • deutsch
download

blog 04 · small teams

time tracking tips for small teams.

Four people, four ways of tracking time, one owner reconstructing the month from memory. There is a cheaper way, and it needs almost no software.

published 8 November 2026 · felix barth

A team of four. One person works from home two days a week, one is on site with customers most of the day, the owner does a bit of everything, and the fourth is a part-timer on 20 hours. Each of them tracks time differently, if at all. At the end of the month the owner spends an evening reconstructing what happened from calendar entries, chat messages and memory.

That evening is the cost of having no method. This post is about getting rid of it with the least possible machinery. It is written for teams of 2 to 10, and it is honest about where a single-user tool like talqt fits and where it does not.

01 · one method for everyone

The single most useful decision is that everyone records time the same way. Not the same tool necessarily, but the same unit, the same rules and the same output. If one person logs projects to the quarter hour and another writes "worked, roughly 8", the records cannot be compared or added up, and you are back to the reconstruction evening.

Write down four things and pin them somewhere:

  • What counts as the start of the working day: first task, arriving at the site, first email.
  • How breaks are recorded. Clock times, not a flat deduction. Why that matters.
  • What granularity tasks are logged at, if tasks are logged at all. Per customer, per project or only start and end.
  • What the day's output looks like and where it goes.

If you employ people in Germany, the output also has to satisfy the recording duty: start, end and duration of each day, kept for two years. The legal post has the details. Any method that meets the four points above already does that.

02 · the daily close

Monthly reconstruction fails because memory does not keep clock times for 30 days. Daily closing works because it only asks about today. Every person ends their working day by closing their record: a last look at start, end, breaks and total, a correction if something is off, then done. Two minutes.

Shops have done this for a century with the till. At closing time someone counts the cash, compares it with the register tape, writes the difference in the book and locks up. Nobody at a bakery would propose counting the till once a month instead. The count takes five minutes and the book is boring.

Make the daily close a visible habit rather than a rule in a document. The owner does it too, ideally first. In a small team people copy what the owner does, not what the handbook says.

03 · plain text files, one per person and day

If you are already rolling your eyes at the word system, this section is for you. The cheapest shared format for a small team is a folder of plain text files. One file per person per day, named so it sorts itself: 2026-11-08-anna.md, or, if an app produces it, talqt-2026-11-08.md inside a folder named after the person.

Why plain text and not a shared spreadsheet or a team SaaS:

  • Everyone can read and write it with whatever they already have. No seat to pay for and no login.
  • A file written on the day and never touched again is better evidence than a spreadsheet cell that could have been edited at any time.
  • It survives the tool. If the app disappears, the files are still there.
  • Adding up is a one-line script or an afternoon with any spreadsheet, once a month, by one person.

The weak spot is real: nobody gets a live dashboard. For 2 to 10 people that is usually fine, because the owner can open five files in a minute. For 30 people it is not, and that is when a team tool earns its monthly fee. What those tools do better, and what they cost you in return.

talqt produces exactly this kind of file. It is a voice time tracker for iPhone: hold a button, say the task, release, and the timer runs until the next entry or a break. At checkout it writes one markdown file for the day into the user's own iCloud Drive, with an overview, a timeline table and a task log. It is strictly single-user. There is no team account, no admin view, no approval flow, and no way for an owner to see a colleague's day except by that colleague sharing the folder or sending the file. In a team of three where everyone has an iPhone and people trust each other, that is a workable system. In a team where the owner needs to see hours without asking, it is not, and it is better to say so here than to have you find out after buying four copies.

04 · the weekly review

Once a week, 15 minutes, the owner or whoever handles payroll opens last week's files and looks for four things:

  1. Missing days. A gap on Wednesday is easy to fix on Monday and impossible in six weeks.
  2. Days over six hours without a break. § 4 ArbZG applies even when everyone was busy.
  3. Days over the target. Overtime that is seen weekly stays small.
  4. Anything that does not match what you know happened. A 12-hour day on a public holiday, a site visit with no travel time.

Then the files go into the month's folder and stay there for at least two years. That is the whole retention policy.

The weekly review is also where you notice that the method is wrong, as opposed to the record. If three people keep forgetting to close their day, the daily close is too hard. Shorten it. If breaks are always exactly 30 minutes, nobody is recording them. They are typing the rule.

05 · what not to do

  • Do not start with software. Start with the four written rules and a folder. Add software where a rule keeps failing.
  • Do not deduct breaks automatically.
  • Do not let the records live only on one person's laptop.
  • Do not fill in weeks after the fact and call them records. They are estimates, and in a dispute they will be treated as such.
  • Do not buy a tool for 10 people when you have 4. The seats you do not use still cost money every month, and the data sits on someone else's server.

If you are a freelancer reading this for your own two-person setup with a subcontractor: the same four rules apply, and the legal part mostly does not. The small business page goes into that case.

06 · who talqt is for, and who it is not for

talqt is for an individual who wants their own working day recorded by voice and written as a plain-text file they own. iPhone only, iOS 17 or later, one-time purchase, no account, no subscription. In a small team it can be each person's recording tool, with the owner collecting the daily files. It is not a team product. There is no dashboard, no admin, no approvals, no invoicing, no Android and no web app. If you need to manage a team's time rather than record your own, pick a team tool and keep the habits from this post.

talqt on the App Store

faq

What is the simplest time tracking setup for a team of five?

Four written rules (start of day, breaks, task granularity, output), a daily close by each person, one plain text file per person and day in a shared folder, and a 15-minute weekly review by the owner.

Do small teams in Germany have to track working time?

Yes, if they employ people. Since BAG 1 ABR 22/21 (13 September 2022) employers must ensure start, end and duration of daily working time are recorded. The form is open and recording can be delegated to employees. Status: November 2026.

Can a team use talqt?

Each person can use it to record their own day. talqt is single-user: no team dashboard, no admin, no approvals. The owner only sees a colleague's hours if that colleague shares the folder or sends the daily file.

When does a small team need a real team tool?

When the owner needs to see hours without asking, when several people bill many projects to many clients, or when the team grows past roughly ten people. Then the monthly fee buys something the folder cannot do.

related reading

  • time tracking for small business ownersWhat German law asks of small business owners who employ people, how to track your own hours honestly, and where a single-user voice tracker fits.
  • why a markdown time log beats an exportWhy one markdown file per working day is a better record than a database with an export: ownership, search, AI, longevity. And where it falls short.
  • talqt vs. subscription time trackersTeam trackers bill per user per month and keep your data on their servers. talqt is a one-time-purchase iPhone app for one person. Where each side wins.
  • legally safe time tracking in germanyWhat the ECJ, BAG, ArbZG and MiLoG require from employers in Germany, what a record must contain, and how a small company complies with simple means.

→ in this section: blog

talqt

talk assisted quick tracking.
voice time tracker for iphone.
made in germany.

links

  • overview
  • use cases
  • compare
  • blog
  • manual
  • privacy
  • contact
  • app store

edition

iphone · v1.9
build · 2026.10
© talqt