Work structure
A structure that holds when projects multiply
Client, project, sub-project, activity: four levels are enough to describe the work of almost any service company, and each one is a level where you can read hours, costs and margin.
You decide the level of detail
Companies working per job stop at the project. Companies invoicing by phase use sub-projects. Companies that must justify every line to the client go all the way down to the activity. Klokka imposes no depth: use the levels you need and leave the others empty, without the reports losing coherence.
How it works
-
Start from the client
The client registry is shared with the Kamzan ecosystem, Kore CRM included: whoever is already a client in the CRM is already available in Klokka, with no double entry and no two versions of the same name.
-
Open the project, or apply a template
If the kind of work repeats — an audit, an installation, a campaign — you save the structure once as a template and apply it to the next client with all sub-projects already inside.
-
Close it when it is done
A closed project disappears from the logging menus but stays whole in reports and history. If the client comes back you reopen it: no need to recreate it or lose the comparison with previous hours.
The right structure is the one that still holds once the projects have become a hundred.
What you can do
-
Four real levels
Client → project → sub-project → activity. Every time entry hooks onto the right level and totals roll up the hierarchy on their own.
-
Structure templates
A project–sub-projects structure saved once and applied to as many clients as you like: recurring jobs are born organised the same way.
-
Rates per client and project
Set the rate where it makes sense — on the client, on the single project — and apply it to already logged hours too when an agreement changes mid-course.
-
Activity catalogue
Recurring activities — site visit, development, training, travel — live in a shared catalogue, so everyone picks the same item and reports stay comparable.
-
Before deleting, you know what you touch
Every client, project and activity shows how many entries hang off it: you delete knowing what you are losing, not by surprise.
Frequently asked questions
Are the clients the same as in the CRM?
Yes: the client registry is shared across the Kamzan ecosystem, so Kore CRM and Klokka work on the same list. Those using Klokka alone can still manage clients directly from here.
Do I have to use all four levels?
No. You can stop at the project and skip sub-projects and activities. Unused levels do not appear in reports and do not complicate time entry.
What happens to the hours if I close a project?
They all stay. Closing removes the project from the logging menus so new hours do not land there by mistake, but history, reports and margin keep including it.
The other Klokka features
Try Klokka in your company
Request a demo: we’ll show you how Klokka simplifies time tracking and hour accounting.
Alex