Admin bonus schemes
Bonus schemes define how weekly (and related) performance translates into payouts. Schemes move through a lifecycle (draft, active, shadow, archived, and transitions your organization uses). Only certain states write to production payout tables after scorecard processes run.
Editor and preview
- Choose Scorecard audience (Driver or Dispatcher) when creating a scheme; it cannot be changed after save. Metric pickers and eligibility fields list only metrics for that audience.
- Use the scheme editor to configure rules, tiers, and qualifying logic.
- Weekly scorecard preview (sidebar on create and edit) runs the calculator for each user on the same roster and filters as
/admin/scorecard/weekly, for the selected operational week. Driver audience schemes preview users with a linked Samsara driver; Dispatcher audience schemes preview users with a linked dispatcher row. Nothing is saved. - On tiered schemes, eligibility can reference one metric (for example driver efficiency) while payout bands follow the Scorecard metric you select for bonus calculation (for example safety). A user can pass efficiency but still earn $0 if every band amount is $0, or fail eligibility even when another metric looks strong for a different week or data source.
Lifecycle operations (promote, activate, deactivate, archive, clone to draft) appear where your permissions allow. For shadow versus active behavior and weekly locks, your operations docs complement this article.
Delete vs archive: The scheme show page Danger zone can permanently delete a scheme only when it has never written production payout rows (bonus_payouts). Shadow evaluation rows are removed with the scheme. If the scheme has pay history or an in-flight pending week, use Archive instead so historical payouts stay traceable.