Skip ahead to the main page
Partner Huddle
Pages

Hourly rate levels: 5 settings before billing time

Partner Huddle Editorial Team · Published · 11 min read

Why one rate is not enough

The five hourly rate levels are workspace, project, member, task, and project member.

Many small firms start with a single hourly figure. A partner picks a number that feels right for the firm's work, enters it in the time tracker, and moves on. That works for a while. It stops working when a new staff member joins, when a long-time client asks for a lower rate on one engagement, or when a specialist spends an afternoon on work that deserves a much higher figure.

A single rate forces the same trade-off every time. You either undercharge for specialized work or overcharge for routine work, and the routine work is where clients notice. A single number also hides what each engagement is actually worth. When a partner asks why one project earned less than another, nobody can answer without digging through spreadsheets.

Rate levels solve this by giving the time tracker a clear order for choosing a rate. Instead of one number, you set a small set of numbers, each covering a different scope. In the examples, a project rate overrides a member rate, and a task rate applies to other people's time; the levels do not nest by scope. Clockify, a time-tracking tool, describes its own setup this way: its help page on hourly rates says it "offers 5 levels of hourly rates to give you maximum flexibility." The software is only one example. The idea behind the levels applies to any firm that bills by the hour, whatever system it uses.

This post covers each level and its scope. They are not benchmarks for your firm, and this post does not suggest what your rates should be. Set your own numbers based on your costs, your market, and your staff.

Level 1: the workspace rate

The workspace rate is the broadest setting. It covers any time that has no applicable override attached to it. Think of it as the default your firm falls back to when nobody has made a specific decision. The Clockify example describes a web development agency that has "set their Workspace billable rate at $100/hour."

The same help page shows what happens to time with no formal home. When a new junior developer logs time on standard, undefined internal client work, or when the team takes on a basic unplanned request that doesn't have a formalized contract yet, that time is "automatically billed at $100/hour." In other words, the workspace rate is not only a default for paperwork. It also governs the work nobody planned for.

That is why the workspace rate deserves careful thought. For a small accounting firm, unplanned work is often a quick question from a client, a one-off document request, a short call that turns into a review, or a request that arrives by email on a Friday afternoon. These tasks are easy to undercount and easy to forget. If the default is far below your normal rates, staff will log routine follow-up to it, and the firm will quietly give away its time. If the default is well above what clients expect, the first bill will cause friction. Neither outcome is good, so set the figure on purpose.

Write the workspace rate down in your firm's policy document, not just in the software. Staff should be able to explain, in one sentence, what the default covers. If they cannot, the policy is not finished.

Level 2: the project rate

A project rate applies to an engagement with an agreed hourly price. The Clockify example shows how this works: "The project manager sets the Project rate for City Rescue Mission Redesign to $75/hour."

The project rate can override a person's member rate. In the same example, Sarah has a member rate of $150/hour. The help page is explicit about what happens when she logs time to the project: "Even if Sarah (whose Member rate is $150/hour) logs time on this project, her time will be billed at the negotiated $75/hour rate."

This matters for small firms because negotiated rates are often where billing goes wrong. A partner agrees to a lower figure with a long-standing client on a specific engagement. The staff accountant who does the work logs time in the usual way, and the invoice goes out at the standard rate. The client is surprised, and the firm has to correct the bill or lose some trust.

A few habits make project rates reliable:

  • Set the project rate when the engagement is agreed, not when the first invoice is drafted.
  • Use a project name that the whole team recognizes, and make it easy to find in the time tracker.
  • Keep a record of where the rate came from, such as the signed proposal or the email in which the client agreed to it.
  • Review the rate when the scope changes. A larger engagement may need a new figure, and an unchanged project rate can carry an old price into new work.

Level 3: the member rate

A member rate is tied to a person. It applies to that person's time across the firm's work, unless another rate overrides it. The Clockify example gives Sarah, a designer, a member rate of $150/hour.

Member rates are the level partners are most reluctant to set. They touch on pay, seniority, and how the firm values each person's work, so they tend to get left alone. But leaving them undefined does not remove the decision. It just means the time tracker uses a generic figure, or each person sets their own, or the operations lead guesses. None of those is a good way to price work.

Decide a member rate for every person who logs billable time, including partners and staff who only work on a few engagements. Put the rates in a single list that the partner and operations lead can both see. Review the list on a set schedule, such as once a year or whenever someone changes role. The goal is not to make rates permanent. The goal is that every change is a decision someone made on purpose, not a side effect of how an entry happened to be set up in the software.

Member rates also make it easier to talk about efficiency. If a senior person's rate is high and that person spends most of the week on routine review, the firm may be assigning work a lower-rate person could handle. Member rates give you a number to compare against the actual hours, so the question becomes concrete rather than a matter of impression.

Level 4: the task rate

It is useful when a particular service needs more skill or carries more risk than the usual work on an engagement, and you want the bill to reflect that. The Clockify example is a project manager who "creates a Task called 'Custom AI Model Training' and sets the Task rate to $200/hour."

The example also shows the most important detail about task rates: they can pull other people's time upward. The help page says that if "a standard developer or Sarah the designer logs time to this specific task to help prepare the UI or format the data, their time is elevated and billed to the client at the $200/hour task rate."

