My LP Portal — loss prevention platform for small business
Official My LP Portal Publication
The Small Business Retail Loss Prevention Audit Manual
GuideFree download

The Small Business Retail Loss Prevention Audit Manual

A Complete Guide to Finding Operational Loss, Preventing Theft, and Building Strong Retail Controls

The complete training manual behind the My LP Portal audit schedule. Ten parts covering why audits exist, the daily/weekly/monthly programs, the ten-step investigation sequence, evidence preservation, coaching conversations, distinguishing theft from operational failure, sustainable program design, a 21-form worksheet library, and a week-by-week 30-day implementation plan. Written for owners who never had a loss prevention department.

My LP Portal
An Official My LP Portal Publication

The Small Business Retail Loss Prevention Audit Manual

A Complete Guide to Finding Operational Loss, Preventing Theft, and Building Strong Retail Controls

Ray Duplechain

Founder, My LP Portal

48 pages · 21 printable worksheets · Free to use, copy, and distribute inside your business

My LP Portal · Audit Manual · Page 1
Contents

What's inside

PartSectionPages
A Letter to Independent Business Owners3
How to use this manual4
IWhy audits exist and what they actually do5–7
IIThe Daily Audit Program8–13
IIIThe Weekly Audit Program14–19
IVThe Monthly Audit Program20–25
VInvestigating Exceptions26–30
VITheft vs. Operational Failure31–34
VIIBuilding a Sustainable Audit System35–37
VIIIThe Worksheet Library (21 forms)38–43
IXThe 30-Day Implementation Plan44
XFrequently Asked Questions45
About the Author46
Why I Built My LP Portal · Meet Collin47
A Final Word48
My LP Portal · Audit Manual · Page 2
From the author

A Letter to Independent Business Owners

Ray Duplechain, Founder of My LP Portal

If you own an independent business, you already know something most people never learn: there is no one else. You are the buyer, the scheduler, the trainer, the customer service department, the maintenance crew, and the person who locks the door at night. Loss prevention is somewhere on that list, usually near the bottom, usually after something has already gone wrong.

I have spent my career on the other side of that equation. Large retailers have entire departments dedicated to protecting inventory and cash — analysts watching exception reports, investigators building cases, auditors running structured programs every single week. You have yourself, and maybe a manager you trust.

That imbalance is the reason most owners do not discover a loss problem until it has already reached their profit. Not because they were careless, but because nothing in their day required anyone to look.

I wrote this manual to change that. Everything in here is practical. It is what I would set up if I walked into your store tomorrow with a clipboard and one week to build a program you could actually keep. Good systems protect a business far better than good reactions ever will — and systems are something you can build starting this week, with the people you already have.

Thank you for spending your time on this. The fact that you are reading a 48-page audit manual tells me you take protecting what you built seriously. You do not need a loss prevention department. You need a routine, a record, and the confidence to act on what you find. That is all in here.

— Ray Duplechain

Founder, My LP Portal

My LP Portal · Audit Manual · Page 3
Orientation

How to use this manual

This manual is built in three layers. Read the training sections once to understand the reasoning. Print the worksheets and put them where the work happens. Then follow the 30-Day Implementation Plan on page 44 rather than trying to launch everything at once.

If you are…Start hereWhy
An owner with no program at allPart II, then the 30-Day PlanDaily controls stop the fastest-moving losses first
An owner with daily routines alreadyPart III and Part IVException review and shrink analysis are where cases are actually found
Facing an active problem right nowPart V, then Part VIOrder of operations protects the case and the innocent
A manager being asked to run auditsPart II–IV plus the Worksheet LibraryEverything you need to execute is in the forms
Multi-locationPart VIIConsistency and verification are the whole game across sites
Best practice
Do not implement more than one new control per week. A program with four controls running for a year outperforms a program with fifteen controls that lasted nineteen days.
A note on tone
Nothing in this manual assumes your employees are dishonest. The overwhelming majority are not. Audits exist to protect them too — a documented record is what clears a good employee when a number goes missing.
My LP Portal · Audit Manual · Page 4
Part I

What an audit actually is

An audit is a scheduled moment where a specific person is required to look at a specific thing and write down what they found. That is the whole definition. It is not an inspection, not a punishment, and not an accusation.

The three functions of an audit

  1. Detection. It surfaces variances while they are still traceable to a date, a shift, and a person.
  2. Deterrence. Opportunity is the one leg of the fraud triangle you fully control. Unpredictable, visible auditing removes it.
  3. Documentation. It creates the record that turns isolated events into a pattern — and protects you legally when you eventually act.

Why owners discover losses late

  • Inventory variance is only measured once a year, so the window is 365 days wide.
  • Cash is reconciled as a store total, hiding offsetting register variances.
  • Receiving is signed rather than counted, so vendor shortages become your shrink.
  • Damage and waste are discarded rather than logged, so they resurface as "theft."
  • Exception data (refunds, voids, discounts) exists in the POS but is never read.
My LP Portal · Audit Manual · Page 5
Part I

The five sources of small business loss

