Wrong or changed paycheck
Show what changed, which source facts support it, and what is still missing before the answer can be trusted.
Reviewable payroll records
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.
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. A review does not monitor or manage agency or filing deadlines — those stay with you — and it creates no attorney-client, accountant-client, or fiduciary relationship.
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.
Payroll tax notice
Organize the notice, affected period, deposits, filings, provider records, conflicts, and advisor questions.
Provider switch
Check whether prior-provider YTD wages, withholding, wage bases, and payroll liabilities are ready to carry forward.
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
Illustrative review levels.
This is a paused service concept shown for product context. Runbook is not accepting or pricing review work.
Paycheck question
Paused
One worker, one pay period, limited evidence inventory, status labels, and a short explanation packet.
Notice or switch packet
Paused
One payroll notice, correction, provider switch, or reconciliation question with full packet structure and next-action summary.
Practice validation
Paused
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 PATHNot active
TriageNo charge
Scope acceptedPaused
Evidence requestPaused
App billingDeferred
Payment before evidence
A future review would begin with scope.
This workflow is a design concept, not an active offer. Before any review service opens, Runbook would confirm the question, scope, exclusions, minimum evidence list, secure intake path, and payment terms.
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.
Triage
Confirm the role, provider, scenario, urgency, and whether the question is narrow enough.
Scope
Define the question, exclusions, price band, and minimum evidence list.
Request evidence
Use a controlled provider request after acceptance; no public document links.
Inventory
Label evidence as usable, redacted, insufficient, conflicting, missing, or out of scope.
Analyze
Build the timeline, separate verified facts from assumptions, and reconstruct the answer.
Deliver
Send the packet and capture whether the review reduced uncertainty or created a payroll buyer.
Review concept
Payroll Correctness Review intake is paused
Runbook is not accepting scenarios or payroll documents for this service. The material below illustrates a possible controlled intake design; use the current-status page for availability.
Public intakePaused. Do not send scenario metadata or payroll records.
No documents yetDo not upload payroll registers, tax notices, SSNs, worker addresses, bank details, or provider exports in the public intake.
Next stepCheck the current-status page for any future availability.
The review concept is paused.
Do not send payroll questions or documents. Check current status for the public surfaces that are available.
See current status