Tillzen manual operating kit

Daily Closeout Manual Kit

A printable operating board that turns Tillzen's closeout record process into a manual store-review routine.

Use whenUse it when teams need a practical checklist, not another high-level cash handling article.

OutputA store-ready record standard for a two-to-four store closeout pilot.

Manual goalSee whether one store can leave fewer unanswered questions after close.

Run the Tillzen Process Manually

Use the stages like a board during closeout review. The point is not a perfect store. The point is a close that district and finance can review without hunting through messages.

Closeout Packet Board

Fill one row per store closeout. If an answer is missing, keep the item open instead of letting yesterday become a memory exercise.

Store / location

Where the closeout belongs

Identity

Date / shift / drawer

Tie the count to the operating moment

Identity

Expected vs counted

Write the POS expected amount beside the physical count

Count

Evidence trail

Attached, delayed, missing, unclear, or not applicable

Support

Exception reason

Shortage, overage, timing, proof, process, or repeat pattern

Explain

Owner / due route

Store, district, finance, payroll, or accounting review

Assign

Evidence Trail

Use these labels so missing or unclear support does not disappear after the store says close is done.

Attached

Evidence is present, legible and tied to the same store, shift, drawer, safe, or deposit event.

Delayed

Evidence is expected after a known bank, bag, safe-drop, or manager handoff window.

Missing

Evidence should exist but is absent, so the packet stays open with an owner.

Unclear

Evidence exists but the reviewer cannot connect it to the closeout without more context.

Not applicable

No evidence is required under the policy for this specific event.

Record Scoreboard

Score each record from 0 to 2. A 2 means the record is easy to check now. A 1 means the owner is known. A 0 means the reviewer has to rebuild the shift.

Area	Easy-to-check signal	Drift signal
Identity	Store, date, shift, drawer, safe, manager and reviewer are visible.	No named reviewer or mixed store/date context.
Cash	Expected amount, counted amount and cash gap are shown together.	Reviewer must compare POS, notes and spreadsheet rows.
Support	The reviewer can see the deposit support beside the daily close.	Support lives in texts, email, camera roll, or shared drive.
Exception	Reason, owner, due path and resolution state are specific.	Vague notes like checked, ok, or will fix later.
Review	Final resolution can be inspected without rebuilding the shift.	Follow-up disappears after manager sign-off.

Reviewer Checks

Use these checks before the closeout moves to finance, district review, payroll context, or the pilot report.

Store, date, shift, drawer, safe, manager and reviewer are visible.

Expected cash, counted cash, deposit proof and proof status stay together.

Every cash difference has a typed explanation, owner and next review follow-up.

The record can be reviewed the next morning without calling the manager first.

Decision Route

End every packet in one route so the next action is not hidden in a message thread.

CleanRecord is easy to check without follow-up.

OpenPacket is usable, but one owner action remains.

EscalateThreshold, repeat pattern, or unresolved proof needs district or finance review.

LearnAdd the pattern to the pilot report before rollout expands.