SourceHow it presentsPrimary control
Operational errorBoth overages and shortages, random across staffTraining, simplified procedures, verification
Vendor / receiving lossCategory variance concentrated on delivery daysBlind receiving, invoice reconciliation, vendor scorecards
Administrative errorMargin erosion without unit lossPrice file audits, markdown review, adjustment approvals
Internal theftEscalating, shortage-only, follows a personRandom till audits, exception review, access control
External theftConcentrated on concealable high-value SKUsHigh-risk counts, layout, greeting, camera coverage
Example
A hardware store logged $6,800 of annual shrink in fasteners and assumed employee theft. Cycle counts showed variance in units, not dollars — bulk bins were being sold by the wrong unit of measure at the register. It was a price-file error, corrected in an afternoon.
Warning
Never begin an investigation with a conclusion. The cost of accusing an innocent employee is not just the employee — it is every other employee watching how you handled it.
My LP Portal · Audit Manual · Page 6
Part I

The audit frequency framework

Control areaDailyWeeklyMonthly
Cash / tillOpen count, drops, EOD reconciliation2–4 random mid-shift auditsVariance trend by cashier
ReceivingBlind count every deliveryInvoice-to-inventory reconciliationVendor scorecards
High-risk productRotating 4–10 SKU spot countFull high-risk category countCategory variance analysis
ExceptionsFlag anomalies as they occurRefund / void / discount rankingOutlier trend, policy changes
InventoryOne department cycle countShrink %, variance by category
Store condition / safetyManager walkthroughEquipment and camera checksRepeat-failure review
PeopleRepeat operational failuresTraining gaps, policy compliance
Manager tip
Print this page and tape it inside the manager's office door. Most programs fail because nobody remembers what tier a task belongs to.
My LP Portal · Audit Manual · Page 7
Part II · Daily

Opening procedures and accountability

The opening routine determines whether any later investigation is possible. Every control that follows depends on a clean, attributable starting point.

The opening sequence

  1. Exterior walk before entry — doors, glass, locks, signs of forced entry.
  2. Alarm log reviewed for overnight activity; anomalies documented, not dismissed.
  3. Safe count verified against the prior night's closing figure by two people.
  4. Starting banks counted in front of the receiving cashier; both initial the sheet.
  5. One cashier per drawer, one login per cashier, recorded on the daily sheet.
  6. Back door, compactor area, and stockroom checked before the first delivery.
Warning
Shared drawers are the number one reason provable theft cases collapse. If two people must use one register, the shortage belongs to neither, and you have paid for a control that produces nothing.
Quick win
The two-person opening count takes 90 seconds and permanently eliminates "the drawer was already short."
My LP Portal · Audit Manual · Page 8
Part II · Daily

Cash handling through the day

Non-negotiables

  • Drops at a published threshold — most small formats set $200–$300 per drawer.
  • No cash counted on the sales floor or in camera-blind areas.
  • Every no-sale requires a reason; the POS should force one.
  • Manager overrides require the manager's own credentials, never a shared code.
  • Deposits prepared by one person and verified by a second before leaving the building.
Daily cash signalBenign explanationEscalate when
Small shortage (<$5)Change error, roundingSame operator, three shifts running
OverageFailure to give changeRepeated overages — often masks pre-planned skimming
No-sale spikeChange-making for a food truck rushOccurs in low-traffic hours or without an adjacent sale
Missed dropRush periodConsistent on one shift — sign of drawer manipulation
Example
A grocery owner tracked overages as carefully as shortages and found a cashier averaging $12 in daily overages. She was ringing sales without giving change, then removing the difference before close. Shortage-only monitoring would never have found it.
My LP Portal · Audit Manual · Page 9
Part II · Daily

Receiving at the dock door

Receiving is where inventory becomes real. A shortage accepted here is untraceable later — it will appear as shrink months after the vendor's claim window has closed.

Blind receiving in five steps

  1. Receiver counts without the expected quantity visible.
  2. Count is compared to invoice by a second person or by the system.
  3. Discrepancies noted on the invoice with the driver present and signing.
  4. Photos taken of damage, reseals, short pallets, or substituted items.
  5. Credit request submitted the same day; tracked until resolved.
Receiving red flagWhat it may indicate
Driver in a hurry, urging a fast signatureKnown shortage on the load
Repeated short counts on one vendor or one driverSystemic issue or route-level theft
Resealed or retaped casesProduct removed after packing
Deliveries scheduled during your busiest hourCounting will be skipped — reschedule it
Same employee always receives one vendorRotate. Familiarity plus no oversight is opportunity
My LP Portal · Audit Manual · Page 10
Part II · Daily

High-risk merchandise counts

Ten to twenty SKUs typically account for the majority of theft exposure in a small format. You cannot count the store daily. You can count these.

FormatTypical high-risk SKUs
ConvenienceCigarettes, vapes, energy drinks, phone accessories, lottery
GroceryBaby formula, razors, meat, spirits, pain relief, coffee, batteries
HardwarePower tool batteries, hand tools, copper fittings, work gloves
Farm & feedVet meds, fencing supplies, chainsaw chain, ammunition
SpecialtySmall electronics, cosmetics, collectibles, replacement parts

Counting rules that keep the data honest

  • Rotate which SKUs are counted; never publish the rotation.
  • Expected quantity hidden from the counter until after the count is recorded.
  • Count at varied times — a 4 p.m. count and an 8 a.m. count tell different stories.
  • Record zeroes. A "no variance" entry is data, not wasted effort.
My LP Portal · Audit Manual · Page 11
Part II · Daily

