Bring up timesheets in a design studio and the room cools. Everyone has worked somewhere that used them as surveillance, and creative people are right to resist being measured by the minute.
But a studio that does not measure time cannot price. It quotes on instinct, discovers the outcome months later, and never learns which instinct was wrong.
The problem is not timesheets. It is what they are used for.
Say what it is for, out loud
If people believe the data feeds appraisals, it will be fiction within a fortnight — round numbers, filled in on Friday, reverse-engineered from what looks reasonable.
Make the purpose explicit and stick to it: timesheets price projects; they do not evaluate people. Then demonstrate it. When a project overruns, the conversation should be about the project — how many revisions, when the approval landed — never about who was slow.
The first time you use time data in a performance conversation, the data dies.
Make logging take ten seconds
Adoption is entirely a function of friction. A designer will not switch app, find a project, find a task, pick a category and write a note.
What works: start a timer when work begins, stop it when it ends, correct it later if needed. Time attaches to the task already open. If someone forgets, fixing yesterday should take one edit, not a form.
If logging time takes longer than a minute a day, you will get compliance instead of data.
Track at the phase level, not the fifteen-minute level
The temptation is to capture everything in fine categories. Resist it. Nobody needs to know whether 40 minutes was drafting or detailing.
Project and phase is enough to answer the questions that matter:
- Which phase consistently overruns?
- Do revisions cost what we assume?
- Which project types are actually profitable?
- Where is senior time going that a junior could do?
Coarser categories get filled in honestly. Fine ones get guessed.
What the data tells you
Once you have a few months, some things become visible that were invisible before.
Revisions cost more than anyone thinks. Studios routinely find the third revision costs 60–70% of the original design phase — the work is redone, and the context-switching back into a closed project is expensive. That single number justifies a revision clause in every contract.
Approval delay is a real cost. Idle time is invisible on a timesheet, but a project sitting for three weeks still consumes rescheduling and re-familiarisation. Pair time data with approval turnaround and the total cost of a slow client becomes arguable — see how to get design approvals signed off faster.
Some project types lose money reliably. Most studios find one segment — often small high-detail residential — where the realised hourly rate is half everything else. That is a pricing decision, and you cannot make it without the number. The arithmetic is in how to price an interior design project in India.
The number to compute
For each finished project: fee ÷ total hours = realised rate.
Compare it across projects. The spread is the finding. Studios usually expect a 20% variance and find 200%.
Then compare it to your true cost per hour — salary loaded with overhead, typically 1.5–1.8× — and you know which projects paid for themselves.
What not to do
- Do not publish individual utilisation league tables
- Do not set a billable-hours target for designers
- Do not backfill six months of history to "get a baseline". Start now
- Do not use it to settle who is working hard. You already know
Used narrowly, for pricing, timesheets are the highest-leverage data a studio can collect. Used broadly, as a management instrument, they cost you good people and give you bad numbers.