For an accounting firm, a task rate could suit a specialized piece of work, such as a review that needs a senior reviewer, a forecast that requires careful modeling, or a memo that calls for detailed analysis. That may be exactly what you want, or it may bill the client for work that someone else did at a lower cost. Decide the rule before the work starts. Ask yourself: when a staff accountant prepares the schedules that a partner reviews under a task rate, should the staff accountant's hours bill at the task rate? Write the answer into your policy, and mention it in the engagement terms when it matters to the client.

Keep the number of task rates small. Each one adds a rule that someone has to remember. A firm with a handful of clearly defined task rates is easier to run than one with a long list of special cases.

Level 5: the project member rate

The fifth level is the most specific. A project member rate applies to one person on one engagement. The Clockify example sets it this way: "The admin sets a project member rate for Elliot on the e-commerce project at $350/hour."

This level is for exceptions that really are exceptions. A senior specialist who joins one engagement for a short, high-value piece of work is a typical case. So is an outside contractor whose work on one matter is priced differently from the firm's usual terms. Because the rate is narrow, it is easy to forget, and an old override can keep billing a rate that no longer makes sense.

The example's figures also show how far rates can spread within a single setup. A project member rate of $350/hour sits well above the $75/hour project rate and the $150/hour member rate in the same examples. A gap that large is easy to set up in software, but in a client relationship it needs a reason you can explain. Record why the override exists and who approved it.

Clean up overrides at the end of each engagement. Remove any project member rate that no longer applies, so it does not carry into the next project by accident.

How the five levels fit together

Each level has a different scope. The table below summarizes what each one covers and the example rate from the Clockify help page.

LevelWhat it covers Example rate on the Clockify help page
WorkspaceDefault for work with no applicable override$100/hour
Project One engagement$75/hour
MemberOne person, across their work$150/hour
TaskA specific task within a project $200/hour
Project memberOne person on one engagement$350/hour

But the examples are not a full rulebook. Your time tracker may resolve conflicts differently, and some combinations may behave in ways the documentation does not spell out. Test the combinations you actually plan to use.

Why rate levels affect your accounting, not only your invoices

Rates matter for more than what the client pays. The timing of revenue and expenses matters too. The U.S. Small Business Administration's glossary of business financial terms describes recognizing revenue when earned: it "Recognizes revenues when earned and expenses are matched with the related revenues and/or are reported when the expense occurs, not when the cash is paid."

For a firm that logs time now and bills later, ask whoever prepares your books whether revenue is recorded when earned or when cash is paid. Ask how work in progress is recorded, and make sure the rate levels produce numbers they can use. The rates and the accounting should agree, and you can only check that if both are written down.

Set the levels before the first bill

Start with a short test. Pick a few realistic time entries: one from a partner, one from a staff accountant, and one from a new hire. Run them against a standard engagement, a negotiated engagement, and an unplanned request with no contract. Check the rate each entry receives. If anything surprises you, fix the setting before the next invoice run, not after the client questions it.

Next, write a one-page rate policy. It does not need legal language. It should answer five questions: what the default is, how a project rate is set, who sets member rates, when a task rate applies and to whom, and who approves a project member override. A policy that fits on one page is more likely to be read and used.

Then decide who owns the levels. In many small firms, the partner makes the calls and the operations lead maintains the setup. Be explicit about that split. If nobody owns the rate list, the list drifts: old overrides stay, new hires get no rate, and staff start entering their own numbers.

Finally, communicate the change. Tell the team what the levels are, why they exist, and how to check which rate applies to an entry. Staff who understand the system are less likely to work around it.

Common mistakes to avoid

Several mistakes come up repeatedly in firms that set up rate levels late.

Using one rate for everything pushes all the complexity into negotiations and bill corrections.

An agreed rate that lives in a message thread is easy to lose. Keep the message as the source record.

A project member rate created for a short engagement can outlast the engagement and bill the wrong person later.

Changing rates in the middle of an engagement without noting when the change took effect makes it hard to explain an invoice later.

A long list of task rates becomes hard to maintain and easy to misapply.

A checklist before billing starts

Use this list before the first invoice run under the new setup:

  • A workspace rate is set, and the policy states what it covers.
  • Each engagement with an agreed hourly price has a project rate, with a note on where the rate came from.
  • Each person who logs billable time has a member rate on the shared list.
  • Each task rate has a written rule for helpers' time.
  • Each project member override has an approver, a reason, and an end point.
  • A set of test entries has been checked against the expected rates.
  • The operations lead and the partner know who maintains the list and when it is reviewed.

For the next check, use the guide to reviewing a client bill.

Closing thoughts

Rate levels are not a complicated system once they are written down. Five levels give the firm enough flexibility to price routine work, negotiated work, specialist work, and exceptions without a separate number for every case. The hard part is the decision-making before the first hour is logged: what the default is, what each level covers, and who can change them.

Related guides: Apply the 22% flat rate before a client bonus payroll · Billable client time: compare 3 rounding methods · Trello and Teams limits for client job tracking: 6 checks.

Sources