Incidents, damage, and the manager walkthrough

Log everything, especially the small things

Damage, spoilage, shoplifting events (including those where nothing was recovered), safety issues, equipment failures, customer complaints tied to transactions, and any refusal at the register. Each entry needs date, time, location, people involved, dollar value, and a factual narrative.

The ten-minute walkthrough route

  1. Front end — drawer security, register area clutter, bag check discipline.
  2. Sales floor blind corners and any product concentration off-planogram.
  3. Fitting rooms / restrooms — packaging, tags, empty containers.
  4. Back hallway, stockroom staging, and anything sitting near an exit.
  5. Compactor, dumpster, and trash exit — the most-used internal theft route.
  6. Back door status and receiving area order.
Manager tip
Vary the timing, keep the route. A fixed route builds pattern recognition; a fixed time builds a schedule that people work around.
My LP Portal · Audit Manual · Page 12
Part II · Daily

End-of-day reconciliation

  1. Each drawer reconciled independently against its own sales.
  2. Variance recorded by register and by cashier — never blended into a store figure.
  3. Exceptions from the day (voids, no-sales, refunds) printed and attached.
  4. Deposit prepared, verified by a second person, and logged.
  5. Safe counted and signed; figure carried to tomorrow's opening verification.
  6. Closing checklist completed and initialed — alarm, doors, lights, cameras recording.
Common mistake
Reporting "we balanced" from a combined total. A store that nets to zero can contain a $140 overage on one register and a $140 shortage on another — two separate findings hidden by one number.
Best practice
Keep 90 days of daily reconciliation sheets accessible in one place. Investigations almost always require going backwards, and paper stored by month is paper you will actually find.
My LP Portal · Audit Manual · Page 13
Part III · Weekly

Random till audits

The random mid-shift till audit is the single highest-yield control available to a small retailer. It is fast, it is unpredictable, and it produces attributable data.

Procedure

  1. Select the register and time without announcing it. Vary cashier and daypart.
  2. Note the exact time; pull the sales total for that drawer to that moment.
  3. Remove the drawer to a secure counting area — never count on the floor.
  4. Count twice. Record the count before comparing to expected.
  5. Reconcile, record the variance, and return the drawer promptly.
  6. Discuss the result with the cashier the same day, whatever the outcome.
VarianceFirst occurrencePattern (3+ in 30 days)
Under $5Note onlyCoach on counting and change discipline
$5–$25Coach, document, re-audit within 7 daysFormal coaching, increase audit frequency
$25+Document, verify data, review transactionsPreserve evidence and open a structured investigation
Repeated overagesNote and monitorInvestigate — overages are rarely random
Warning
Audit your best cashiers too. A program applied only to suspects is a bias program, and it will not survive scrutiny if it ever leads to a termination.
My LP Portal · Audit Manual · Page 14
Part III · Weekly

Reading exception data

Every POS produces exception data. Almost no independent retailer reads it. Ten minutes a week here finds more than a hundred hours of video review.

ExceptionRank employees byOutlier meaning
RefundsCount, dollars, and % without receiptRefund fraud, returns to gift card, phantom returns
VoidsPost-tender voids specificallyCash removal after a completed sale
No-salesCount per 100 transactionsDrawer access without a sale
Discounts% of own transactions discountedSweethearting, unauthorized employee discount use
Price overridesCount on high-margin SKUsUnder-ringing for known customers
Item deletesDeletes after subtotalMerchandise leaving unpaid inside a real transaction
Best practice
Always compare an employee to peers working the same daypart and department. A closing cashier will legitimately show a different profile than a morning cashier.
My LP Portal · Audit Manual · Page 15
Part III · Weekly

Cycle counts that mean something

A cycle count is a full count of one department or category, performed on a rotation so the entire store is covered each quarter without closing.

  1. Pick the department at the start of the week; count on a varied day.
  2. Count blind — no expected quantities on the sheet.
  3. Recount every variance greater than your threshold before recording it.
  4. Check for receiving errors, misplaced product, and unit-of-measure issues first.
  5. Record the result even when clean; the clean weeks define your baseline.
Variance profileMost likely cause
Many units, low dollarsOperational error, damage, unit-of-measure issue
Few units, high dollarsTargeted theft, internal or external
Variance across whole departmentReceiving or system entry problem
Variance isolated to one shelf/binConcealment location or a specific access point
My LP Portal · Audit Manual · Page 16
Part III · Weekly

Receiving review and inventory adjustments

Weekly receiving reconciliation

  • Match every invoice to a receiving document and to what entered inventory.
  • List open credits by vendor and age; anything over 30 days gets escalated.
  • Note which employee received which vendor — rotate assignments monthly.

Adjustment audit

Pull every manual inventory adjustment for the week. For each: who, why, how much, and who approved it. Adjustments made by the same person who counts, receives, and sells the product represent a complete absence of segregation of duties.

Warning
Unrestricted adjustment rights are the quiet back door of small retail systems. A person who can move product on paper can move product in reality and reconcile the difference themselves.
My LP Portal · Audit Manual · Page 17
Part III · Weekly

Security equipment and camera review

