Setup home

Your next payroll task lives here.

Runbook keeps the next step, owner, and evidence boundary visible while payroll setup is still being routed. This is a static task home for manual onboarding, not a production payroll workspace.

View current status Change setup answers

What happens next

One task, one owner, no sensitive evidence yet.

Use the active card as the next manual step. The other cards stay visible so a buyer can change paths without starting over.

Payroll

Confirm first-payday setup

Best for employers starting payroll, hiring a team, adding contractors, or evaluating Runbook as the payroll provider.

Next task: Confirm first payday target, worker mix, states, and current provider status.
Owner: Buyer starts intake; Runbook responds with the setup path.

Switch

Scope the provider handoff

Best when prior-provider wages, filings, deposits, deductions, and corrections need review before handoff.

Next task: Name the current provider, target first Runbook pay date, states, and known gaps.
Owner: Runbook decides whether a switch checklist is needed.

Notice

Bound the notice question

Best when a payroll tax notice needs to be mapped to payroll periods, deposits, filings, and evidence gaps.

Next task: Share the agency, deadline, filing period, provider involved, and who needs the answer.
Owner: Runbook scopes whether this belongs with payroll, CPA, tax advisor, or counsel.

Correction

Reconstruct the payroll question

Best when a paycheck, late fact, retro item, deduction, or correction needs a payroll answer.

Next task: Describe the pay period, worker type, provider involved, and the question in one sentence.
Owner: Runbook writes a bounded scope before any records move.

Advisor

Pick one client scenario

Best for CPAs, bookkeepers, and payroll advisors evaluating Runbook for client payroll review or setup.

Next task: Send a metadata-only client scenario: provider, state count, issue type, and urgency.
Owner: Runbook proposes the advisor review or setup path.

Multi-state

Map state and local payroll facts

Best when state, local, remote-work, registration, or tax-account facts need to be understood before payroll runs.

Next task: List work states, local tax exposure, current registrations, and first-payday timing.
Owner: Runbook routes payroll setup or a scoped review.

Proof

Inspect the sample record

Best when a buyer wants to see the Runbook record model before starting a payroll setup conversation.

Next task: Open the sample proof packet and verifier, then reply with the payroll path to evaluate.
Owner: Buyer reviews the sample; Runbook answers setup-path questions.

Open the sample proof packet

Evidence boundary

Do not upload or email payroll records yet.

This page is for setup routing only. Runbook asks for sensitive payroll evidence only after the path, scope, approval/payment, and secure request are clear.

Allowed nowCompany name, contact details, provider name, worker count, states, current situation, and target timing.

Not yetSSNs, bank details, worker addresses, tax documents, payroll exports, notices, paystubs, or broad worker files.

Later, if scopedA secure request with a document list, owner, deadline, and evidence inventory rules.

Continue with the current setup path.

Runbook will use the selected path to route the manual follow-up. Sensitive payroll records stay out of public forms and ordinary email.

See current availability