Capture
FR03FR04FR05US02–US04
The camera is the first screen. Take the photo, confirm where it belongs, choose a tag, write a line and save.
- No session to start, ever
- Files itself when the GPS reading is clear
- Asks you when it isn't
HOA common-area inspections · Developer handoff v0.4
Every inspection photo, filed to the right neighborhood.
RoveCheck is a phone-first photo workflow. Set up each neighborhood once, take photos on site without starting a session, and pull together the day's review back at the office.
- Project
- RoveCheck
- Source
- Handoff v0.4
- Dated
- 3 Nov 2026
- Status
- Clickable demo
9:41
This phone works. Press the shutter, confirm the area, pick a tag and save. Everything is simulated, nothing leaves your browser.
The app
Three tabs, one operator
The same people run the agency and do the inspections, so nobody switches roles. Setup, capture and review all sit under three tabs.
Neighborhoods
FR01FR02FR06US01
A name, an optional picture, a solid outer boundary, dotted subareas and the neighborhood's own tags.
- Map shows the boundary and subareas
- History groups photos by tag
- No global archive to dig through
Inspection Generator
FR07US05US06
Pick a day that has photos, then a neighborhood photographed that day, then review its photos by category.
- Only days with saved photos are listed
- One card per neighborhood, never duplicates
- Exclude a photo without deleting it
A field day
From the truck to the report desk
Reporting no longer has to happen before the inspector drives away. Photos are saved one at a time in the field, and the review comes together later by day and neighborhood.
- 01
Set up the neighborhood
Draw the outer boundary and the smaller areas, then choose its tags.
Set one up - 02
Take the photo
Open the app straight to the camera. No session, no report setup.
Field preview - 03
Confirm the place
A clear GPS match files itself. An unclear one asks for the area.
See the five cases - 04
Tag, note, save
Pick the neighborhood's tag and write a line. Time and location are added for you.
See History - 05
Pick the day
Inspection Generator lists only the days that have photos.
Choose a day - 06
Review the set
Check descriptions and categories, and leave out what you don't need.
Open a review
Location filing · FR09 · LC1–LC5
Where does the photo go?
Automatic filing is the default, but GPS is not always precise enough for a pool deck or a mail kiosk. The app says so and lets the inspector choose. It never files to the nearest area by guesswork, and it keeps the original reading next to the choice.
Try each case on the phone
Read the spec, handoff section 10
Every reading in the demo is simulated and labeled that way.
Safeguards
Rules that protect the evidence
Excluding is not deleting
Leaving a photo out of a review only changes that review. The original, its note, time and location stay in the neighborhood's History.
Capture time sets the day
The day comes from when the photo was taken, in the neighborhood's reporting time zone. A late upload never moves a photo to another day.
Reading and choice stay separate
A manual filing is marked manual. The GPS coordinates and accuracy are kept as captured, never rewritten to fit the choice.
Save tells the truth
Each photo shows whether it is on the device, uploading or synced. Tapping Save twice never makes a second copy.
Report output · FR08, later phase
A sample inspection sheet
A completed sheet for Willow Creek Estates on 3 November 2026, built from the same demo photos you can review in Inspection Generator.
- Cover with community, dates and who prepared it
- Summary, condition by category and action items
- Photos grouped by category with observations and actions
- Inspector notes, exclusions and a photo log
A concept for discussion. The handoff keeps report output out of the demo until the owner's template and Brock's example report arrive. This sheet is there to get feedback on content and layout, not to fix the format.
Scope
What this demo proves
The demo shows the interactions. It does not prove live camera, GPS accuracy, storage, sign-in or PDF generation, and it says so on every screen.
In this demo
- Capture, Neighborhoods and Inspection Generator tabs
- Fake photos, simulated GPS and sync, each clearly labeled
- Neighborhood setup with a drawn boundary, dotted subareas and custom tags
- Map and History grouped by tag, with date and area filters
- Manual filing for missing or unclear locations
- Day-first review with include and exclude counts that add up
Later, or not assumed
- Live camera, real GPS accuracy, durable storage, offline sync and sign-in
- PDF generation from the owner's template, with versions and safe retries
- Photo pins, before-and-after comparisons, customer portals and urgent alerts
- No AI tagging, invoicing, bidding, dispatch, public links or app-store release by default
Delivery roadmap
Six stages, no dates yet
Estimates come after the platform, offline scope, location rules and report template are reviewed.
- Stage 1
Update the brief
Review the three tabs, Map and History, manual fallback and day-first review. Confirm tags against Brock's examples.
- Stage 2 This demo
Build the base demo
Capture, Neighborhoods and Inspection Generator with simulated photos and locations.
- Stage 3
Validate production choices
Test camera, location, boundaries, storage, uploads and permission failures on real devices.
- Stage 4
Build the product workflow
Signed-in photo storage, routing, review and report generation once the template is in.
- Stage 5
Pilot real use
Field capture and office reporting with selected operators. Watch corrections and recovery.
- Stage 6
Release and extend
Fix pilot issues, set up support, then decide on pins, comparisons, portals or alerts.
Open decisions
What we still need from the owner
None of these block the demo. They shape the production build.
| ID | Decision | Question | Needed for |
|---|---|---|---|
| D01 | Report template | What content, branding, photo density, observation and action placement, and pagination does Brock's example report set? | Final PDF output |
| D02 | Devices | Which phones, tablets and browsers are supported? Is a responsive website enough for production? | Device testing |
| D03 | Offline scope | Must photos save with no network? How long can they stay on the device? | Capture reliability |
| D04 | Area rules | Can subareas overlap? What happens inside a neighborhood but outside every subarea? | Location routing |
| D05 | Time and dates | Which time zone defines a neighborhood's day? How are wrong device clocks corrected? | Report selection |
| D06 | Text and tags | Which tags replace the provisional four? Are tag and description required? Where do actions go? | Review rules |
| D07 | Access and delivery | Who can see which neighborhoods, and how do PDFs reach the board? | Security and sharing |
| D08 | Retention and capacity | How long are originals, drafts and report versions kept? What photo volumes are expected? | Storage and operations |
| D09 | Pilot approval | Which operators and neighborhoods pilot it, and who signs off? | Release decision |