CheckStandardFrequency
Cameras recordingAll channels, verified visuallyWeekly
RetentionMinimum 30 days; know your actual numberWeekly
Register overheadDrawer, scan bed, and hands all visibleWeekly
Back door / receivingFull door swing and staging areaWeekly
Alarm testZones respond; contact list currentMonthly
Safe / key controlCombination changed on staff departureOn event

Fifteen-minute targeted review

Do not watch hours of footage. Pick three moments from the week's data: the largest refund, one late close, and one large delivery. Review those specific timestamps. Data picks the moment; video confirms it.

Warning
Cameras discovered broken during an investigation are worse than no cameras — you managed the store believing you were covered.
My LP Portal · Audit Manual · Page 18
Part III · Weekly

Repeat failures and accountability

Track failures, not just fixes. The finding is never "someone propped the door." The finding is that your workflow requires the door to be propped.

Repeat failureUsual root causeFix
Back door proppedNo doorbell or staging space for deliveriesInstall a bell; create a staging zone
Drops missedThreshold unrealistic for volumeRaise threshold or add a scheduled drop time
Receiving unsignedDeliveries during peak hoursReschedule the delivery window
Damage unloggedLog lives in the office, damage happens on the floorPut the log where the damage occurs
Checklist gaps at closeClosing crew understaffedShorten the list to what actually matters
Manager tip
Run a 30-minute weekly review at the same time each week. One page: variance total, top three exception outliers, cycle count result, receiving discrepancies, open corrective actions.
My LP Portal · Audit Manual · Page 19
Part IV · Monthly

Shrink analysis

MetricFormulaUse
Shrink %(Book − Physical) ÷ Net salesOverall control health
Shrink $ by categoryVariance × costWhere the money actually goes
Unit vs. dollar ratioUnit variance ÷ dollar varianceError vs. targeted theft signal
Known vs. unknownLogged damage/waste ÷ total shrinkDocumentation quality
Shrink per labor hourShrink $ ÷ hours workedNormalizes across seasons and sites

The most revealing number is the known-to-unknown ratio. A store that logs damage, waste, and markdowns well should be able to explain a meaningful share of its shrink. When unknown shrink is 90% of the total, the problem is documentation before it is theft.

Best practice
Compare this month to last month and to the same month last year. Seasonality moves shrink more than most owners expect.
My LP Portal · Audit Manual · Page 20
Part IV · Monthly

Category and department analysis

Rank departments two ways — by shrink dollars and by shrink percentage. The lists will differ, and both matter. Dollars tell you what to work on. Percentage tells you what is broken.

Three questions for your top two departments

  1. Is it losing product? Look at receiving and theft controls.
  2. Is it losing margin? Look at pricing, markdowns, and discounts.
  3. Is it losing accuracy? Look at counting method and system entry.
Example
A farm and feed store showed 4.1% shrink in animal health. Product loss was minimal. The cause was expired inventory pulled from shelves and discarded without a waste entry — a documentation failure that looked exactly like theft on a spreadsheet.
My LP Portal · Audit Manual · Page 21
Part IV · Monthly

Vendor performance

Vendor metricTargetAction when missed
Discrepancy rateUnder 2% of deliveriesPresent documented data to the rep
Credit turnaroundUnder 14 daysEscalate; withhold payment on aged credits
Damage rateUnder 1%Request packaging or handling change
Substitution frequencyOnly when pre-approvedRequire approval before delivery
Driver consistencyDocumented route staffRotate your receiver; increase count scrutiny

Vendors correct for the customers who count. Three months of documented discrepancy data changes both the conversation and the behavior — and the discrepancies that remain get credited instead of absorbed.

My LP Portal · Audit Manual · Page 22
Part IV · Monthly

Training deficiencies and policy compliance

Map every monthly finding to one of three outcomes:

FindingMeaningOwner's action
Policy exists and was followedControl gap in the policy itselfRedesign the control
Policy exists and was not followedAccountability issueCoach, document, verify in 14 days
Policy does not existOwnership gapWrite it, train it, then measure it
Policy exists but nobody can find itFunctionally, it does not existPost it where the task happens

Training record minimums

  • Who was trained, on what, by whom, on what date.
  • Acknowledgement signature for cash handling, refunds, and receiving.
  • Refresher cadence — at minimum annually and after any related incident.
My LP Portal · Audit Manual · Page 23
Part IV · Monthly

Corrective action planning

Every monthly audit ends with no more than three corrective actions. Three completed beat fifteen listed.

ElementRequirement
FindingStated as a fact with a number attached
Root causeProcess, training, policy, or control — not a person
ActionOne specific, observable change
OwnerA named individual, never 'the team'
Due dateWithin 30 days
Verification dateA second date when you re-audit the same control
Common mistake
Closing a corrective action because the task was completed rather than because the metric moved. Verification is a measurement, not a checkbox.
My LP Portal · Audit Manual · Page 24
Part IV · Monthly

Operational trends and the owner's dashboard

Keep five numbers on one running sheet, month after month:

  1. Shrink % (and shrink dollars)
  2. Total cash variance (absolute value, not net)
  3. Receiving discrepancy rate
  4. Exception outlier count
  5. Open corrective actions

Review the line, not the dot. A store improving from 3.1% to 2.4% is being managed well even if the target is 1.5%. A store holding steady at 1.8% for six months has a stable system and can now afford to expand its program.

