Services

Incident response

When something just happened.

Support for retail owners who just discovered a serious issue and need a clean, neutral record before decisions are made. MarginHero helps organize the facts, evidence, follow-up questions, and control fixes so the situation does not become a messy pile of notes, screenshots, and memory.

What it is for

Preserve the facts, organize the evidence, and make the next decision from a clean record.

When a theft, refund abuse issue, cash shortage, policy violation, inventory problem, or employee-related incident is fresh, the first few steps matter. The goal is not to rush to an accusation. The goal is to capture what is known, identify what is missing, and keep the business record clear enough for HR, insurance, police-report support, or internal follow-up.

Rapid intake

What happened and what is pending

Clarify the timeline, people involved, known facts, business decisions that are coming up, and what evidence has already been collected.

Evidence map

Receipts, video, logs, and notes

Identify the receipts, POS logs, camera timestamps, photos, messages, witness notes, drawer records, inventory records, and policy documents that may matter.

Question prep

Follow-up without winging it

Build neutral follow-up questions for managers or owners to use so conversations stay fact-based and consistent.

Incident summary

A usable written record

Create a structured summary that separates confirmed facts, open questions, evidence locations, timeline notes, and recommended follow-up.

Gap check

What is missing before action

Identify weak spots in the record before the business makes a termination, restitution, insurance, or police-report decision.

Control fixes

Stop the same issue from repeating

Translate the incident into practical controls: manager review rhythm, training, camera checks, refund rules, cash documentation, or inventory follow-up.

Process

How response support works.

  1. Initial intake Review what happened, when it happened, who is involved, and what decisions are pending.
  2. Evidence inventory List the records, files, camera timestamps, POS reports, and statements that may support the incident.
  3. Timeline build Organize the incident into a chronological record with confirmed facts and open questions.
  4. Follow-up questions Prepare neutral questions for managers, witnesses, or involved employees where appropriate.
  5. Documentation packet Produce the incident summary, evidence checklist, missing-item list, and next-step control recommendations.
  6. Document module handoff Where useful, set the store up to use the Incident Vault for future reports and records.
Best fit

Use this when the record needs to hold together.

  • An employee, vendor, or customer incident was just discovered.
  • There may be cash theft, refund abuse, policy violation, or inventory manipulation.
  • The owner has evidence but no organized packet.
  • Camera video, POS logs, receipts, and statements need to be tied together.
  • The business wants to avoid making a decision from scattered notes.
  • The incident exposed a control gap that needs to be fixed immediately.
Boundaries

What this service is not.

  • It is not legal, HR, insurance, tax, or accounting advice.
  • It is not law-enforcement work or private investigation representation.
  • It does not include accusatory interviews or confrontation services.
  • It does not guarantee recovery, prosecution, claim approval, or employment outcomes.
  • It should not be used as the only basis for discipline, termination, or reporting.

How it connects

One incident should improve the system, not just close a file.

Incident Response is designed to feed the Document module. The immediate goal is a clean record. The longer-term goal is a repeatable process for every future incident, with training and controls updated from what the business learned.

Document

Turn the current incident into a structured record and future reporting process.

Train

Push follow-up training where the incident exposed a policy or procedure gap.

Detect

Monitor for related POS exception patterns so repeat behavior is easier to spot.

Next step

Get the facts organized before the record gets messy.

Send a short note with what happened, when it happened, and what evidence you already have. MarginHero will confirm whether Incident Response is the right fit.

Request support