Runbook

Payroll Correctness Review

When payroll has a question, build the record before guessing.

Bring one payroll question. Runbook organizes the facts, evidence, timeline, assumptions, conflicts, and missing records into a packet you can use with your CPA, payroll provider, or internal team.

Request a review View pricing

This is a limited review offer. It is not live payroll processing, tax filing, money movement, agency representation, or legal, tax, accounting, or financial advice.

REVIEW PACKETPCR-2026-###
Packet verdict Assumed + missing

Paystub changed, but timecard and final payroll register are still needed before the answer can be verified.

Facts Evidence Timeline Calculation Next action

Illustrative packet preview. Real reviews use customer-provided evidence and explicit status labels.

Good first cases.

The review is for a narrow payroll question where the buyer needs the record organized before the next decision.

01

Wrong or changed paycheck

Show what changed, which source facts support it, and what is still missing before the answer can be trusted.

02

Payroll tax notice

Organize the notice, affected period, deposits, filings, provider records, conflicts, and advisor questions.

03

Provider switch

Check whether prior-provider YTD wages, withholding, wage bases, and payroll liabilities are ready to carry forward.

04

CPA cleanup

Turn screenshots, registers, exports, and client explanations into a packet an advisor can actually review.

What the customer receives.

The deliverable is not a loose opinion. It is a structured packet showing verified facts, missing evidence, assumptions, conflicts, and the next action.

1ScopeThe one question Runbook is reviewing and the boundaries of the review.
2Fact inventoryEmployer, worker, pay period, earnings, tax, jurisdiction, and provider facts.
3Evidence inventoryDocuments received, missing, conflicting, redacted, or out of scope.
4TimelineWhat happened, when it was effective, when it was recorded, and what was learned later.
5Calculation or reconciliationThe path from source facts to the payroll number, with estimates labeled.
6Next actionProvider question, correction path, advisor review, referral boundary, or stop/go decision.

Secure intake posture

Dropbox now. SmartVault later. Same evidence model.

Early reviews use a controlled, manual Dropbox file request only after a case is scoped and payment or owner approval is recorded. Runbook stores the case model, evidence labels, provider references, and packet logic. Raw payroll files stay in the document provider.

Before acceptanceNo sensitive payroll documents through the public form.
After acceptanceOne case id, one scoped request, separate password when available, and a closed request after receipt.
Future upgradeThe same fields map to SmartVault when validation or risk justifies the spend.
DOCUMENT PROVIDERProvider-neutral
Case idPCR-YYYY-###
WorkspaceFolder / vault / portal
RequestScoped evidence list
ObjectsProvider references
Runbook storesMetadata only

Offer levels for manual validation.

These are validation prices for scoped review work, not final full-service payroll pricing.

Starter

Paycheck question

$250-$500

One worker, one pay period, limited evidence inventory, status labels, and a short explanation packet.

Standard

Notice or switch packet

$750-$1,500

One payroll notice, correction, provider switch, or reconciliation question with full packet structure and next-action summary.

Advisor

Practice validation

$2,500-$5,000

Three to five cases for a CPA/bookkeeper workflow, including repeatability review and product feedback.

Prices are validation estimates. Runbook may decline, narrow, or refer a case if the issue requires representation, emergency legal action, unsupported jurisdiction analysis, or unsafe evidence handling.

PAYMENT PATHManual first
TriageNo charge
Scope acceptedInvoice or payment link
Evidence requestAfter payment or approval
App billingDeferred

Payment before evidence

Charge only after the question is scoped.

Early reviews are sold manually. Runbook confirms the question, scope letter, price band, exclusions, and minimum evidence list first. Then the customer receives an invoice or Stripe Payment Link. Only after payment or explicit owner approval should Runbook open a document request.

No self-checkout for broad payroll evidenceThe public form collects scenario context, not documents or payment credentials.
Payment references stay in the trackerRecord invoice/payment link id, amount, status, paid date, and refund/cancel status.
App billing waitsSubscription billing, metered usage, and in-app checkout come after the review workflow proves repeatable.

How a review moves.

The workflow is intentionally manual until real cases prove which questions buyers will pay to answer.

1

Triage

Confirm the role, provider, scenario, urgency, and whether the question is narrow enough.

2

Scope

Define the question, exclusions, price band, and minimum evidence list.

3

Request evidence

Use a controlled provider request after acceptance; no public document links.

4

Inventory

Label evidence as usable, redacted, insufficient, conflicting, missing, or out of scope.

5

Analyze

Build the timeline, separate verified facts from assumptions, and reconstruct the answer.

6

Deliver

Send the packet and capture whether the review reduced uncertainty or created a payroll buyer.

Start the intake

Request a Payroll Correctness Review

Share the scenario, not the payroll files. Runbook will confirm whether the question is narrow enough, then send scope, price, exclusions, and the secure evidence path before asking for documents.

Email directly

Temporary implementation: this prepares a structured email. The future endpoint is `POST /api/review-inquiry` and must collect metadata only, with no file uploads or sensitive payroll data.

Bring one payroll question. We will tell you whether it can be reviewed.

Do not send payroll documents through the public form. Start with the scenario and we will confirm the right intake path.

Request a review