Condition photos at issue and return

Condition photos at issue and return are dated pictures of the same asset so a later damage argument has a before and after. They sit inside handover evidence; they are not a second packing list. The itemized list of what to issue and recover stays on the employee asset handover checklist. How you link catalog to person stays on how to assign a company asset. Product surface: Dayzen asset management, which includes handover and return photo comparison on people-linked assets. Use that comparison. Do not invent a parallel photo album in chat.

This is operational guidance, not legal advice. What photos prove in a dispute, and what you may recover, may depend on applicable law, contract, policy, or company practice. Verify with your HR and legal or SME team. This page does not tell you to photograph people.

Why a photo is evidence, not decoration

Written condition (“good”, “ok”, “used”) collapses under disagreement. Two people can mean different things by “light wear.” A dated photo of the lid, the screen, the ports, and the charger brick is harder to rewrite. The point is not aesthetics. The point is that issue and return can be compared on the same serial.

Disputes that photos actually reduce in office practice:

• Cracked glass: was it issued cracked, or returned cracked?
• Missing keys, dented corners, peeled coating: present at issue or only at exit?
• Wrong charger or a substitute brick: does return match what left the store?
• “I never got the bag / dongle”: was it in the issue shot?

Photos do not replace serial numbers or acknowledgement. A beautiful picture of the wrong laptop is worse than no picture. Always pair the image with the catalog identifier. Dayzen comparison is useful because it keeps issue and return shots against the assignment, not in a manager’s camera roll.

Photos also do not replace the handover checklist. If you forget the SIM and the badge, pictures of the laptop will not invent those rows. Shoot what you issued; still run the list.

Scope: the device, not the person

Default scope is the asset: body, screen (on and off if useful), ports, accessories that travel with the kit, asset tag if you use one. Do not photograph the employee’s face, workspace with family photos, or ID documents “for completeness” unless a reviewed policy explicitly requires a different practice. Most custody disputes are about plastic and glass, not identity theatre.

If a hand appears in frame holding the device, crop or retake. If a badge photo would show a portrait, photograph the badge number or the reverse if that is what you need to identify the token — not a portrait of the wearer. SIM trays and serial stickers are device evidence. Selfies with the laptop are not.

This is a privacy and dignity choice as well as a records choice. Condition evidence is not a second HR file of people. Store photos in the asset record. Do not dump them into a public channel. Retention should follow your issued records practice; this page does not invent a numbered data-protection duty.

If your policy already forbids personal devices photographing company kit, use a designated capture path (admin desk camera, or the product’s handover photo flow) so you are not collecting random WhatsApp images with no chain of custody.

When to shoot: issue, return, and the rare mid-life shot

Issue. After you confirm the serial, before or as the employee acknowledges. If the box is unopened, you may shoot the sealed box plus the serial label, then a second set after unboxing if accessories must be shown. Unboxing later without photos is how “the charger was never there” starts.

Return. Same angles as issue, same serial in frame or in the filename/record, return date on the assignment. Comparison only works if both sets exist. A return-only gallery proves what arrived back; it does not prove what left.

Mid-life. Optional when you already know the item was damaged in service and you are opening a repair log (see the repair and custody sibling). A dated damage photo helps the repair record. It is not a substitute for naming who holds the device while it sits in a shop. Do not require weekly beauty shots of every laptop; that is surveillance of people by another name. Stick to handover events plus documented incidents.

What “comparison” means in practice

Comparison is looking at issue and return images of the same catalogued item side by side. Dayzen supports that handover/return photo comparison. Operators should actually open it at return, not assume the files exist. A practical return desk:

1. Open the assignment by employee and serial.
2. Confirm the physical serial matches the record.
3. View issue photos.
4. Capture return photos in the same spirit (same sides of the device).
5. Note new damage in the written condition. If none, write that too.
6. Complete return acknowledgement. The checklist still confirms other kit lines.

If issue photos are missing, you cannot honestly “compare.” Write that gap on the return record and start the practice from this issue onward. Do not fake an issue photo from a stock image of the model.

Lighting and focus matter more than camera brand. A sharp, well-lit phone shot of the four corners and the screen beats an artistic blur. Include a paper slip with date and serial in one frame if your desk still does that; the product record date still wins as the system timestamp.

Who captures, who stores

Typical owners:

• Issuer (IT, admin, or HR asset owner) captures issue photos at the handover appointment.
• Return desk captures return photos. Prefer the same function that issued, so angles stay comparable.
• Employee may capture unboxing photos for remote issue if you allow it — still stored on the asset record, still of the device. Give them a short shot list so you do not receive a picture of their cat and a corner of a box.

The employee my-assets portal is where they see assignments. Photo comparison for operators lives with the assignment and handover record. Do not ask employees to email private albums as the only copy.

If a third-party courier delivers, the condition that matters is the condition when the employee first had a chance to inspect — plus any pack photos the courier already requires. Write which set you treat as “issue.” Ambiguous remote issue is a process design problem; photos make it visible, they do not magically create a desk.

What this page must not steal

Do not reprint the handover checklist’s item rows. Do not rewrite the full assignment workflow. Do not turn this into an ITAM imaging guide, MDM compliance photography, or a helpdesk ticket form. Dayzen is not those products. Do not link unpublished helpdesk. Do not claim GPS, barcodes, or automatic damage detection. A human still looks at the two image sets.

Do not use condition photos as a substitute for acknowledgement. A picture of a laptop on a desk does not prove the named employee accepted custody. Pair photos with the assignment event.

A small shot list (devices, not a second checklist)

Shot	Why
Full device, lid closed, tag/serial visible if possible	Identity of the object
Four corners / edges	Dents and cracks people argue about
Screen on, typical desktop or lock screen without personal photos	Panel damage; avoid people in the wallpaper
Ports and hinge	Common wear that “good” hides
Charger, bag, or listed accessories as a group	Kit completeness

Phones, monitors, and tools get the same idea: identity, damage-prone surfaces, accessories. Skip shots that only exist to fill a quota. Five clear images beat twenty duplicates.

Failure modes

Photos in WhatsApp only: the group is gone, the intern left, the evidence left with them. Issue photos of a different serial than the assignment. Return photos in a dark bag so every scratch is invisible. Photographing the employee “holding the asset” as if that were custody law. Using stock marketing images of the model. Comparing across people (“all ThinkPads look like this”) instead of this serial. Skipping photos on day one because the joiner is late, then arguing at exit. Treating photo comparison as the entire handover so badges and keys are forgotten. Uploading faces “for security” without a reviewed policy. Assuming Dayzen will auto-grade damage; comparison is a human look at stored images.

Another failure: keeping photos forever in a personal drive with no link to the assignment. When FNF and recovery start, nobody can find the issue set. Store where the assignment lives.

When the photo work is done

Issue photo work is done when the assignment has dated device images tied to the serial, scoped to the kit, with no unnecessary pictures of people. Return photo work is done when a comparable set exists and someone has actually compared them and written condition. Gaps are dated exceptions (“no issue photos — practice starts now”), not silent omission.

Shoot the device at issue and at return, keep both sets on the assignment, compare them, write what changed. Dayzen has handover/return photo comparison — use it. The checklist still owns the item list. Default: pictures of kit, not of people.

Start on the next issue, not on a historic fleet you never photographed. You cannot backfill honesty. Stop when evidence is on the record — not with a second handover novel or a surveillance programme.