Categories, work types, and departments

Each event gets two orthogonal classifications plus an optional department attribution. The starting values are below; admins can customize them per-company at /admin/taxonomy (sidebar: Categories & depts).

Editing the lists

• Add — type a new value, click Add. Available immediately in every dropdown.
• Deactivate — hides from new entries; existing events keep showing it (no rewrite).
• Reactivate — re-enables a previously deactivated value.

To rename a value, add the new one and deactivate the old. Bulk-correct existing events from the team admin page if you need historical consistency. Changes affect My Day, /events/mine, reports, manager review, classification rules, and the AI auto-classifier — all read your current company list.

Category — what kind of work was it?

Fixed enum:

Limiting a category to some departments

Some categories only make sense for one team, such as solver_development for engineering or Social Media for marketing. On /admin/taxonomy, click all departments under a category and tick the departments that should see it. Everyone else stops being offered it in My Day and on their events page, and the AI classifier stops putting their activity into it. Tick nothing to offer it to everyone again.

It's matched against each person's Department on their profile. Events that already carry the category keep it, and admins and reports still see every category.

Work type — how does this affect billing?

Starting values:

"Counts as" — the name is yours, the arithmetic is fixed

Work types are free-text labels you can rename or extend, so the reports can't rely on the name to know what to add up. Each work type therefore carries a counts as class — set from the dropdown beside it on /admin/taxonomy — and that class is what the reports, utilization and capacity actually total:

If you add a work type such as client-support or retainer, set its class to billable or it will be treated as internal by default. Existing work types were classified automatically on upgrade (billable → billable, off → off, everything else → internal), which matches how the reports already treated them.

How they combine

A single event has one category and one work type. Examples:

• "Building a client slide deck" → category=design, work_type=billable
• "Team standup" → category=meeting, work_type=internal
• "Attending a conference" → category=training, work_type=training
• "Doctor's appointment" → category=off_time, work_type=off

Who decides these values

1. Admin rules (instant, deterministic) — patterns like "app=Outlook.exe → category=communication"
2. Past event lookup — if someone corrected chrome.exe / Gmail before, new events inherit
3. AI classification — Claude Haiku classifies when nothing else matches
4. You correcting on My events — always wins; propagates forward

Adding your own dimensions

OtiumWork's categories are fixed (changing the enum requires a schema change). For project-specific or team-specific labels that don't fit the enum, use tags — see Tags.