Rate Cards for Resource Types
How rate cards price a resource type by state and period, with pay and charge rates, minimums and billing clocks, and how the default card is chosen.
A rate card holds the rates for a resource type: what it costs you, shown as Pay, and what you charge for it, shown as Charge. Each resource type owns its rate cards, so pricing for a type lives with the type.
How Rate Cards Work
A type can have several cards, and one of them is the default. The first card you add becomes the default automatically. Because cards belong to a type, a card cannot be shared with another type. If two types cost the same, each carries its own card.
When BackOps prices a request for a resource, it uses the first card it finds in this order:
- A card chosen on the request itself.
- The card of the variant the request matches.
- The type's default card.
The resources you own, and the variants of a type, can link to several of the type's cards with one marked as the default. A single truck can carry a standard card and a weekend card while still having one default to fall back on.
Rates, States and Periods
A card is a list of rates. Each rate prices one state, such as Regular, Overtime or Holiday pay, so the same hour can cost more once a rule moves it into overtime. States are created under States in Resource Templates, and a card cannot have rates until at least one state exists. See States, Block Types and Categories.
Each rate has one or more billings, by Hour, Day, Week, Month or Flat / per unit. Every billing has a fixed part and a variable part, for both Pay and Charge. On a time billing the variable part accrues per hour, and a Day, Week or Month billing can say how many Hours included the period covers. On a Flat billing the variable part is per unit, which is how a type with a Unit attribute is priced by the mile, and the billing can set a minimum number of billable units.
A state prices time one way only. It can have one time billing, such as Day, plus a Flat fee beside it, but not both an Hour and a Day billing.
Minimums and Billing Clocks
A card's Minimums set a floor under the price. A money minimum sets a Minimum cost and a Minimum charge. A time minimum, billed in hours, days, weeks or months, holds a booking to a minimum length. The time minimum applies once per shift across every state, so a call that runs into overtime is held to one minimum, not one per state.
Billing clocks say when a period count or a minimum starts over. A clock starts a new billing period after a gap in the schedule, after a block of a given type, or at the start of each calendar day, week or month. Once a card has clocks, choose one for Period count resets, Money minimum resets, Time minimum resets, or on a single rate under This rate resets. With no clocks, minimums and period counts apply once across the whole engagement.
Add and Manage Rate Cards
Open the type
Add a card
Add rates
Choose Add rate, pick a State, and add a billing for each period you price. Enter the Pay and Charge amounts. If no states exist yet, the button reads Add state instead.
Set minimums and clocks
Choose the default
The Used by column shows what points at each card, such as variants and inventory resources. A card that is in use cannot be deleted, and the delete option's tooltip names what uses it. Move those references to another card first. Deleting the default card makes another of the type's cards the default.
A composite type's cards set only the charge. Its cost always rolls up from its components, so the card shows the rolled-up cost instead of Pay fields. See Composite Resource Types.