Some people fill in a week at a time. Some book as they go. Some would rather press start and forget about it, and some would rather say it out loud. Quantim records all of it against the same jobs and the same rates, so the fee position is right whichever way the time arrives.
Start a free trial Book a demoDaily, weekly, a running timer or your own voice. They are tabs on the same screen, writing to the same week, so nobody has to change how they work and you are not reconciling four different systems afterwards.
One booking at a time, for people who would rather close the day down than reconstruct a week from memory on a Friday afternoon.
A grid of jobs down the side and days across the top. Most people fill it in once, on a Friday or a Monday, and load their usual rows rather than retyping them.
Start a timer against a job and get on with the work. The elapsed time runs on screen, and stopping it writes the booking onto the timesheet.
Say what you did and the booking is drafted for you. For the drive back from site, when typing into a grid is the last thing anybody is going to do.
The strip above the timesheet, which is the part most people look at before they book anything. Pick a numbered point to see what it does.
Four points on this screen.
Time written down days later is time remembered, not recorded, and the half hours are the first thing to go. Set your own numbers.
Assumes 46 working weeks, half an hour per person per week that never reaches an invoice, and twenty minutes per person per week of chasing and correcting.
An illustration from the figures you entered, not a measured result. Your own position depends on how your team works today.
The parts of timesheets that are not about typing hours in.
Each person has an approver, set per person rather than assumed from the team structure, because the person who signs off the time is not always the person who manages the diary.
An approver sees the weeks waiting on them, approves or returns each one with a note, and the person who submitted it sees that note against the timesheet. Approved time is what the fee and invoicing screens use, so nothing reaches a client invoice that somebody has not signed off.
A toggle on the timesheet switches the whole screen between decimal hours and clock time: 1.5 or 01:30, the same booking either way.
Small, and it matters. Fees are calculated in decimals and people think in minutes, and asking everybody to convert in their head is how quarter hours go missing.
Some people will never fill in their own timesheet. Rather than pretend otherwise, you can authorise a named person to book time for them, and that authority is explicit: you choose who may book for whom.
Entries made this way record who entered them as well as whose time they are, so an approver can see at a glance that a week was booked by somebody else.
A repeat booking on the daily screen sets a frequency and an end date, so a standing commitment is entered once. Block booking does the same for a range of days at a time, including annual leave and bank holidays.
Both exist for the same reason: the long stretches where this week really is the same as last week should not be typed in cell by cell.
Recorded time is the input to the rest of the system rather than a return that gets filed. It drives the fee position on each job, what can be invoiced, and the chargeable percentage per person and per team.
Because every entry route writes to the same timesheet, that position is the same whether the hours arrived from a weekly grid, a timer or a voice note.
Nothing here is a separate system. The same job, the same people and the same numbers run through all of it.
A free trial takes a few minutes to set up, and no card. Or let us walk you through it against the way your practice actually works.
Start a free trial Book a demo