A Ticket Has a Department and No Cost
A ticket knows which department raised it and, to the minute, how long it waited. It holds no hours, no rate and no cost, and nothing in the product references a ticket except its own comments. Internal service work is the one kind of work here that is measured entirely in time and not at all in money.
Ask what your IT support costs the finance department and you are asking a question about two records that share no field.
The service desk in this product is properly built on the dimension it cares about. A ticket carries the department it belongs to, the category that routed it, the requester, the assignee, a first-response clock and a resolution clock, a pause, two breach markers, a satisfaction rating and a signature at resolution. Everything you need to run a desk.
It carries no hours. No rate. No cost. And a search across the whole schema for anything pointing at a ticket returns exactly one table: the ticket's own comments.
Effort is costed, but not here
The product does cost effort. Time entries record hours against a task, with a cost rate and a bill rate on each entry, and they roll up into project profitability.
A task, though, carries no department — it inherits one from its project, if it has a project. So the record that knows the department has no hours, and the record that knows the hours has no department.
Two records, one missing column each
| Record | Department | Hours | A rate |
|---|---|---|---|
| A ticket | Yes | No | No |
| A time entry | No | Yes | Yes |
| A task | Partly — configurable by you | Yes | Partly — configurable by you |
Built and maintained Configurable by you, not maintained by us Not built
A task shows partial on both counts because it borrows them: a department through its project, a rate through the entries logged against it. Nothing links a task to a ticket, so the borrowing cannot be arranged after the fact.
The desk measures how long somebody waited, precisely. Nothing measures how long anybody spent.
What you can and cannot answer today
| The question | Answerable? |
|---|---|
| How many tickets did Facilities raise last quarter? | Yes — the department is on every ticket |
| Which category generates the most work? | Yes |
| Did we meet our response target for that department? | Yes, to the minute, with pauses excluded |
| Which department waits longest for a resolution? | Yes |
| How many hours did we spend on Facilities? | No — a ticket holds no hours |
| What did that support cost us? | No |
| Should we charge it back to the department? | No — there is nothing to charge |
The first four are the questions a service desk exists to answer, and they are answered well. The last three are the questions a finance director asks about a service desk, and they need a dimension the ticket has not got.
The workaround, which is one habit
The same technique that fixes departmental expense attribution fixes this, which is a good sign it is the right technique rather than a trick.
-
A standing project per department
Permanent, named for the department, never completed. It exists to be selectable.
-
A task on it for substantial service work
Not for a password reset. For the half-day at a branch, the migration, the recurring facilities job — the work that is worth knowing the cost of.
-
Log the hours against the task
With a cost rate. Now the effort is costed and attributed to the department through the project, and it appears in the project reporting like any other work.
-
Keep the ticket as the ticket
It still routes, still runs its clocks, still gets signed off. The task is a costing shadow for the small proportion of tickets that justify one, not a duplicate of the queue.
Do not shadow every ticket
A task per ticket doubles the desk's administration and will be abandoned within a month. The whole value is in the ten per cent of tickets that consume real time, and picking those ten per cent is a judgement a supervisor makes, not a rule a system enforces.
Three fields and a report
This one is unusually contained, because the costing machinery already exists and is already good. What is absent is a route from a ticket into it.
Time logged on a ticket
Hours against a ticket, at the assignee's cost rate, using the same shape as the existing time entries. One table, one form.
A ticket linked to a task or a project
The cheaper half: let a ticket reference the work it belongs to, so the hours can be logged where they already can be and still find their way back.
Cost per department per period
The report that makes the other two worth having, and the one that turns an internal desk into something a department can be asked to fund.
We publish scope, not dates.
Scope service-desk costingThree questions for any service desk you are buying
Can I log time on a ticket?
A good answer sounds like
Yes, and here is the field.
What ours actually is
No. Ask this early — many desks answer yes for a timer that is not costed, which is a different thing.
Is that time costed at a rate?
A good answer sounds like
A cost rate and a bill rate, named separately.
What ours actually is
Both exist in the product, on time entries against a task, and a ticket cannot reach them.
Show me cost per department for last quarter.
A good answer sounds like
One report.
What ours actually is
Ticket counts and response performance per department, and no cost figure. Ask for the report rather than the capability.
Our take
This is a boundary rather than a defect, and it is worth knowing which. A service desk built to answer "how long did they wait" answers it very well here, including the parts that are hard — pausing a clock, marking a breach, capturing a signature at resolution. A service desk that also answers "what did it cost" is a different product, and ours is not that today. If chargeback or cost-per-department is a requirement you will be held to, use the standing project and the selective task from the day you start, because retrofitting hours nobody recorded is not possible at any price.
What AWRA OpsHub does today
- A department on every ticket, and a category that carries a default department and a default assignee so routing is a maintained rule rather than a habit.
- First-response and resolution targets per category, with a pause, two breach markers and notification.
- A satisfaction rating and a resolution signature on the ticket.
- Hours costed at both a cost rate and a bill rate — on time entries logged against a task.
- Project profitability built from those entries, including a billable flag and an invoice reference per entry.
- Ticket counts, ageing and response performance grouped by department.
More we can add to your workspace
- Hours logged directly on a ticket, at the assignee's cost rate, using the costing shape the timesheet already has.
- A ticket linked to the task or project it belongs to, so existing time entries can find their way back to the request that caused them.
- Cost per department per period from the service desk, which is the report that makes internal chargeback possible.
- An effort estimate on a ticket, so a queue can be read as a workload rather than as a count.
- A department on a task, independent of whether the task belongs to a project.
Where we point you to a specialist
- We would not add a running timer that produces hours nobody has confirmed. An unreviewed timer is worse than no figure, because it gets charged to a department and then defended.
- Whether an internal service desk should be charged back to the departments it serves is a management decision with real consequences for behaviour, and we point you at your own finance leadership rather than shipping a default. Our part is to make the figure available if you decide you want it.
- A satisfaction rating from an external requester who has no account is not something we can produce today, and we would rather say so than publish an average with no denominator.
Time on a ticket plus the cost-per-department report is a single, well-bounded piece of work, and the costing machinery it needs already exists. If chargeback is on your roadmap, this is the one to scope.
Decide now whether you will ever need the cost
It is the one question in this article with a deadline, because hours not recorded in the moment cannot be recovered later. If the answer is yes, set up the standing projects this week. If it is no, run the desk on its clocks and enjoy how good they are.
Talk it throughFrequently asked questions
Can I log time against a ticket at all?
Not on the ticket. Time entries in this product attach to a task, carry a cost rate and a bill rate, and roll into project reporting — and nothing links a ticket to a task, so the hours cannot be attached after the event either. The workaround is to raise a task for the service work that is worth costing and log the hours there.
Why does the ticket have a department but no cost dimension?
Because a department answers the question a desk is built for — which queue, whose target, who is waiting — and cost was the projects module's question. Each module carries the dimension it needed. The two only have to meet when somebody asks what the desk costs a department, which is a finance question arriving at a service-desk record.
Is the response-time measurement affected by any of this?
No, and it is worth saying plainly because the two get confused. First-response and resolution clocks, the pause, the breach markers and the per-category targets are all real and all unaffected. What is absent is time spent, not time elapsed.
Could I approximate the cost from ticket counts?
You can, and for many organisations it is enough: take the desk's total monthly cost, divide by tickets closed, and apportion by each department's share. It is defensible as a management figure and indefensible as a chargeback, because a password reset and a half-day at a branch count the same. If the number will be argued over, record the hours instead.
Does an integrated suite help here at all?
Partly, and it is worth being precise about how. The advantage is that the costing machinery — rates, time entries, project attribution — already exists a module away, so the work needed is a link rather than a new subsystem. The disadvantage is that "it is all one system" is easy to hear as "the ticket already knows what it cost". Ask for the report, not the architecture.
What about a department that has employees but no logins — does it still route tickets?
Yes, and it is a common shape: a ward, a site, a programme team. Which is worth knowing alongside one other thing about such departments — the delete check does not cover ticket routing, so removing a department that a category routes to empties that routing quietly. See A Department Is a Name and a Description.
