Rental move in photo dates can conflict when a resident uploads an image days after taking it, an inspection app adds its own timestamp, or two copies show different file details. The manager should preserve each version, identify what the date field represents, and compare the image with other records before relying on it. A file’s displayed date alone does not establish when a condition was photographed.
The National Archives and Records Administration’s digital photo records guidance says federal agencies should preserve and transfer available EXIF information as part of digital photographic records. That is technical guidance for federal records management, not a legal requirement for a private rental file. Its useful lesson here is limited: keep available image metadata with the original file when practical, and do not treat a later export as the only version.
Identify what each date means
A photo can have a capture time embedded in its metadata, a file creation or modification time, an upload time, an email receipt time, and a date entered in an inspection form. Those values may describe different events. A portal timestamp can show when the system received a file, not necessarily when the camera captured it. An email date can show when a message was sent, not the age of an attachment. The manager should label each date by its source.
Mobile devices and cameras may use different time zones or have clocks set incorrectly. A file copied from one system to another may display a new modification time. An image sent through a messaging app may be resized or stripped of some metadata. These differences can create an apparent conflict without showing that anyone changed the underlying photograph. The manager should record the observed values and preserve the original file rather than guessing which one is correct.
When two tenants or staff members provide similar photos, identify which file came from which person and channel. Ask whether the image was captured on the move-in day, copied from an older album, or exported from another platform. Keep the answer as a statement from the source, not as an independently verified capture time unless the file actually supports that conclusion.
Preserve the original before comparing copies
Save the file as received in the authorized property record before renaming, cropping, annotating, compressing, or converting it. Keep the original filename if possible and add a separate descriptive label in the record. If an employee needs to mark a detail or reduce the image for a report, create a working copy and identify it as edited or exported. Do not replace the original with a marked-up image.
Record who supplied the photo, how it arrived, when the office received it, the related unit, and the inspection or report it concerns. Where the management system supports it, preserve the upload receipt and the unmodified image together. The received time is still useful even if it cannot establish the capture date. It shows when the property file acquired that particular copy.
A checksum can help a company verify that a stored original did not change after intake, if the management system already supports that method. It does not prove who took the photo or when. A manager should not add a technical process that employees cannot maintain. A simple source note and readback may be more useful than a hash that no one can interpret during an owner handoff.
Compare each image with other move in records
Use the photo as one item in a larger move-in record. Compare it with the signed condition form, inspection notes, portal submission, email thread, key handoff record, and any other dated material the parties provided. Look for matching room names, visible fixtures, unique marks, or framing that indicates the images show the same area. Similarity can help organize the file, but it does not by itself settle which date is accurate.
Keep a simple comparison table when values differ. List the image filename, person or system that supplied it, the date shown in metadata if available, upload or receipt date, related form entry, and the point that remains unresolved. This lets the owner or reviewer see the conflict without changing the source material. If a signed checklist refers to photos by number or label, preserve that reference alongside the corresponding files.
IRES’s page about move-in and move-out inspections covers condition records around a tenancy. The narrower issue here is whether a photo’s dates and source can be reconciled with the file. An inspection form may provide context, but it should not be edited simply to match an image timestamp that has not been confirmed.
Handle conflicting photo dates neutrally
If an image’s metadata and upload record disagree, preserve both values and explain what each appears to represent. Avoid choosing the date that supports one version of the condition without considering how the file was transferred. A mismatch is a reason to ask a factual question, not proof that the image is inaccurate or that a person acted improperly.
A neutral follow-up can ask when the photo was taken, which device or app created it, whether the original file is still available, and whether another copy was edited or forwarded. Do not demand passwords or access to a personal device. If the sender has the original file, ask them to provide it through the company’s approved channel. Record the request and any response in the same property file.
If the original is not available, state that limitation. The manager can compare the copy with other records and note why the date cannot be confirmed. Do not change the file’s metadata, type a date into the image, or recreate a missing original from a screenshot. A later note may explain the conflict, but it should not make the underlying image appear more certain than it is.
Separate image chronology from the condition question
Two questions often become mixed together: what condition does the photo show, and when was the photo captured? The first may require comparing the visible condition with an inspection or repair record. The second may depend on metadata, a platform receipt, or a sender’s account. Keep the questions distinct so a difference in dates does not erase a useful image and a clear image does not settle an uncertain date.
Use concrete descriptions such as ?image shows a mark near the bedroom window? rather than concluding ?the mark existed at move in? unless the record supports that timing. If a contractor later repairs the area, preserve the before and after images under their respective sources and dates. The condition can change over time; the manager should avoid combining files in a way that obscures that sequence.
The same care applies to a renter’s own documentation. IRES’s article on what renters may document at move in discusses evidence collection from a renter’s perspective. A management file can acknowledge a tenant’s images while recording when the office received them and what date information can or cannot be confirmed. These are related tasks, not interchangeable conclusions.
Keep originals and working copies organized
Store photos in a folder or record tied to the correct property, unit, and tenancy period. Use consistent filenames that identify the room or subject without embedding an unverified capture date as fact. If dates are uncertain, a label such as ?kitchen cabinet image received September 18? is safer than ?kitchen cabinet move in photo September 1.? Keep the original name in the note so an employee can locate the source file.
Separate original files from exported sets prepared for the owner, vendor, or inspection report. A shared folder should identify which copy is original, which was resized, and whether any annotation was added. Limit distribution to people who need the images for the management task, following the company’s privacy procedures. Do not circulate unrelated photos from a resident’s camera roll simply because they were bundled with a requested image.
If the file includes many images, maintain a short index showing each filename, room or item, source, received date, available capture data, and any version relationship. The index lets another employee understand the photo set without opening every file and guessing. When images arrive in several batches, record when each batch came in and what additional context accompanied it.
Use clear handoffs for open discrepancies
If a date conflict remains unresolved when staff hand off the file, state the question plainly: two copies show different dates; the office has the upload timestamp and one image export; the sender has been asked for the original. Assign the next person to review the response or compare a new source. Do not mark the timeline complete merely because the image has been uploaded to the system.
At management onboarding, owners can ask whether incoming inspection photos are stored as originals, how metadata is retained, and how a conflict is recorded. If a former manager provides only a PDF contact sheet, request the original image files and any index or inspection report that links them to a unit. Preserve the received PDF as a separate record rather than treating it as a substitute for files that were never transferred.
A new renter may also receive IRES’s Nevada residency checklist as general move-in information. That checklist serves a different purpose from preserving photo files and their source details. The manager should keep a record of condition evidence in the property system even when a tenant also keeps their own copies.
Questions owners can ask their property manager
Ask how the company records the received date, source, unit, and file version; whether original images are kept; and how edited or exported copies are labeled. Ask what the manager does when a photo date conflicts with an inspection form or portal timestamp. The answer should distinguish the dates the system can verify from the date a sender recalls, and should show how unresolved items remain visible to the owner.
Owners should also ask who can access tenant images, how photos move during a management transfer, and whether a standard handoff includes the index and original files. The owner does not need to decide the meaning of every metadata field. A manager should be able to say what is in the record, what source supports it, and what cannot be confirmed.
These habits help a property file remain useful over time. Original photos, dated receipt records, and neutral notes give the next manager context without forcing them to infer a timeline from a filename. If the dates cannot be reconciled, the record can preserve that uncertainty while the owner obtains any review needed for a later decision.
Do not let exports replace the source file
When the owner requests a packet for review, provide a labeled copy set and keep the originals in the authorized property file. A PDF montage, screenshot, or compressed album can make a group of images easier to read, but its layout may obscure file names and metadata. Keep an index that links each view in the packet to the corresponding original. If an image is cropped to focus on one detail, mark that it is a crop and retain the full frame.
If a vendor or former manager returns images after inspection, store the delivery date and source separately from any date the camera displays. Ask for the original files when practical, and preserve both the delivered set and any later originals. This avoids a common handoff gap where the owner has a visual report but the management file lacks the source images needed to understand how it was assembled.
A clear source trail also helps employees avoid circulating duplicates under different names. If two files are identical or appear to be resized versions, note the relationship instead of deleting one. The manager can keep the file set manageable while retaining enough information to trace which copy came from which person or system.
Owners looking for a managed process for inspections, resident records, and document handoffs can review IRES’s Las Vegas property management services and ask how the team preserves condition photos across a tenancy.