Best practice
Post the trend, not the individual results, where staff can see it. Teams respond to a shared number; individuals respond badly to public individual scoring.
My LP Portal · Audit Manual · Page 25
Part V · Investigations

The ten-step investigation sequence

  1. Verify the data. Recount, confirm balances, rule out timing and posting errors.
  2. Identify access. Who could have — from schedules, logins, keys, and override rights.
  3. Establish the timeline. Last verified present; first confirmed missing.
  4. Preserve evidence. Export video immediately; save transaction detail and originals.
  5. Review transactions. Full history for the window, not just the flagged items.
  6. Review video against data. Match timestamps to specific transactions.
  7. Interview last. Open questions, two people present, unlocked door, no accusations.
  8. Document objectively. Facts, dates, amounts, sources. No adjectives.
  9. Take corrective action. Always paired with the control change.
  10. Follow up. Re-audit the same control at 14 and 30 days.
Warning
Three mistakes destroy cases: confronting before verifying, letting video overwrite, and documenting conclusions instead of facts.
My LP Portal · Audit Manual · Page 26
Part V · Investigations

Evidence preservation

Evidence typeHow to preserveCommon failure
VideoExport to a separate drive with a hash or copy logRetention overwrites at 14–30 days
Transaction dataExport item-level detail, not summary reportsOnly the summary is saved
PaperworkSecure originals; work from copiesOriginals annotated or lost
Physical itemsPhotograph in place with date and scale, then bag and tagItem handled and returned to stock
StatementsWritten the same day, in the person's own words, signedRecalled from memory a week later
System logsExport login and override history for the windowLogs purge on a shorter cycle than video
Manager tip
Know your actual video retention period today, not during an investigation. Write it on the inside of the office door.
My LP Portal · Audit Manual · Page 27
Part V · Investigations

The interview

Before

  • Facts assembled and written down; you should not be learning during the interview.
  • Two management representatives present; door unlocked; reasonable length.
  • Know your state's requirements and your own policy before you begin.

During

  • Open questions first: "Walk me through how you handle a no-receipt return."
  • Let silence work. Do not fill it.
  • Never accuse, never threaten, never promise leniency or outcomes.
  • Document exact language; avoid paraphrasing anything that matters.

After

  • Written summary the same day, signed and dated by both managers.
  • Decision made on facts and policy — consistently applied across every employee.
  • Control change implemented regardless of the outcome.
Warning
If a case may involve law enforcement, prosecution, or a significant dollar amount, consult counsel before the interview — not after.
My LP Portal · Audit Manual · Page 28
Part V · Investigations

Case walkthrough: the $312 refund pattern

Trigger. Weekly exception review showed one cashier with 41% of no-receipt refunds while working 18% of transactions.

Step 1 — Verify. Report rerun for 90 days. Pattern held across all three months.

Step 2 — Access. Refunds processed under her login only; no shared credentials in use.

Step 3 — Timeline. Pattern began seven weeks after a manager departure removed the second-approval requirement.

Step 4 — Preserve. Nine days of video remained. Exported the same afternoon.

Step 5 — Transactions. 14 refunds averaging $22 with no matching original sale that day.

Step 6 — Video. Refunds processed with no customer present at the counter.

Step 7 — Interview. Facts presented neutrally; admission obtained without accusation.

Outcome. $312 documented over 90 days; restitution agreed; termination consistent with policy.

The real finding
The control gap — a removed approval requirement nobody replaced — mattered more than the individual. Reinstating second approval on no-receipt refunds closed the door permanently.
My LP Portal · Audit Manual · Page 29
Part V · Investigations

Coaching conversations that hold up

Most audit findings end in coaching, not investigation. Coaching done well prevents the escalation that leads to real cases.

StepSay thisNever say this
Open with the fact"Your drawer was $18 short on Tuesday's audit.""We're having a problem with you."
Ask for the process"Walk me through your change routine.""Do you have an explanation?"
Identify the gap"Let's look at where the count breaks down.""You need to be more careful."
Agree on the action"You'll count twice before close, starting today.""Just don't let it happen again."
Set verification"I'll audit again within the week."(no follow-up)
Best practice
Document coaching the same day in the same format every time. Consistent documentation is what makes a later decision defensible — and what proves you gave someone a fair chance.
My LP Portal · Audit Manual · Page 30
Part VI

Distinguishing theft from operational failure

SignalOperational failureTheft
TimingRandom across shifts and peopleClusters on shifts, dates, or one operator
Variance directionOverages and shortages bothShortages only
Product profileBulky, low value, damage-proneSmall, high value, resellable
DocumentationMissing or incompleteComplete and clean — reality does not match
Response to trainingVariance drops and stays downDrops briefly, returns or changes method
SpreadAcross many employees doing the taskFollows one person across tasks
Scale over timeFlat and proportional to volumeEscalating
My LP Portal · Audit Manual · Page 31
Part VI

The six causes, in the order you should rule them out

  1. Poor training — the employee never learned the correct method.
  2. Poor procedures — the correct method does not exist or cannot be followed during a rush.
  3. Vendor shortages — you paid for product that never arrived.
  4. Administrative mistakes — price files, markdowns, unit-of-measure, duplicate receiving.
  5. Employee theft — internal, usually escalating, usually attributable.
  6. External theft — concentrated on concealable, resellable product.

