Taskomat overview: structure and key concepts

🔹 At a glance

Taskomat helps you connect time and value through four core entities:

• Client → who you work for
• Project → a container that groups related work
• Work Unit → where budget and time are tracked together
• Task → the timed activity that consumes the Work Unit’s budget

✅ Why this matters

• You always know how much time you can still spend to stay within budget
• You can read KPIs at every level: client, project, work unit, task
• You avoid orphan data and keep analytics clean and aggregated

🧱 Core entities

Client

The top-level entity. All projects, work units and tasks belong to a Client, enabling aggregated analysis across everything you do for them.

Project

A simple container that groups Work Units. Projects don’t enforce a budget or deadline by themselves; they help you keep related Work Units together.

Work Unit (the core)

The Work Unit tracks budget and derives the time limit from your hourly rate.

You set the price sold to the client → Taskomat converts it into available hours.

Task

A timed activity that consumes a Work Unit’s budget.

Tasks can have an hourly estimate or none, and must be linked to a Work Unit to be counted correctly.

🔄 Typical flow

1. Create a Client
2. Create a Project for that client
3. Add one or more Work Units (set price and hourly reference)
4. Create Tasks and link them to the right Work Unit
5. Plan tasks in the Planner and track time while working

Note: you can create quick tasks on Dashboard/Planner and link them later to a Work Unit

🚫 Avoid orphan data

• You cannot create a Work Unit without a Project/Client (by design)
• You can create tasks on the fly, but remember to link them to the right Work Unit to keep KPIs accurate

🔗 Related

• Work Unit: what it is and how it works
• Plan tasks with Planner in 3 steps
• Track time on Work Units (manual and timer)
• Taskomat KPIs explained: Effectiveness, Efficiency, Punctuality

.

Updated on: 28/08/2025