Shift handover sheet: the business day is a decision somebody records.
Who owned the trading period, when it opened and closed, what the cut-off was, the cash state you are handing over, the payment-mode split, and everything still open with a name against it. One handover, two named people, two sign-offs. Copy it as CSV and use it at the changeover.
The template, filled with an example
The example is one fictional counter, one business day on a 22:00 cut-off, and the handover at the close of the evening shift. The float issued at the changeover was ₹3,000.00, the evening shift took ₹24,150.00 in cash, and the drawer came up ₹60.00 short after two counts. Every total on the sheet is computed from the figures shown rather than typed in, so the arithmetic can be checked.
Illustrative example only. The counter, terminal, both shift owners, the manager, the customer, and every amount and time on this page are invented. No shrinkage figure, no typical cash variance, and no average behaviour of any kind is claimed anywhere on it — the numbers exist so the arithmetic on a handover can be checked. A business day is an operating convention, not a statutory or filing period, and recording it well is not the same as reconciling bank, UPI, or card settlement.
Shift and business-day header
- Location
- Sample Retail Counter — Bengaluru (example)
- Counter / terminal
- Counter 1, terminal T-04 (example)
- Business day
- 04-10-2026 08:00 to 04-10-2026 22:00 — an interval, not a calendar date
- Cut-off for this location
- 22:00, fixed — written down as a setting, not held as a habit
- Handover
- Close of the evening shift S2 to the open of the morning shift S1 on 05-10-2026
- Outgoing shift owner
- Sample Shift Lead B (example)
- Incoming shift owner
- Sample Shift Lead A (example)
- Outgoing shift closed at
- 22:12 — after the 22:00 cut-off, with the reason recorded below
- Incoming shift opened at
- 22:14, from the state written on this sheet
- Currency
- INR
The shifts in this business day
| Shift | Period | Owner | Trading hours | Cash (INR) | UPI (INR) | Card (INR) | Bank (INR) | Total (INR) | Sign-off |
|---|---|---|---|---|---|---|---|---|---|
| S1 | Morning, 04-10-2026 | Sample Shift Lead A (example) | 08:00 to 14:00 | 18,400.00 | 31,250.00 | 14,800.00 | 0.00 | 64,450.00 | Signed off at 14:08 by the shift owner |
| S2 | Evening, 04-10-2026 | Sample Shift Lead B (example) | 14:00 to 22:00 | 24,150.00 | 48,300.00 | 31,450.00 | 6,200.00 | 1,10,100.00 | Signed off at 22:12 by the shift owner, handed to S1 at 22:14 |
Each row is a period of trading with one named owner, closed with a sign-off. A shift is not a timesheet: there is no hours-worked record behind these hours and no payroll module attached to them. They exist so that a sale can be attributed to a person and a period, which is what makes a variance a fact rather than a feeling.
Payment-mode split for the outgoing shift
| Payment mode | System total (INR) | Counted (INR) | Variance (INR) | Note |
|---|---|---|---|---|
| Cash (sales only) | 24,150.00 | 24,090.00 | (60.00) | Cash drawer, counted twice at 22:08 and 22:12 |
| UPI | 48,300.00 | 48,300.00 | 0.00 | Matches the provider counter for the shift. Settlement is a separate check on a separate timetable |
| Card | 31,450.00 | 31,450.00 | 0.00 | Counter total only. One hand-keyed entry is not yet confirmed on the provider batch |
| Bank transfer (NEFT / RTGS) | 6,200.00 | 6,200.00 | 0.00 | Two transfers received after 18:00, both matched to a bill |
| Total collections for this shift | 1,10,100.00 | 1,10,040.00 | (60.00) | The variance on this line is the cash difference, not a shortfall in takings |
Only cash is physically in the drawer. UPI and card are checked against the provider counter, which arrives on a different timetable, so a settlement that has not landed yet is not a shortage. Writing it as one is how a good day gets made to look like a bad one.
Cash state at the handover
| Line | Amount (INR) | Basis |
|---|---|---|
| Opening float issued at 14:00 | 3,000.00 | Counted with the incoming shift owner at the changeover |
| Cash sales during the shift | 24,150.00 | The cash line of the payment-mode table above |
| Expected cash in drawer | 27,150.00 | Opening float plus cash sales |
| Counted cash in drawer | 27,090.00 | Second count performed; the same figure twice |
| Cash variance | (60.00) | Short. Cause not identified, so it is left open rather than written off |
Expected in the drawer is 27,150.00 — the 3,000.00 float plus 24,150.00 of cash sales. Counted was 27,090.00, so the variance is a ₹60.00 short. Total collections across the four modes were 1,10,100.00 expected against 1,10,040.00 counted, and the whole business day took 1,74,550.00 across both shifts.
Left open at the handover
| Item | Detail | Owner | What closes it |
|---|---|---|---|
| Cash short of ₹60.00 at close | Counted twice, at 22:08 and 22:12, with the same result. No cause identified. Recorded on this sheet rather than absorbed into the next shift's float. | Sample Shift Manager (example) | The counter tape for 14:00 to 22:00 has been read and the outcome written on this sheet, whichever way it went. |
| One card entry of ₹12,400.00 keyed by hand at 19:48 | Terminal T-04 dropped the network mid-transaction. The customer slip is stapled to this sheet. The card line above is the counter total and has not been checked against the provider's batch. | Sample Shift Lead B (example), outgoing | The entry appears on the provider's batch for 04-10-2026, or the card figure on this sheet is corrected with the reason written down. |
| One promised reservation not yet made: Sample Client Textiles (example) | Told at 20:35 that two bundles would be set aside for collection on the morning of 05-10-2026. Nothing is reserved anywhere, so the promise exists only on this sheet. | Sample Shift Lead A (example), incoming | The goods are reserved before the counter opens, or the customer is called back and told they are not. |
Every open item carries a person, not a department, and carries the condition that closes it. An open item with neither is a complaint waiting for a date, and it is the single most common reason a handover sheet stops being read.
The incoming shift opens from this state
- Cash handed over
- ₹27,090.00 counted — ₹3,000.00 float and ₹24,090.00 of cash sales, ₹60.00 short and unresolved
- Card figure status
- Not confirmed against the provider batch. Treat the card line as provisional until it is.
- First action for the incoming shift
- Reserve the two bundles promised to Sample Client Textiles (example) before 09:00 on 05-10-2026.
- Items left open, each with a named owner
- 3 items — every one of them has a name against it, not a department
- Transactions outside every shift in this business day
- 0. The roster covers 08:00 to 22:00 and the cut-off is 22:00, so nothing fell into a gap.
- Roster gap 22:00 to 08:00
- Closed trading, not an unowned shift. A sale here would be an exception, not a rounding error.
Sign-off
- Outgoing shift owner
- Name / signature / time — Sample Shift Lead B (example)
- Incoming shift owner
- Name / signature / time — Sample Shift Lead A (example)
- Variance reviewed
- Yes / No — and by whom
- Card batch confirmed
- Yes / No — and when
- Open items carried to the next business day
- 3 — listed above, not summarised away
Reading the numbers
- Collections in the business day
- 1,74,550.00
- Collections in the outgoing shift
- 1,10,100.00 expected, 1,10,040.00 counted
- Cash variance
- (60.00) against the transactions of this shift alone
- Shifts in the business day with a named owner
- 2 of 2
- Open items with a named owner
- 3 of 3
- Closing float handed to the next shift
- 27,090.00
Shift handover sheet (CSV — illustrative example data) As on 2026-10-04 Field,Value Location,Sample Retail Counter — Bengaluru (example) Counter / terminal,"Counter 1, terminal T-04 (example)" Business day,"04-10-2026 08:00 to 04-10-2026 22:00 — an interval, not a calendar date" Cut-off for this location,"22:00, fixed — written down as a setting, not held as a habit" Handover,Close of the evening shift S2 to the open of the morning shift S1 on 05-10-2026 Outgoing shift owner,Sample Shift Lead B (example) Incoming shift owner,Sample Shift Lead A (example) Outgoing shift closed at,"22:12 — after the 22:00 cut-off, with the reason recorded below" Incoming shift opened at,"22:14, from the state written on this sheet" Currency,INR Shift,Period,Owner,Hours,Cash (INR),UPI (INR),Card (INR),Bank (INR),Total collections (INR),Sign-off S1,"Morning, 04-10-2026",Sample Shift Lead A (example),08:00 to 14:00,"18,400.00","31,250.00","14,800.00",0.00,"64,450.00",Signed off at 14:08 by the shift owner S2,"Evening, 04-10-2026",Sample Shift Lead B (example),14:00 to 22:00,"24,150.00","48,300.00","31,450.00","6,200.00","1,10,100.00","Signed off at 22:12 by the shift owner, handed to S1 at 22:14" Payment mode,System total (INR),Counted (INR),Variance (INR),Note Cash (sales only),"24,150.00","24,090.00",(60.00),"Cash drawer, counted twice at 22:08 and 22:12" UPI,"48,300.00","48,300.00",0.00,Matches the provider counter for the shift. Settlement is a separate check on a separate timetable Card,"31,450.00","31,450.00",0.00,Counter total only. One hand-keyed entry is not yet confirmed on the provider batch Bank transfer (NEFT / RTGS),"6,200.00","6,200.00",0.00,"Two transfers received after 18:00, both matched to a bill" Total collections for this shift,"1,10,100.00","1,10,040.00",(60.00),"The variance on this line is the cash difference, not a shortfall in takings" Cash reconciliation,Amount (INR),Basis Opening float issued at 14:00,"3,000.00",Counted with the incoming shift owner at the changeover Cash sales during the shift,"24,150.00",The cash line of the payment-mode table above Expected cash in drawer,"27,150.00",Opening float plus cash sales Counted cash in drawer,"27,090.00",Second count performed; the same figure twice Cash variance,(60.00),"Short. Cause not identified, so it is left open rather than written off" Left open at the handover,Detail,Owner,What closes it Cash short of ₹60.00 at close,"Counted twice, at 22:08 and 22:12, with the same result. No cause identified. Recorded on this sheet rather than absorbed into the next shift's float.",Sample Shift Manager (example),"The counter tape for 14:00 to 22:00 has been read and the outcome written on this sheet, whichever way it went." "One card entry of ₹12,400.00 keyed by hand at 19:48",Terminal T-04 dropped the network mid-transaction. The customer slip is stapled to this sheet. The card line above is the counter total and has not been checked against the provider's batch.,"Sample Shift Lead B (example), outgoing","The entry appears on the provider's batch for 04-10-2026, or the card figure on this sheet is corrected with the reason written down." One promised reservation not yet made: Sample Client Textiles (example),"Told at 20:35 that two bundles would be set aside for collection on the morning of 05-10-2026. Nothing is reserved anywhere, so the promise exists only on this sheet.","Sample Shift Lead A (example), incoming","The goods are reserved before the counter opens, or the customer is called back and told they are not." Handover state,Value Cash handed over,"₹27,090.00 counted — ₹3,000.00 float and ₹24,090.00 of cash sales, ₹60.00 short and unresolved" Card figure status,Not confirmed against the provider batch. Treat the card line as provisional until it is. First action for the incoming shift,Reserve the two bundles promised to Sample Client Textiles (example) before 09:00 on 05-10-2026. "Items left open, each with a named owner","3 items — every one of them has a name against it, not a department" Transactions outside every shift in this business day,"0. The roster covers 08:00 to 22:00 and the cut-off is 22:00, so nothing fell into a gap." Roster gap 22:00 to 08:00,"Closed trading, not an unowned shift. A sale here would be an exception, not a rounding error." Sign-off,Value Outgoing shift owner,Name / signature / time — Sample Shift Lead B (example) Incoming shift owner,Name / signature / time — Sample Shift Lead A (example) Variance reviewed,Yes / No — and by whom Card batch confirmed,Yes / No — and when Open items carried to the next business day,"3 — listed above, not summarised away" Reading,Value Collections in the business day,"1,74,550.00" Collections in the outgoing shift,"1,10,100.00 expected, 1,10,040.00 counted" Cash variance,(60.00) against the transactions of this shift alone Shifts in the business day with a named owner,2 of 2 Open items with a named owner,3 of 3 Closing float handed to the next shift,"27,090.00"
The example closes twelve minutes after the cut-off, and the sheet says so rather than hiding it — a shift that ran past its boundary is an event with a reason attached, not an error to be quietly absorbed into the next day. The three open items are the real content of a handover. The cash line is a comparison; what the incoming person cannot reconstruct from the numbers is the whole reason the page exists.
How to fill it in
Four steps, in the order that keeps the count honest and the handover short.
Fix the cut-off once, in writing
Put the boundary in the header block with the date it took effect, so it is a fact two people can read rather than a habit they assume they share. Fixed time of day is the easy version; a rolling cut-off is defensible for a counter that trades overnight, and whichever you choose, the same rule applies to every shift that day.
Open the shift with a named owner and a counted float
The float is counted by two people at the changeover, not written down at the end. A shift that belongs to a shared counter session rather than to one named person cannot support a variance, because there is nobody for the variance to be about. Where staff sign in separately — a PIN rather than a shared login — the attribution means something.
Take the system figures before touching the cash
Read the expected totals for cash, UPI, card, and bank first, then count. Counting first and comparing afterwards invites the number to fit whatever was found. Reconcile each mode against its own reference — the drawer for cash, the provider counter for UPI and card — and mark anything still in transit rather than forcing it to match.
Close against a stated population, then hand over three things
The outgoing owner signs the close against the transactions the sheet names. Then the handover carries exactly three things: the cash state including anything unresolved, the open items with a name against each, and the first action the incoming shift has to take. A handover that hands over a folder instead of three lines will be read once and never again.
When to use this, and when to stop
A handover sheet is the right size of tool for a counter with a fixed roster and two or three people on it. The sign that it has run out is when filling it in takes longer than the changeover it was meant to shorten.
When this template is the right tool
- You run shifts and the handover currently happens as a conversation in the doorway, so whatever the incoming person was not told is simply gone.
- You want the same close whoever was on the counter, so a new person on the till is not left guessing what the last one was dealing with.
- You take cash, UPI, card, and bank and cannot yet say reliably which mode is short on a bad day.
- Your daily figures do not line up with what anybody remembers happening, and you would like a close that somebody who was not there could recompute.
When you have outgrown it
- Producing the expected figures takes longer than counting the cash, because the totals are re-derived by hand from receipts.
- The handover is the same paragraph every day, so it is no longer being read and a late sale or a short would go unnoticed.
- A cash difference surfaces days later, when the cash box or the bank does not agree, and nobody can reconstruct which shift it belonged to.
- You have more than one location trading different hours, and the daily totals are being added together as if the days were the same interval.
The same process in NoxOrigin
The handover is only cheap if the state it hands over already exists, so the point of the system is that the expected figures come from the transactions of the shift rather than from a recount at the end of it: payment mix, discounts, refunds, and overrides are already on the record, and the person closing types in what was actually counted against them. Shifts are opened and closed against a named person through PIN-based staff access, and a transaction that falls outside every shift is held as a visible exception rather than quietly absorbed into the next day. Two limits belong here rather than in a footnote. A shift is a period of trading, not a timesheet: there is no hours-worked record and no payroll module, so if your business bills on time, that requirement is real and this product does not meet it. And the cut-off is a setting agreed at setup rather than a default, because no boundary we could ship would be right for a pharmacy counter and a market wholesaler at the same time.
- Whose hour is it? Shifts and the business dayThe argument behind this sheet: a business day is a recorded cut-off with a named owner, and every figure derived from it is only as good as that boundary.
- Day-end business reportingShifts, payment mix, expected cash, counted cash, variance, and exceptions produced from the transactions of the shift rather than re-keyed at the end of it.
- Day-end closing sheetThe close of the trading day itself, if your handover is the last step before it rather than a substitute for it.
- Cash, UPI and card reconciliation worksheetA wider payment-mode worksheet with a written reason required for every difference, for the days the split gets more complicated than four lines.
- Day-end reconciliation calculatorThe expected-against-counted arithmetic on its own, if all you need tonight is the number.
- Day-end close, in the glossaryWhat a close is, and where a margin or a variance figure stops being trustworthy once the boundary underneath it was never decided.
Shift handover sheet questions
Where should the business day end?
Wherever you decide, written down. A fixed time of day is the common choice and the easiest to explain to everyone who works there. A rolling cut-off — the day ends at the first transaction after a quiet hour — is defensible for a counter that trades all night, but it makes the day's total depend on how busy the day was. Either is fine; what is not fine is the calendar's midnight, which is a default nobody chose. The example uses a fixed 22:00 cut-off at one counter.
What happens to a sale that happens after the cut-off?
It is a real transaction that belongs to no shift, and there are two honest ways to hold it. Give it to the shift that owned that period and reopen that shift's close with a reason and an approval recorded, or carry it as an exception against a named person so the day's total stays complete and the money stays visibly unattributed. What to avoid is the default of letting it slide into the next day, where it inflates a number that is then compared against a drawer count it was never part of.
Why does a cash variance only mean something if the population is right?
Because a variance is expected cash compared with counted cash for a stated set of transactions. Compare the drawer against a calendar day and the number is not a variance at all — it is two different populations subtracted from each other, and it can be non-zero when the drawer is correct. The example closes the evening shift against the evening shift's own transactions, which is why the short is a fact about one person and one period.
Is a shift the same thing as a timesheet?
No, and the difference matters before you build anything on it. A shift here is a period of trading with one named owner, opened and closed with a sign-off, so a sale can be attributed to a person and a period. There is no timesheet record here, no hours-worked record, and no payroll module — attendance, hours, and wages are records kept by a different tool. If your business bills on time, that requirement is real, and this product does not meet it.
Does recording a business day well mean the day reconciles to the bank?
No, and the two are easy to confuse because they sit next to each other. Recording the boundary well makes the close reproducible: somebody who was not there can recompute what it covered from the records. Settlement is a separate exercise — whether the card batch and the UPI settlement have actually landed is checked against the provider, on the provider's timetable, and a business day boundary on its own does not do it. A business day is also an operating convention, not a statutory or filing period; whatever your accountant needs for a return is their determination to make from the records.
Make the business day a cut-off somebody decided.
If nobody who was not on the counter can say what yesterday's close covered, the boundary is currently a memory. That is the part worth fixing.