Work them in this order. The first four are more common and cheaper to fix, and ruling them out honestly makes the remaining case dramatically stronger.

The paperwork test
Ask: could I reconstruct exactly what happened from the documents I have? If not, your first finding is documentation, not dishonesty.
My LP Portal · Audit Manual · Page 32
Part VI

Decision tree

QuestionIf yesIf no
Does the variance repeat with the same person present?Treat as a pattern. Preserve data before any conversation.Examine the procedure — the fault follows the task, not the person.
Does a documented procedure exist for this task?Verify compliance; coach and re-verify in 14 days.You found a control gap. Write the procedure first.
Is the paperwork complete and internally consistent?Compare paperwork to physical count and system entry.Documentation is the finding. Restore it, run 30 days, re-evaluate.
Did retraining reduce the variance?Operational cause confirmed. Monitor quarterly.Escalate to a structured investigation.
Is the loss concentrated in concealable high-value SKUs?Consider external theft; review layout and coverage.Consider receiving, pricing, and waste documentation.
My LP Portal · Audit Manual · Page 33
Part VI

What the numbers usually say

Observed patternMost probable causeFirst move
Shrink concentrated in one department, units high, dollars lowWaste and damage not loggedPut the damage log on the floor
Cash variance on one shift onlyCash handling procedure or one operatorRandom till audits on that daypart
Category variance tied to delivery daysReceiving loss or vendor shortageBlind receiving plus vendor scorecard
Margin down with inventory accuratePricing, markdowns, discount abusePrice file and discount exception audit
Escalating shortage on high-value SKUsInternal theftPreserve evidence, then investigate
Shrink up store-wide after a staffing changeTraining and procedure driftRetrain, re-verify, tighten checklists
My LP Portal · Audit Manual · Page 34
Part VII

Designing a program you will keep

  • Consistency beats intensity. Ten minutes, 300 times a year.
  • Documentation is the product. An unrecorded audit did not happen.
  • Accountability runs both ways. Managers audit staff; owners verify managers.
  • Trends, not snapshots. Six months of one metric beats one perfect month.
  • Data must change decisions. Schedules, layouts, vendors, policies, thresholds.
  • Improve the program twice a year. Retire checks that never find anything.
Common mistake
Launching fifteen controls in week one. Program mortality is highest in weeks three and four, and always for the same reason: the program was designed for a slow week.
My LP Portal · Audit Manual · Page 35
Part VII

Segregation of duties in a very small team

Full separation is impossible with four employees. Partial separation is not, and partial is enough to remove most opportunity.

FunctionNever combine withSmall-team workaround
Receiving productEntering inventory adjustmentsOwner approves all adjustments weekly
Counting inventoryOrdering that categoryRotate counters monthly
Processing refundsApproving refundsSecond approval above a set dollar threshold
Preparing depositsReconciling the bankOwner reconciles, always
Voiding transactionsClosing the drawerManager credentials required for post-tender voids
Best practice
Where you cannot separate the duty, add verification. A second set of eyes after the fact is the small-business substitute for segregation before the fact.
My LP Portal · Audit Manual · Page 36
Part VII

Multi-location consistency

  • Identical forms at every site — variation destroys comparability.
  • Same submission deadline weekly; late is a finding of its own.
  • Owner reviews a ranked comparison, not individual site reports.
  • Rotate an unannounced site visit monthly; verify audits were actually performed.
  • Share what the best site does differently — most gaps are practice, not people.
Example
A three-store operator found one location's cash variance running triple the others. The cause was not staff — it was a single register positioned so the drawer sat outside camera coverage. Moving the register solved it in a day.
My LP Portal · Audit Manual · Page 37
Part VIII · Worksheet Library

Daily and Weekly Audit Worksheets

1. Daily Audit Worksheet

One per day. File by month.

Date
Store / location
Opening manager
Closing manager
ControlCompleted byTimeResult / varianceAction
     
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

2. Weekly Audit Worksheet

Completed at the weekly review meeting.

Week ending
Reviewed by
AreaFindingMetricOwnerDue
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date
My LP Portal · Audit Manual · Page 38
Part VIII · Worksheet Library

Monthly, Cash, and Receiving Worksheets

3. Monthly Audit Worksheet

Month
Prepared by
Shrink %
Prior month shrink %
CategoryVariance $Variance unitsProbable causeAction
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

4. Cash Audit Worksheet

Date / time
Register
Cashier
Auditor
DenominationCountExpectedVariance
    
    
    
    
    
    
    
    
Completed by / date
Reviewed by / date

5. Receiving Audit Worksheet

Date
Vendor
Invoice #
Driver
Received by
ItemInvoiced qtyCounted qtyVarianceCredit requested
     
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date
My LP Portal · Audit Manual · Page 39
Part VIII · Worksheet Library

Inventory, High-Risk, and Store Walkthrough

6. Inventory Audit / Cycle Count Worksheet

Date
Department
Counted by
Verified by
SKU / descriptionCountedSystemVarianceRecountCause
      
      
      
      
      
      
      
      
      
Completed by / date
Reviewed by / date

7. High-Risk Merchandise Count Sheet

Rotate SKUs. Do not print expected quantities on the counter's copy.

Date
Time
Counted by
SKUCountExpected (office only)VarianceNotes
     
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

8. Store Walkthrough Sheet

