Architecture time tracking that shows which projects lose money, whether a fixed fee is holding, and who has capacity. Timers your team will actually keep.
Timesheets your studio will actually keep — because nobody has to fill them in. Hours are captured as a side effect of moving work through the board. No stopwatch to remember, no Friday-afternoon reconstruction, no surveillance.
Time tracking isn't paperwork. It's the only way to answer these before the damage is done.
You quoted the job on an assumption about hours. Without real numbers you find out whether that assumption survived only after the project is closed — too late to price the next one differently.
Most studios have one. It looks fine on the invoice and eats three times the hours anyone planned. It stays invisible until someone compares planned time against what really happened.
Assigning work by who looks free is guesswork. Real tracked hours show who's genuinely at capacity and who has space, before you hand out the next deadline.
Most time tracking was built to prove people are working. It counts keystrokes, grabs screenshots, and turns a design studio into a call centre. Teams resent it, so they fill it in badly at the end of the week — and the data it produces is fiction anyway.
Spreadbox records two things: which task is being worked on, and whether someone is clocked in for the day. That's enough to price a project properly and protect a team from overload. It isn't enough to spy on anyone, which is exactly the point.
Moving a task into In Progress opens a work session; moving it out closes it. Hours are the sum of real elapsed time across every stint — never a number derived from the plan.
Clock in when the day starts, clock out when it ends, with breaks accounted for. Presence is reported separately from task hours, so a full day at the desk never double-counts as billable project work.
Every project carries the hours you planned for it. The timeline shows tracked hours next to that plan, so a job drifting past its fee is visible while there is still time to react.
No. Spreadbox records when a task is being worked on and when someone is clocked in for the day — nothing else. There are no screenshots, no keystroke logging, no idle detection, and no activity scoring. The point is to understand where a project's hours went, not to watch people.
Almost never. Hours are captured as a side effect of moving work: when a task goes to In Progress the clock starts, and when it leaves that state the clock stops. The timesheet assembles itself from what already happened, so there is no Friday-afternoon reconstruction of the week.
Generic tools track hours against a flat list of clients or tags. Architecture work runs in phases with fees attached, so hours only mean something when they sit against a phase, a deliverable, and a project budget. Spreadbox tracks time inside the project structure the studio already uses.
Yes. A principal or studio manager can see hours across the team, per project and per person, and compare them against what was planned. Finance figures like cost per hour are kept behind a separate permission, so hours can be shared widely without exposing salaries.
There is nothing separate to remember — the timer follows the task status, which people are already changing to keep the board honest. There is also a day clock-in and clock-out for overall presence, and entries can be corrected after the fact.
Yes. Every feature is included during the beta, with unlimited projects and team members and no credit card required.
Longer reads on getting hours right in an architecture studio.
Find out where the hours actually go. Free during beta — unlimited projects, unlimited team members, every feature included.