From a draft plan to an approved allocation, inside your own org.

01Build the plan and watch the cost as you type

A planning workspace, not scattered tabs

Grid, approvals, portfolio, instructor board and setup live in one place, instead of separate pages someone has to remember to check.

Courses are the plan, not an afterthought

Every course the department might offer is a row, staffed or not. An unstaffed course is something you can see and fix, rather than something absent.

The cost shows up before you save

Type a quantity against a position and the rate resolves from your own rate cards, totalling as you go. Nobody re-keys numbers into a spreadsheet to find out what a plan costs.

An unpriced position is a flag, not a silent zero

A line with no rate for that position and year is flagged, not quietly totalled as free.

Instructor search starts with who's already on the plan

Assigning an instructor searches the people already on that plan, not every contact in the org. Searching wider is a deliberate step, and anyone found that way stays marked as one.

A conflict hint that stops at the boundary it should

Assigning someone already committed elsewhere says so at that moment — that a commitment exists, and nothing more. Not the department, not the plan, not the amount. Enough to ask the right question, not enough to see across a line you are not entitled to.

What-if planning that cannot touch the real plan

Copy a plan, change it, compare the two side by side, promote the one that wins. The plan of record is never at risk while you explore.

Starter+

Your bargaining-unit titles, not just ours

Import your own position and rate data from CSV. Every row is validated first, and the file loads completely or not at all — a half-loaded rate card does not fail loudly, it prices something at zero.

A rate card that arrives late leaves no stale lines behind

A batch job reprices any line left at zero because its rate card arrived after the plans did.

Buyout accounting is a setting, not a guess

Whether external funding on a buyout reduces the department's dollar ask is your institution's choice, with a per-line override for the genuine exception. The setting survives when a plan is copied forward.

Follows the institution's currency, not a hardcoded one

It reads your org's currency, and each user's own the moment Salesforce Multi-Currency is on. Nothing to configure separately.

02Route it through the approval chain you already have

Stages built from who your institution actually names

Not a fixed four-person chain. Five slots you name yourself, or ten on Premium — enough for a campus routing through school, division, budget office, senate and provost. A stage nobody has been named for is skipped, not left blank.

The order is yours to set

If your budget office signs off after the dean rather than before, reorder the slots. The router, the preview and the approver badges all read the same order, so a plan cannot preview one route and then take another.

Starter+

A queue for the people who approve, not just the people who plan

Each approver sees only what is theirs to decide. A plan with unpriced lines cannot reach them until those lines are acknowledged.

Caps evaluated automatically, not policed after the fact

Per-department caps are checked at submission. A plan over its cap is flagged for the approver to allow or deny, with the effect on the total shown as they decide.

Starter+

Approve a stack of plans in one action

A dean approves a queue in one action instead of clicking through plans one at a time. Each plan commits on its own, so one bad plan cannot roll back the good ones.

Starter+

03Totals that cannot disagree with each other

The screen, the report and the record page cannot disagree

Every dollar figure is a native rollup, computed once, and all three read the same field. There is no second, code-calculated version of the number to drift from it.

An immutable record of what was actually approved

Approving a plan freezes a snapshot, and a built-in check reconciles any live plan against any snapshot. That is what makes a cutover from an old system verifiable rather than hoped for.

Approved cost is on the record permanently, at every tier

Submit, approval and finalization each capture the approved cost permanently, with no way to purge it. Procurement asks this early; the answer is already here.

Lists are capped; money is not

Where a screen limits how many rows it shows, the totals above it still cover everything in scope. A shortened table can never quietly shrink the number that matters.

Tested like software that handles real budgets

Automated tests across the server logic and the interface run before any change ships. Regression tests are proven by breaking the fix on purpose and watching the test catch it.

04See the whole department, and the whole institution

Workload across a department, at a glance

Who is committed to what, with exact totals even when the list below them is capped for readability.

A dean's view and an analyst's view of the same data

Portfolio home, budget report, worksheet and cost-by-role. Allocation against planned cost, with no export step in between.

Starter+

Compare scenarios across a whole portfolio, not one plan at a time

Line up scenarios across every department in one view, instead of opening plans one after another. A comparison too large to hold is refused with an explanation, never silently trimmed.

Premium

Reports and dashboards that ship in the box

They read the same rollups the screens do, so there is no second reporting calculation to keep in sync.

05Access controlled the way a university actually needs it

Private by default

Plans, ledgers, transfers and workload records start private. Access is computed and granted deliberately, not left open and policed by habit.

Sharing computed from your own org chart

Each plan is shared with its department's actual approvers, and recalculated automatically when the department or owner changes.

A planner's permission set that cannot see past its own department

Everything a planner needs day to day — build, cost, submit — with no org-wide “see and edit everything” grant baked in.

Field-level security enforced, not assumed

Every user-facing query and write states the access level it runs under, rather than inheriting one from the sharing model and hoping.

Who can act on a plan changes with its status

The owner while it is a draft, the current approver once submitted, nobody once approved. Any bypass is an administrator grant that ships assigned to no one.

06Install and configure without an engineer on call

A real Salesforce managed package

Installed from a version ID like any AppExchange product, not a bundle of source that someone has to deploy by hand.

A guided setup wizard

Six steps: institution basics, the academic calendar, departments and approvers, positions and rate cards. Each one reports whether it is actually finished.

Historical plans, without a data migration project

Old plans load as queryable snapshot records, so the history is there to look at without migrating tens of thousands of transactional rows.

Premium

Documentation written for an administrator who has never seen the codebase

Install, configure, administer, and the concepts underneath. Every cross-reference is checked, so a link cannot quietly rot.

07Built to hold up as an institution grows into it

Every list has a ceiling, and every ceiling says so

Nothing degrades quietly. A capped screen says it is capped.

Bulk operations refuse a batch they cannot finish

They refuse before touching anything, rather than failing partway and leaving a half-done job behind.

The planning grid does not recompute what it already knows

Grouping and totals are cached, and thrown away only when something underneath actually changes.

Large grids render only what is on screen

With full keyboard navigation, so a department with hundreds of lines is not a slow page.

The cross-department instructor board is precomputed overnight

It only recalculates live if the cache goes stale. Rarely slow, never wrong.

Premium

Plan finalization runs in safe batches

Not one giant nightly job that can die quietly at scale.