Date / time
Manager
ZoneObservationRiskAction taken
    
    
    
    
    
    
    
    
    
Completed by / date
Reviewed by / date
My LP Portal · Audit Manual · Page 40
Part VIII · Worksheet Library

Incident, Investigation, and Evidence Forms

9. Incident Documentation Worksheet

Date / time
Location
Type
Reported by
Dollar value
Police report #
FactSourceTimeRecorded by
    
    
    
    
    
    
    
Completed by / date
Reviewed by / date

Facts only. No conclusions, characterizations, or opinions.

10. Investigation Checklist

StepCompleted (date)By whomNotes
    
    
    
    
    
    
    
    
    
    
Completed by / date
Reviewed by / date

Steps: verify data · identify access · timeline · preserve evidence · transactions · video · interview · document · corrective action · follow-up.

11. Evidence Collection Form

Case reference
Collected by
Date / time
Storage location
ItemDescriptionSourceChain of custody
    
    
    
    
    
    
    
Completed by / date
Reviewed by / date

12. Interview Preparation Worksheet

Subject
Date planned
Second manager present
Location
Established factSupporting documentQuestion to ask
   
   
   
   
   
   
   
   
Completed by / date
Reviewed by / date
My LP Portal · Audit Manual · Page 41
Part VIII · Worksheet Library

Coaching, Corrective Action, and Review Forms

13. Corrective Action Worksheet

Finding
Root cause
Action owner
Due date
Verification date
Verified result
Completed by / date
Reviewed by / date

14. Manager Review Form

Manager
Period
Reviewed by
Audit typeRequiredCompletedOn time %Findings acted on
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

15. Training Record Form

Employee
Role
Hire date
TopicTrained byDateAcknowledgedRefresher due
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

16. Exception Tracking Log

Period
Prepared by
EmployeeRefundsVoidsNo-salesDiscounts %Outlier?
      
      
      
      
      
      
      
      
      
Completed by / date
Reviewed by / date
My LP Portal · Audit Manual · Page 42
Part VIII · Worksheet Library

Analysis, Planning, and Risk Forms

17. Shrink Analysis Worksheet

Period
Net sales
Shrink $
Shrink %
Prior period %
CategoryBookPhysicalVariance $Known cause $Unknown $
      
      
      
      
      
      
      
      
Completed by / date
Reviewed by / date

18. Vendor Performance Tracker

VendorDeliveriesDiscrepanciesRate %Open credits $Avg days to credit
      
      
      
      
      
      
      
      
      
Completed by / date
Reviewed by / date

19. Operational Trend Tracker

MonthShrink %Cash variance $Receiving disc. %OutliersOpen actions
      
      
      
      
      
      
      
      
      
      
      
      
Completed by / date
Reviewed by / date

20. Annual Audit Planner / Loss Prevention Calendar

Assign each department a cycle-count month and each policy a review month.

MonthCycle count departmentPolicy reviewedTraining scheduledPhysical inventory
     
     
     
     
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

21. Store Risk Assessment

Score each area 1 (weak) to 5 (strong). Anything scoring 3 or below becomes a corrective action.

Risk areaScoreEvidencePriorityAction
     
     
     
     
     
     
     
     
     
     
Completed by / date
Reviewed by / date

Areas: cash controls · receiving · inventory accuracy · high-risk product · refunds and voids · access and keys · camera coverage · training records · documentation · opening and closing.

My LP Portal · Audit Manual · Page 43
Part IX

The 30-Day Implementation Plan

Week 1 — Establish the baseline

  • Complete the Store Risk Assessment (Worksheet 21). Be honest; nobody else sees it.
  • Confirm video retention, camera angles, and who holds keys and override rights.
  • Start the two-person opening safe verification and one-cashier-per-drawer rule.
  • Begin per-register end-of-day reconciliation. Record every variance, however small.

Week 2 — Protect assets in motion

  • Implement blind receiving on every delivery; file invoices the same day.
  • Choose 10 high-risk SKUs; begin rotating daily spot counts.
  • Put the damage and incident log where the work happens, not in the office.
  • Run your first two random till audits — including on your best cashier.

Week 3 — Turn on the pattern layer

  • Pull refund, void, no-sale, and discount data; rank by employee.
  • Run your first cycle count on the department with the highest suspected loss.
  • Verify cameras, retention, and register overhead views.
  • Hold the first 30-minute weekly review meeting. Same day, same time, every week.

Week 4 — Close the loop

  • Complete the first monthly shrink and category analysis.
  • Score every vendor on discrepancy rate and open credits.
  • Write no more than three corrective actions with owners, due dates, and verification dates.
  • Fill in month one of the Operational Trend Tracker and schedule the annual calendar.
Day 31
Change nothing for 60 days. Let the program run until the routine is boring. Boring is the objective — boring means it will survive December.
My LP Portal · Audit Manual · Page 44
Part X

Frequently asked questions

How long should the daily audit take?

15–25 minutes total, split across open, midday, and close. If it takes an hour, it will be abandoned.

Should I tell employees about audits?

Announce the program, never the schedule. Known-but-unpredictable is what removes opportunity.

What is an acceptable shrink percentage?

Benchmarks vary widely by format. Your direction over six months matters more than any published figure.

What if I find a small shortage repeatedly?

