Last updated 2026-10-23
Company dashboards
Company in the left menu has one dashboard per department. Each shows a few headline numbers, red/amber/green flags and links into the tools that already exist. Built so far: Overview, Consulting, Development, Hiring, IT, Legal, Finance. Sales, Marketing and Tech Support follow once their data sources are connected.
Who sees what
- Admins and people with finance access see every dashboard.
- Anyone else sees the dashboards their department or they personally have been given. Admins set this at the bottom of each dashboard ("Who can see this dashboard").
- Money (budget $, invoiced, margin) shows to admins and finance only, on every dashboard.
Consulting
Every paid customer project (linked to a customer or billable by default) that is active or planned, worst first.
| Column | Meaning |
|---|---|
| Hours used / budget | All hours logged on the project by everyone, against its hour budget |
| % used vs % done | Bar = share of the hour budget used; line = the project manager's own % done |
| Forecast | Hours used ÷ % done: where the project ends up if it continues like this |
| Last 4 wks / Next 4 wks | Hours logged in the last four weeks; hours already allocated for the next four (from Capacity) |
| Next milestone | The next open ◆ milestone in the project's Gantt |
Flags: 🔴 over budget, forecast more than 10% over budget, or past its end date and still being worked on. 🟠 hours used running 20+ points ahead of % done, 85%+ of the budget used, or tasks overdue. 🟢 otherwise.
Missing data lists projects with no budget, no project manager, no customer, no or past end date, or no % done. The flags are only as good as this, so it's the first thing to fix.
Overview
One tile per dashboard you can open, with its headline numbers and anything red or amber first. A grey tile means that department has nothing recorded yet; the note under it says what's missing. Anyone who can open at least one department dashboard can open the Overview.
Development
Features and bug fixes this month (from the code history, the same numbers as the roadmap's leaderboard), open bug reports and feature requests from Feedback, the requests pipeline (new → triaged → being worked on → fixed on staging → developer-approved → approved for prod), the oldest open requests, and desktop client releases.
Hiring
Open positions with applicants, new in the last 7 days, candidates past "applied", offers, how long each has been open and its target fill date. Flags positions with no applicants or no movement in 30 days, and lists hiring requests waiting for approval.
IT
Open helpdesk tickets, most urgent first, with who has them and how old they are; past-due and unassigned counts, who has what, tickets by category, and the average time to resolve.
Legal
Contracts expiring in the next 90 days (and whether they auto-renew), compliance items overdue or due in 30 days, open data-subject requests, open disputes, documents out for signature and insurance policies expiring. Everything comes from the Legal pages, so an empty dashboard means nothing has been recorded there yet.
Finance
Bookings this year (from Finance → Sales), invoiced, receivables open and overdue, expenses waiting for a decision, billable hours and the billable share of hours. Money figures show to admins and finance only. The missing-data list also catches internal projects (no customer) with hours marked billable.
For project managers
On their own project page, project managers (and managers and admins) can:
- set % done: an honest estimate of how much of the work is finished. It's shown next to the share of hours used, so an overrun shows before it happens;
- open 👥 Who's available? to see everyone's free hours, week by week, sorted by who's most free, filter by department, and add people to the project with their allocated hours in one click.
Issues & changes
Every project page has an Issues & changes log that the project manager keeps as things come up, so the numbers come with a reason:
| Type | For |
|---|---|
| Change order | Scope the client asked to add: hours and $ impact; requested → quoted → approved / rejected |
| Billing dispute | An invoice or hours the client contests: amount, invoice reference |
| Waiting on client | Work blocked on the client, and since when |
| Risk | What might go wrong, and the plan |
| Scope / quality issue | Rework or quality problems: hours lost, who pays |
- Anyone on the project's team can log one and add updates; the project manager (and managers, admins) change the status.
- A change order can get its own task, so the work is logged against it. Hours logged there before the client approves are flagged as unbillable risk and turn the project red.
- Approving a change order needs a reference (PO number, email, who and when) and adds its hours and $ to the project's budget once, recorded in its history.
- On Consulting: open issues per project, open change orders, hours on unapproved changes, and (for admins and finance) $ in billing disputes. Open billing disputes and unapproved change work turn a project red; waiting on the client and open risks turn it amber.
- Change orders are not emailed to clients from Otium (yet).
Where the planning pages went
- Capacity and Scenario are under Projects in the menu: planning tools for managers and admins.
- Utilization and Profitability are for admins and finance: open them from Company → Consulting and from Finance.
See something wrong or outdated in this article? Report it →