Set yourself up
You can do the whole of the first ten minutes here without waiting for anybody. Nothing below is sent anywhere, nothing is charged, and you can stop and come back to exactly where you left off.
Where you are
0 of 6 required answersWhat each capability would give you
Two open in a self-onboarding session3
Compliance and Cost Savings
Multi-state workforce exposure, worker classification and the savings case that follows from them. Seven points, each one a thing your institution either has an answer to or does not.
Read this before you read a number on this page
This program does not currently score your exposure, and saying otherwise is the specific mistake being corrected here. The screen that appeared to do it held five states written into the source with every answer fixed, and the institution it was shown to made no difference to what it said. It was recorded as live for months. Nothing on this page is a compliance assurance, and none of it is billable until the state catalogue is a maintained legal dataset rather than a representative seed.Points in the program
7
across two sections
Engine exists
0
of 5 in section 1
Partial
2
classification and savings
Billing
Off
by decision, see 1.4
1. Multi-state exposure and monitoring
Five points · none built2. Classification and cost savings
Two points · both partialYour state footprint
No states declared yet
Every state you declare is shown here whether or not it is unlocked. Hiding an unpaid state would
hide your own risk footprint, which is the opposite of the point. What an unlocked state adds is the score,
the requirement detail, the citations and the remediation list.
Declare your states in step 2 of the VMS setup. Nothing is charged and
nothing is unlocked by declaring them.
What it would cost
Agreed pricing · billing switched off
An employee counts once however many states they work in: the state fee already prices the states.
There is no free state, deliberately, because a free one is the one nobody checks.
Nothing is billable today and point 1.4 above is why.
How the monitoring is designed to work
Designed, not yet running
The promise is not that a statute is parsed by a machine the second it is amended. It is that every source
registered for your states is checked on a stated cadence, the screen shows when each was last checked, and
a person reviews every detected change before you are told anything. That
review step is deliberate. It is what stops an automated feed telling you something wrong, quickly.
Cadence
Hourly job
The Federal Register every run. Each state source at least once every 24 hours, staggered so roughly a twenty-fourth are fetched per run.
A detection
Not a conclusion
A changed content hash, a Federal Register document, or a known rule whose effective date crosses today. It lands in a review queue with the before and after excerpts.
Before you hear anything
Two people
A reviewer confirms or dismisses with a reason. A change that would flip you to non-compliant on a critical requirement needs a second internal approval before the notice sends.
Then how fast
One business day
Internal notice within an hour of confirmation; your notice within one business day for a critical change, otherwise in the weekly digest.
If we are wrong
Retracted, never deleted
A finding judged wrong is struck through and a correction references the original by id. A deleted row would look like concealment.
If the watcher stops
Red banner
A source not checked within twice its cadence, or a job that misses its heartbeat for three hours, raises an alarm. A monitor that can die silently is worse than none.
What an institution can do today, honestly
The two partial points are the ones with something behind them: person types are captured, so a classification view has real data to sit on, and the savings method exists as a worked model even though the in-app calculator does not. Everything in section 1 needs a decision before it needs a build, and the decision in 1.5 is the one that gates the rest: nothing can report a state footprint until it is settled where a worker's work state actually comes from.1
Set up your VMS
Six steps, roughly ten minutes, and you can stop and come back. Every question here is one somebody would otherwise ask you on a call, and each one says why it is being asked.
Your institution
This names the tenant and decides which of the higher-education defaults apply. A community college and a research university get different requisition approvals out of the box, and changing it later means re-approving live requisitions.
An estimate is fine. It sets the default page sizes and whether bulk import is switched on, nothing more.
Where your people work
Select every state where somebody physically works, including remote workers sitting outside your own state. This is the single most consequential answer in the wizard: it drives tax registration questions, and it is the input the compliance program cannot currently derive on its own.
Pick the ones you know. You can add more later, and adding one never removes work already recorded against another.
Why this is asked rather than worked out
Neither the billing nor the payroll warehouse carries a state dimension, so a footprint derived from existing data cannot be trusted. Asking you is the honest option until that is fixed. It is recorded as compliance point 1.5.Worker types you engage
Each type turns on a different set of screens and a different onboarding path. Leaving one off is easy to correct; turning them all on gives everybody a cluttered product on day one.
Your academic calendar
This is the step a corporate VMS does not have, and it is the reason courses can exist here at all. A course is an adjunct hired to teach a specific section, for a specific term, for a specific fee. Pay follows the academic calendar, not a corporate pay cycle, so the term dates are what the milestones are generated from.
One real number. It is used below to show you the schedule those dates would produce, and nothing is created.
Monthly means the 1st of each month after the course starts, which is what the intake form does. Weekly and bi-weekly land on Fridays.
A course is not a statement of work
The university still manages the professor: they are your faculty member. nextSource is Employer of Record for payroll, tax and the W-2 only. That is why a course is always W-2 with a unit payment rather than a rate, and why it has its own intake form instead of being a configuration of a vendor-managed project.The milestones those dates would generate
Give a start, an end and a feeApprovals
Who has to say yes before a requisition becomes a work order. Start with the fewest approvers that would satisfy your finance office: every extra approver is a day of time to fill, and adding one later is a two-minute change.
Leave blank to route every requisition the same way.
Funding and cost centres
Higher education is the reason this step exists. Grant-funded work has an end date and a cap that general-fund work does not, and getting the fund type wrong is discovered at closeout rather than at hire.
One real example. It is used to validate the rest, so a wrong code is refused at entry rather than at the general ledger.
Check it, then start
Nothing has been created yet. Everything below is what will exist the moment you finish, and every line is editable afterwards.
Step 1 of 6
⚠
Claims against reality
For Erik, Stefani and whoever owns the site copy. Every promise hghred.com makes about compliance, quoted exactly, against what the readiness board says is behind it. Not linked from anywhere a prospect goes.
The sharp one
The site offers a free diagnostic consisting of a compliance score and a list of at-risk workers. Both are readiness points recorded as not built. It is a public offer in the present tense with no qualifier, so somebody can accept it this afternoon and it cannot be produced. Everything else on this page is a wording problem; that one is a commitment.What the website promises, and what is behind each promise
Read before quoting the site
Rows marked not behind it are promises the readiness board records as
not built. They are on a public page in the present tense, and two of them are offered as a free
diagnostic, so a prospect can ask for one this afternoon.
1
Courses
An adjunct hired to teach a named section, for a term, for a fee. The course is the unit of work, and the pay schedule comes from the academic calendar rather than from a corporate pay cycle.
A course is not a statement of work, and the difference is who manages the professor
With a statement of work the vendor manages the people and delivers an outcome. With a course the university still manages the professor: they are your faculty member, teaching your section, to your syllabus. nextSource is Employer of Record for payroll, tax and the W-2 only. That is why a course is always W-2 with a unit payment rather than an hourly or daily rate, and why it has its own intake form instead of being a configuration of a vendor project.What a course carries
The intake form's own fieldsTry the payment schedule
Give a start, an end and a fee
Monthly pays on the 1st of each month after the course starts, through the 1st of the month after it
ends. Weekly and bi-weekly land on Fridays. The split is even and the rounding remainder goes on the
last payment, so the schedule always ties to the fee exactly.
What happens either side of the schedule
Before
Term dates
A course cannot exist without a term. The dates come from your academic calendar, which is why the setup wizard asks for them.
During
Breaks in service
Semester gaps, re-hire, multi-course loads and per-course pay are part of the model rather than a spreadsheet a department keeps on the side.
After
Payroll, as EoR
The milestones become the pay schedule. nextSource is the legal employer for payroll, tax and the W-2; the teaching relationship stays with you.
🔒
Capability
You are seeing this because your account cannot open this capability yet. It is listed anyway, and deliberately. A menu that hides what you lack teaches you the product is smaller than it is, and the first thing most people want to know about a platform is what else is in it.
Access is granted per capability rather than per screen, so turning this on gives a person everything inside it and nothing outside it.