Fake/sample data onlyNo real records, auth UI, uploads, downloads, payment workflows, or real GIS are live yet.

Visit Planning

Visit planning readiness workflow

This page turns visit planning into a practical field-readiness workflow: what should happen before the trip, which conditions or supplies could change the plan, which follow-up items matter afterward, and what stays sample-only until real field data is approved.

Sample workflow only. No real routes, gate details, lock details, family schedules, coordinates, photos, or private trip records are included.

Checklist lanes

4 sample phases

Before, during, after, and follow-up phases stay visible.

sample
Weather watch items

3 placeholders

Conditions affect timing without exposing real trip details.

monitor
Maintenance ties

3 sample tasks

Visit notes can feed later work without becoming a route log.

review
Real access data loaded

0 by design

This PR keeps the workflow field-safe and metadata-only.

do not build yet
Field-planning guardrail

Use this workflow to prepare and follow up, not to store access details

This page should help the owner feel ready for a trip while keeping the sensitive parts out of the app. It stays focused on sample checklist lanes, readiness signals, and safe follow-up actions.

Trip Readiness

Sample readiness lane

Trip-readiness baseline

Sample
Trip readinessHigh priorityBefore visit
Weather / SeasonMonitor
EquipmentReview later
Document NeedMetadata only
Next ActionKeep goals, timing, and checklist scope visible before any real route or access detail is allowed.
Future Supabase Tablevisit_tasks
Workflow Note

Future Supabase path: the first `visit_tasks` rows can stay limited to sample titles, phases, priorities, and next actions.

Sample readiness lane

Field-safety guardrail

Needs owner review
Safety boundaryHigh priorityDuring visit
Weather / SeasonMonitor
EquipmentNeeds owner review
Document NeedMetadata only
Next ActionKeep the workflow useful without turning it into an access guide, coordinate log, or family schedule.
Future Supabase Tablevisit_tasks
Workflow Note

The app can plan a trip without storing sensitive arrival, route, or gate information.

Sample readiness lane

Follow-up capture path

In review
After-visit notesMedium priorityAfter visit
Weather / SeasonReview later
EquipmentSample
Document NeedReview later
Next ActionUse short, safe follow-up items that can later connect to maintenance or conservation boards.
Future Supabase Tablevisit_tasks
Workflow Note

This keeps the future backend connection low-risk while still making visits feel productive.

Visit Checklist

Sample checklist item

Sample visit goal check

Not started
ChecklistHigh priorityBefore visit
Weather / SeasonNo
EquipmentReview later
Document NeedMetadata only
Next ActionWrite down the one question the trip should answer before adding extra field tasks.
Future Supabase Tablevisit_tasks
Sample checklist item

Sample time-window review

Needs owner review
ChecklistMedium priorityBefore visit
Weather / SeasonNo
EquipmentSample
Document NeedNo
Next ActionMatch the sample task list to a realistic trip length so follow-up work stays believable.
Future Supabase Tablevisit_tasks
Sample checklist item

Sample field observation pass

Future task
ChecklistMedium priorityDuring visit
Weather / SeasonYes
EquipmentNeeds owner review
Document NeedReview later
Next ActionKeep observations broad and safe without naming a real boundary, route, or access instruction.
Future Supabase Tablevisit_tasks
Sample checklist item

Sample follow-up note save

Not started
ChecklistHigh priorityAfter visit
Weather / SeasonNo
EquipmentNo
Document NeedMetadata only
Next ActionTurn one useful trip outcome into a later task instead of trying to log everything.
Future Supabase Tablevisit_tasks

Weather & Season Placeholders

Sample condition watch

Sample wet-ground caution

Monitor
Weather / seasonMedium prioritySeasonal placeholder
Weather / SeasonYes
EquipmentReview later
Document NeedNo
Next ActionFlag conditions that could change the trip scope without storing any real site or access detail.
Future Supabase Tablevisit_tasks
Sample condition watch

Sample summer overgrowth watch

Review later
Weather / seasonLow prioritySeasonal placeholder
Weather / SeasonMonitor
EquipmentSample
Document NeedNo
Next ActionKeep seasonal visibility issues visible without turning them into a map or route workflow.
Future Supabase Tablevisit_tasks
Sample condition watch

