Staff Management and Rates - Quantim

Staff Management and Rates

The record that makes every other number work

A timesheet is just hours until the system knows what that person costs, what grade they are, how much of their week should be chargeable and who signs their time off. All of that lives on one record, and most of the figures elsewhere in Quantim are derived from it. It is not an HR system and does not replace one.

Start a free trial Book a demo
The screens

People, grades, rates and who approves what

The directory, the grade structure behind it, the rate history underneath that, and the approval routes that depend on all three.

The staff directory

Everybody, with the four things you look people up for: what grade they are, what access they have, which office, and what proportion of their week is supposed to be chargeable.

  • Target utilisation per person, not one figure for the practice
  • Start and leaving dates, with archived staff kept separately
  • The record behind each one: permissions, holiday allowance, rate history
  • A staff hours audit trail and a history of what changed

Grades and grade groups

Grades are the vocabulary the rest of the system bills and reports in. Grouping them means a report can say senior staff without listing six titles.

  • Your own grades, with a count of who is currently on each
  • Grade groups, so reporting works a level up from job titles
  • Assign a grade to staff in bulk rather than one record at a time
  • Archive a grade you no longer use without losing its history

Cost rates, with their history

A rate is not a single number, it is a number with a date. Old work stays costed at the rate that applied when it was done, which is the only way a job from two years ago still reports correctly.

  • Cost rate per person, with an effective date
  • Separate additional hours rate, and one for non working days
  • Every amendment records who made it
  • Assign a new rate; the previous one stays on the record

Three approvers, not one

Timesheets, expenses and holiday each have their own approver per person. They are often the same individual and they do not have to be.

  • A separate approver list for time, for expenses and for leave
  • Assign one approver across a selection of staff in one action
  • Anybody without an approver is visible as exactly that
  • The approval screens elsewhere read from these three lists
A closer look

What one record decides

Four fields on a staff record that quietly determine figures all over the system. Pick a numbered point.

Four points on this screen.

    Work it out

    What an hour of someone's time really costs

    The number every fee is built on, and the one most practices guess at. Set your own figures.

    Assumes 1,725 paid hours a year, which is 46 weeks of 37.5 after holiday and bank holidays. Overhead is excluded: add yours on top.

    Cost of a chargeable hour, before overhead

    Chargeable hours a year at that utilisation

    What the same person costs per hour at 50% utilisation

    An illustration from the figures you entered, not a measured result. The cost rate on the staff record is where your real figure belongs.

    The rest of the module

    Access, privacy and what else the record holds

    The parts of a staff record that are not about rates and time.

    Each person has an access level and a permissions tab behind it. A job runner, a director and an administrator are not looking at the same system and should not be.

    Login history is kept separately, which is the part that matters when somebody asks who looked at what.

    A separate screen controls which staff a given person is authorised to see named on reports. It exists because a report that is useful to a director can be uncomfortable in the wrong hands.

    An office manager may need the hours without the names attached, and this is how that distinction is made rather than by trusting everybody not to run the wrong report.

    Which page they land on, whether their timesheet opens daily or weekly, whether they get an email when something needs approving, how dense they want the grid.

    None of it changes the data and all of it changes whether somebody uses the system willingly. The notification settings in particular decide whether approvals happen the same day or the following week.

    Somebody who leaves is archived, not removed. Their time stays on the jobs they worked on, their costs stay in the history, and the reports from three years ago still add up.

    Archived staff are listed on their own tab, so the directory stays the current team while the record survives.

    Emergency contacts, holiday allowance, length of employment, a staff hours audit trail and a history of changes. Reference details held against the person who is already in the system.

    Quantim is not HR software and does not try to be. There is no payroll here, no recruitment, no appraisals, no absence policy. If you run an HR system, keep running it. This record exists so that time, cost, utilisation and approvals are right.

    See it with your own team in 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 is actually structured.

    Start a free trial Book a demo