Property Inspection

Property Inspection guide

Property Inspection is a free workspace for recording what you inspect. It keeps original JPEG and PNG photos, separate annotations, written observations and reviewed report versions in this browser profile. Ordinary code handles the process; no model interprets your photos or writes assessments.

Open the workspaceHow storage works →

1. Define the property and scope

Start an inspection and enter its title, address, date and inspector. Describe the scope and limitations: which areas were accessible, what you looked at and what you could not inspect. Use a separate inspection for a different property.

Use Add room checklist for neutral prompts covering walls and ceilings, floors, doors and windows, visible fixtures and general condition. The prompts do not constitute a professional inspection standard or establish that these areas are safe. Add, remove or duplicate observations to match the work you actually performed.

2. Record assessments and evidence

Add original JPEG or PNG files to an observation. Open a photo, enter a caption and draw a rectangle or use percentage coordinates. Give each mark a descriptive label. Marks are separate overlays; they never change the original bytes. Reattaching identical bytes reuses the original record.

Screen and PDF images are display copies capped at 1,200 pixels, with a white background. Download an original or export report JSON for full detail. SHA-256 identifies the supplied bytes; it does not prove when, where or by whom the image was captured. Original files may include camera or location metadata.

3. Review a fixed version

Review & save version checks for missing property details, incomplete assessments, missing follow-ups and unexplained coverage gaps. Read every observation and compare it with the original evidence, then enter the reviewer name and review note. These names are self-entered, not authenticated signatures.

A reviewed version keeps its text, captions, overlays and original-photo references. Later draft edits or detached photos do not change it. Copy to draft asks before replacing the current draft. Reviewed versions remain available.

4. Hand over a report or follow-up plan

The full report includes all observations, even if the editor is filtered. Print or save a PDF, export a report JSON containing referenced original photos, or export a CSV with evidence references. Report JSON is a report format; it cannot replace a workspace backup.

The follow-up plan sorts Needs attention items by Urgent, Prompt, Routine, then unset priority. Equal-priority items retain their original observation order and numbers. Not assessed and Not inspected entries appear separately as coverage gaps. A plan with no attention items does not certify a defect-free property.

Draft plans display outstanding review requirements. Reviewed plans use the fixed version even after you edit the draft. Print the plan or download its CSV. The CSV contains attention items and coverage gaps, scope and source labels, plus photo names and hashes. It omits other observations, original bytes, image overlays and draft-validation warnings. Share the full report where that context matters. No repair tracking, assignee verification or automatic reminders are provided.

5. Back up and restore your work

Export backup saves all inspections, drafts, reviewed versions and original photos. Keep a copy in a location you control before clearing browser storage, changing devices or performing a restore. Backups contain sensitive property details and original metadata.

Restoration checks the file structure, photo hashes, byte counts and decoded dimensions, then asks before replacing the whole workspace. Invalid or cancelled imports leave the current workspace intact. Remove unused photos only deletes originals no longer referenced by any draft or reviewed version.

If a save fails or another tab has written a newer workspace, export your current backup first. The unsaved memory draft remains available while the tab is open. Reloading can discard those unsaved edits.

Supported files and limits

Eight inspections, 50 observations per inspection and ten reviewed versions each. Forty original photos totaling 18 MB. Each original must be JPEG or PNG, at most 5 MB, 20 megapixels and 10,000 pixels per side. Each observation supports twelve photos and each photo link twenty annotation rectangles. The full backup limit is 32 MB.

HEIC, animated images, PDFs, video, document imports and automatic defect detection are not supported. There is no cloud sync, account login, public sharing service or payment flow in this preview. Google and direct product accounts, team storage and billing remain future release work.

Return for a reinspection

From a saved version choose Start reinspection. After you confirm the date and inspector, its property, scope, area and component names replace the current draft. Every assessment returns to Not assessed; observations, priorities, recommendations, reasons, evidence notes, photo links and summary are cleared. Preserve unfinished draft work in a backup or version first. Review the copied scope and inspect each area again. Earlier reviewed reports and original photos stay intact. Ten reviewed versions are supported per inspection; start a new inspection after that limit.

Compare recorded versions

Choose Compare with draft from a reviewed version, or Compare with previous version from a later reviewed version. The comparison matches stable observation IDs, even when labels repeat. Added, removed and changed records are shown separately; relative reordering is identified. Text, assessment, priority, follow-up, property/scope, photo captions, hashes and annotations can be compared. Draft review gaps remain visible.

Expand photo evidence for both sides. Display copies show the saved annotations; original image bytes remain unchanged. Text, CSV and JSON downloads contain changes and evidence references without original bytes. Print includes the linked photos. Unchanged observation bodies are omitted; consult both full reports for every finding. A removed record or changed status does not establish a completed repair, cause or safe condition. Reviewer names and dates are author-entered, and hashes do not verify capture time or authenticity.