How to Set Different Pay Rates for Different Instructors

The problem with a single pay rate

Most schools don't pay every instructor the same amount. A senior tutor earns more than a junior one. A specialist brought in for test prep commands a higher rate than someone covering general homework help. A tutor who covers another instructor's students might earn less per session than when teaching their own.

If you're managing this on a spreadsheet, you're probably doing one of two things: maintaining a separate tab for each instructor's rates, or just trying to remember it all and correcting mistakes at the end of the month. Neither scales well once you have more than a handful of staff.

The good news is that the underlying logic isn't complicated. There are really only three questions to answer, and once you've answered them, the rest is just documentation.

The three questions to answer before you set anything up

1. What is this instructor's baseline rate?

Every instructor should have a single default rate — the amount they're paid when nothing more specific applies. This is your fallback. If you haven't set one, you're relying on memory, and memory fails.

2. Does this instructor get paid differently for certain services?

A tutor might earn $40/hr for college essay coaching, $35/hr for subject tutoring, and $20/hr for admin time. These are service-level overrides — they apply whenever that instructor teaches that type of session, regardless of which student is involved.

3. Does this instructor get paid differently for a specific student or enrollment?

Sometimes the rate is tied to a particular arrangement rather than a service type. A tutor covering another instructor's students might earn $110/session for those lessons but $135/session for their own students. That's an enrollment-level override.

The resolution order matters: enrollment override beats service override beats default rate. If you've set all three, the most specific one wins.

A worked example

Say you have a tutor whose standard rate is $30/hr. She teaches four different service types:

You'd set her default at $30/hr, then add four service-level overrides for the exceptions. Any session that doesn't match one of those overrides automatically falls back to $30/hr. You don't need to list every service — only the ones that differ from the default.

Now say she also covers a colleague's students on a temporary basis, and the arrangement is $25/hr for those specific lessons. You'd add an enrollment-level override for each of those enrollments. Her service-level rates and default rate stay untouched.

Hourly rates vs. session rates

Not every school pays by the hour. Some pay a flat amount per session regardless of length — for example, $50 per parent-teacher meeting, or $135 per tutoring session.

Before you set up your rate structure, decide which model applies to each instructor (or each service type). Mixing the two is fine, but be explicit about it. A common mistake is setting an hourly rate for someone who's actually being paid per session, then being surprised when a 45-minute lesson generates a different payout than expected.

What changes when you update a rate — and what doesn't

This is the part that catches people out. When you change an instructor's rate — whether it's their default or an override — the change applies to pending and future sessions only. It does not retroactively update sessions that have already been submitted for payroll.

That means:

• If you realize you've been paying someone the wrong rate for the past month, you'll need to handle the correction manually for those past sessions.

• If you update a rate mid-month, sessions already submitted stay at the old rate; sessions not yet submitted pick up the new one.

• The safest time to make rate changes is before the pay period begins, not during it.

A practical setup checklist

Before you open any software, work through this on paper or in a spreadsheet:

1. List every instructor. Include anyone who gets paid per session, even occasionally.

2. Set a default rate for each. If you're not sure, use their most common rate. You can always add overrides.

3. Identify service-level exceptions. For each instructor, note any service types where their rate differs from the default.

4. Identify enrollment-level exceptions. Note any specific student arrangements that differ from both the default and the service rate.

5. Decide: hourly or per-session? For each instructor or service type, be explicit.

6. Document the resolution order. Write it down somewhere your team can find it: enrollment override → service override → default.

Once you have this documented, entering it into any system — software or spreadsheet — is straightforward. The documentation is the hard part, and it's also the part that protects you when someone questions a payout.

One thing to watch for: who can change rates

In some schools, the person who manages scheduling isn't the same person who manages payroll. If that's your situation, be clear about who has permission to add or change pay rate overrides. One tutoring centre found that a staff member without billing permissions couldn't set overrides at all — those had to be handled by a billing administrator. Sorting out that access question before you need to make a change saves a lot of back-and-forth.

A note on what we built

Noto is school management software built for exactly this kind of setup — default rates per instructor, service-level overrides, enrollment-level overrides, and both hourly and per-session rate types. The logic described in this article is how Noto's payroll system works. If you're looking for software that handles multi-tier instructor pay without a spreadsheet, it's worth a look.