Overview

Rate cards and member overrides both affect bill rates, but they solve different problems. A rate card is standard pricing by role. A member override is an exception for a specific person in a specific context.

If many people should share the same role price, use a rate card. If one person needs a special rate, use an override. Keeping that distinction clear makes rate behavior easier to explain later.

Decision guide

QuestionUse a rate card whenUse an override when
Who should use this price?Anyone assigned to the matching billing role.One specific member.
How reusable is the price?The same role price applies across a client, project, package, or year.The price is a negotiated exception.
What should happen when another member joins?They should use the same role price once assigned to the billing role.They should not automatically get this person's exception.
How should reporting explain it?The rate came from standard role pricing.The rate came from a member-specific override.

Use a rate card for standard role pricing

  1. Create the job roles your team bills by.
  2. Create a rate card with one bill rate per role.
  3. Attach the rate card to the client or project.
  4. Add members to the client or project billing roster.
  5. Select the matching billing roles for those members.

Example: Acme Co uses Standard Services. UX Designer is $150/hr and Project Manager is $175/hr. Anyone assigned as UX Designer for Acme Co can resolve to the UX Designer card rate unless a more specific override applies.

Use an override for an exception

  1. Confirm the standard rate does not already cover the situation.
  2. Create the override at the narrowest useful scope: client, project, role, or task.
  3. Set the bill rate and effective dates.
  4. Document why the override exists in the rate name or notes if your workflow supports it.
  5. Review the override when the special agreement ends.

Example: Alex normally uses Acme Co's UX Designer rate, but Website Redesign has a negotiated $120/hr rate for Alex only. That should be a project + role member override, not a new rate card for every designer.

Warning signs you are overusing overrides

  • Most members have individual client or project rates with the same amount.
  • New members require many manual rate records before they can bill standard work.
  • People cannot explain why a member's rate differs from the client rate card.
  • Expired exceptions are still affecting current work.
  • Reporting shows many one-off rates for what is really standard role pricing.

How to clean up an over-customized setup

  1. List the rates that are repeated across multiple people.
  2. Create or update a rate card for those standard role prices.
  3. Attach the card to the right client or project.
  4. Assign members to the matching billing roles.
  5. Expire or remove overrides that duplicate the card rate.
  6. Keep only true exceptions as member overrides.