Coach first, verify with a re-audit inside seven days, and escalate only when the pattern survives retraining.

Can I review video without cause?

Reviewing your own business footage is generally permissible, but audio recording and certain locations are restricted. Know your state law and your posted policy.

Do I need a POS with exception reporting?

It helps enormously, but a manual tally of refunds and voids by cashier for two weeks will surface the same outliers.

What if my manager resists auditing?

Audit the manager's controls first and frame it as protection. Resistance to documentation is itself a finding worth understanding.

How do I audit when I am not on site?

Require same-day submission of completed forms, verify a random sample in person monthly, and never accept a week of sheets completed at once.

My LP Portal · Audit Manual · Page 45
About the author

Ray Duplechain

Ray Duplechain, Founder of My LP Portal

"Most losses are not mysteries. They are visible in a store's own numbers long before anyone notices. The job is to build a routine that makes someone look."

Ray Duplechain has spent more than two decades working at the intersection of retail loss prevention, criminal investigations, and operational leadership. His career has covered internal theft investigations, organized retail crime, cash and receiving controls, interview and documentation practice, and the design of audit programs that managers can actually sustain during a busy season.

That work began with military service, where he learned that reliable outcomes come from disciplined process rather than individual heroics — a principle that shapes every recommendation in this manual. He carried that approach into investigative work, where cases are won or lost on documentation, evidence handling, and the order in which facts are gathered.

Working directly with store owners and managers, he saw the same pattern repeatedly: independent retailers were losing real money to problems large chains had solved decades earlier, not because owners lacked capability, but because professional loss prevention tools were built and priced for enterprise organizations.

He built My LP Portal to close that gap — combining field-tested loss prevention practice with technology designed specifically for small business realities. He writes and teaches on retail audits, internal theft, receiving controls, and investigations, and he still believes the most valuable thing you can give a store owner is a system simple enough to keep.

My LP Portal · Audit Manual · Page 46
The mission

Why I Built My LP Portal

A large retailer facing a shrink problem opens a case, assigns an analyst, pulls exception data, dispatches an investigator, and implements a corrective action tracked at the district level. An independent retailer facing the same problem has a bad feeling, a spreadsheet, and no time.

I spent years on the enterprise side of that comparison, and then years talking to owners on the other side of it. The gap was never about intelligence or effort. Independent owners understand their business more deeply than any corporate analyst ever will. What they lacked was infrastructure — the boring, essential machinery of scheduled audits, connected records, exception reporting, and follow-up that makes loss visible.

Professional loss prevention tools existed. They cost more than most independent stores could justify, required specialists to operate, and were built around organizational structures that do not exist in a four-employee business.

My LP Portal exists to remove that barrier: professional-grade audits and checklists, incident management, high-risk merchandise tracking, receiving intelligence, loss heat maps, structured training through LP Academy, and AI guidance — in one affordable platform designed for the owner who is also the buyer, the scheduler, and the closer.

You worked too hard building this to lose it a hundred dollars at a time.

My LP Portal · Audit Manual · Page 47
Meet the assistant

Meet Collin — Your AI Loss Prevention Assistant

Collin — AI LP Assistant

Collin is the AI loss prevention assistant built into My LP Portal. He was designed around a simple observation: most owners do not need someone to tell them their store matters — they need a second set of eyes that never gets busy.

  • Documenting incidents — asks the right questions so reports stay factual and complete.
  • Guiding investigations — walks the ten-step sequence in the correct order.
  • Identifying operational risk — flags control gaps before they turn into losses.
  • Supporting inventory work — highlights variance patterns worth counting again.
  • Analyzing trends — surfaces the shift, category, or vendor behind a number.
  • Recommending next steps — practical actions sized for your team.
  • Teaching — connects any question to the right LP Academy lesson.

Collin does not make decisions about your people or your business. He organizes what your data already shows and tells you where to look — which is exactly what an analyst does on the first floor of a corporate loss prevention department.

My LP Portal · Audit Manual · Page 48
Closing

A Final Word

If you take one idea from this manual, make it this: loss prevention is not about distrust. It is about building systems that let honest people succeed.

Every control in this book protects your good employees more than it constrains them. A documented count clears the cashier who did nothing wrong. A blind receiving process protects the stocker from an accusation about a vendor's shortage. A written procedure tells a new hire exactly what "doing it right" looks like on their second day. Ambiguity is what damages teams — not accountability.

You will not implement all of this in a week, and you should not try. Pick the daily controls. Run them until they are boring. Add the weekly layer. Then the monthly. In ninety days you will know things about your business you have never known, and most of what you find will be fixable.

Keep learning. Keep counting. Keep writing it down. And when you want the record kept for you, My LP Portal will be here — not as a sales pitch, but as the next chapter of the same education.

My LP Portal

mylpportal.org · Professional loss prevention for independent retailers

My LP Portal · Audit Manual · Page 49

This manual is provided for educational purposes and does not constitute legal advice. Employment, surveillance, interview, and detention laws vary by state and locality. Consult qualified legal counsel before implementing disciplinary action, conducting investigative interviews, or involving law enforcement.

Want future resources and updates?

Enter your email. Optional — no spam, unsubscribe anytime.

Related resources

Run all of this inside one place

My LP Portal turns these checklists, incident reports, and trackers into a working system — built for small businesses. Free to start.