Small business outsourcing workflow guide
Build a damaged-order photo checklist for a support assistant
A photo checklist that gives a support assistant the right evidence for a damaged-order claim before the packaging disappears.

Decide what the photo must prove
A damaged-order photo should prove three things: which order arrived, what was damaged, and how the package looked when it was opened. Write those three questions at the top of the checklist. A photo that shows only the broken item cannot be matched to a shipment. A photo that shows only the box cannot show the damage.
Ask the assistant to take the photos before the customer discards the packaging. Once the box is gone, the claim becomes a description rather than evidence. If the customer has already thrown it away, record that fact and ask for what remains. The checklist should work even when the ideal evidence is no longer available.
Capture the order label and the damage together
Take one wide photo that includes the shipping label, the box, and the damaged item in the same frame. The label should be readable enough to match the order number. If the label is damaged, photograph the packing slip beside the item. One frame that connects the order to the damage saves several messages later.
Take a second photo close enough to show the damage clearly. Include a ruler or a common object for scale when the size matters. Avoid filters, heavy shadows, and extreme angles. The assistant should check the photo on the screen before the customer leaves or the package is moved.
Take wide and close views
Use one wide view to show the package in its setting and one close view for the damaged area. Add a third photo of any leaking, crushed, or wet packaging. The wide view explains how the box was handled, while the close view supports the specific claim. Both are needed when the carrier and the supplier ask different questions.
Check that the photos are in focus and that the damage is not hidden by glare. If the customer is taking the photos, send a short example rather than a paragraph of instructions. A visual example is faster to follow and produces more consistent images. The assistant should confirm the set is complete before closing the message.
Record the conditions at delivery
Write down who received the package, the time it arrived, and whether anyone signed for it. Note whether the box was left in the rain, on a step, or with a neighbor. These details explain damage that is not visible in a single photo. The delivery record and the photos should tell the same story.
Ask the customer to describe what they saw when they picked up the package. Record their words rather than a summary that fits the claim. If the carrier's tracking says delivered but the customer says otherwise, keep both statements. The assistant should not resolve the conflict alone; the record should preserve it for the owner.
Write the customer message before the claim
Draft the message to the customer before filing the claim so the next step is clear. Tell them what will happen, how long it usually takes, and whether they should keep the packaging. Do not promise a refund or a replacement until the owner or supplier confirms it. A calm message with a real next step prevents a second complaint.
Use the photos to describe the damage in plain language rather than repeating the customer's anger. Include the order number and the date of delivery in the message. If the customer needs the item urgently, offer the approved urgent path if one exists. The message should leave the customer knowing who will contact them next.
Store the evidence with the order record
Save the photos and the customer message in the same place as the order record. Use a file name that includes the order number and the date, not a camera default. Record who took the photos and when they were added. Evidence stored in a personal phone is not available to the next shift.
Keep the original images rather than a compressed copy sent through chat. If the customer sends photos by message, download them at full size and keep the original message. Record the source of each image. A later reviewer should be able to tell which photos came from the customer and which were taken by the team.
Set a same-day deadline for the claim
File the claim within one business day of receiving the evidence. Carriers and suppliers often have short windows, and a late claim weakens the business's position. Put the deadline on the queue item when the photos arrive, not when someone remembers. The assistant should know which claims are due before the end of the day.
If a document is missing, file the claim with a note and add the missing item when it arrives. Do not hold the entire claim for a perfect packet. Record the date the claim was filed and the reference number. The queue should show the claim's status separately from the customer's status.
Review claims that were rejected
When a claim is rejected, read the reason before writing to the customer. Record whether the problem was the photo, the timing, the packaging, or the supplier's rule. Update the checklist with the specific evidence that would have changed the result. A rejection is useful only if it improves the next claim.
Share the lesson with the assistant in one sentence rather than a long review. If the same rejection appears twice, change the customer instructions or the carrier. Keep the rejected claim with the order record so the pattern is visible. The checklist should get shorter as the team learns what actually matters.
Sources and next steps
- Federal Trade Commission, business guidance
- U.S. Small Business Administration, manage your business
- IRS, recordkeeping for small businesses
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.
Related guides
Write a reimbursement request path a small-business assistant can follow
A reimbursement path that captures the receipt, the business purpose, and the approval before a small expense turns into a month-end argument.
Write a knowledge-base update note when a policy changes
A one-screen update note that tells a support assistant which pages, macros, and saved replies changed and what to use instead.