Sample cold-weather check

Future task
Weather / seasonLow prioritySeasonal placeholder
Weather / SeasonYes
EquipmentNeeds owner review
Document NeedNo
Next ActionUse a placeholder condition check so seasonal prep can stay simple and non-sensitive.
Future Supabase Tablevisit_tasks

Equipment Readiness

Sample equipment lane

Sample field kit list

Review later
EquipmentMedium priorityBefore visit
Weather / SeasonMaybe
EquipmentNeeds owner review
Document NeedNo
Next ActionKeep the list generic and useful without adding personal gear details or family planning notes.
Future Supabase Tablevisit_tasks
Sample equipment lane

Sample phone and battery check

Not started
EquipmentMedium priorityBefore visit
Weather / SeasonNo
EquipmentSample
Document NeedNo
Next ActionMake sure the sample workflow supports a simple readiness check before leaving home.
Future Supabase Tablevisit_tasks
Sample equipment lane

Sample photo capture hold

Needs owner review
EquipmentLow priorityDuring visit
Weather / SeasonMaybe
EquipmentReview later
Document NeedReview later
Next ActionKeep photo-related thinking as a placeholder only, with no real image storage or upload flow.
Future Supabase Tablevisit_tasks

Maintenance Follow-Ups

Sample maintenance follow-up

Sample gate-condition follow-up

Needs owner review
Maintenance taskHigh priorityDuring visit
Weather / SeasonNo
EquipmentNo
Document NeedReview later
Next ActionRecord that a maintenance question exists without storing any gate, lock, or access detail.
Future Supabase Tablevisit_tasks
Sample maintenance follow-up

Sample drainage recheck

Future task
Maintenance taskMedium priorityFollow-up
Weather / SeasonYes
EquipmentNo
Document NeedNo
Next ActionUse a follow-up lane that can later connect to conservation without exposing the real location.
Future Supabase Tablevisit_tasks
Sample maintenance follow-up

Sample repair-question backlog

Review later
Maintenance taskMedium priorityAfter visit
Weather / SeasonNo
EquipmentSample
Document NeedMetadata only
Next ActionKeep repair follow-ups narrow so the visit lane stays practical instead of becoming a full work-order board.
Future Supabase Tablevisit_tasks

Document Needs

Metadata-only placeholder

Sample insurance contact packet

Review later
Document needLow priorityBefore visit
Weather / SeasonNo
EquipmentNo
Document NeedMissing file
Next ActionShow that a document might matter later without pulling real policy details into the trip plan.
Future Supabase Tablevisit_tasks
Metadata-only placeholder

Sample land-record reference hold

Do not build yet
Document needHigh priorityBefore visit
Weather / SeasonNo
EquipmentNo
Document NeedMetadata only
Next ActionKeep any land-record reference blocked until the owner approves real document use separately.
Future Supabase Tablevisit_tasks
Metadata-only placeholder

Sample maintenance note packet

Sample
Document needMedium priorityAfter visit
Weather / SeasonNo
EquipmentNo
Document NeedReview later
Next ActionTreat maintenance paperwork as a later metadata lane, not as an upload step in this PR.
Future Supabase Tablevisit_tasks

Future Supabase Connection Path

visit_tasks

Trip phases, checklist items, weather placeholders, equipment readiness, maintenance follow-ups, document needs, and next actions.

Next Safe Actions

Required

Connect only low-risk visit metadata first

The first backend-linked visit records should be sample titles, phases, priorities, weather flags, and next actions only.

Next Safe Action

Start the future Supabase connection with read-only `visit_tasks` metadata rows.

Do not build yet

Keep trip planning separate from access data

A useful visit workflow should not become a route guide, coordinate log, gate note, or family scheduler.

Next Safe Action

Preserve the privacy boundary even when the UI gets more detailed.

Sample

Link follow-up tasks to other boards later

Visit outcomes may eventually create finance, conservation, or maintenance follow-ups, but this lane should stay lightweight first.

Next Safe Action

Use next actions and document needs as the bridge instead of building cross-board automation yet.

Page sample-data boundary

No real routes, access notes, gate details, lock details, family schedules, coordinates, parcel references, photos, or private visit records are included.