3 sample tasks
Urgent work stays easy to spot without pretending anything is live or time-sensitive.
high
Open Tasks
Open tasks and follow-up queue
This page turns cross-board follow-up into a real action queue: what is urgent, what is blocked, what is ready for owner review, which workflow each task belongs to, and what should happen next before any real property data is introduced.
Sample workflow only. No real property data, routes, coordinates, documents, tax records, payments, family schedules, or private owner details are included.
3 sample holds
Dependencies and approval holds stay visible before the queue grows.
review
3 sample reviews
Owner-review lanes stay distinct from blocked or deferred work.
sample
100% sample
The queue prepares future work without storing any real owner or land details.
do not build yet
Action queue guardrail
Make follow-up work easy to scan without pulling in private operating detail
This queue should help the owner see what is urgent, blocked, review-ready, or later without turning the app into a live reminder system, route log, document vault, tax tracker, or private family planning tool.
Urgent Queue
Urgent task
Needs owner reviewConfirm the safe property summary fields
Property overviewHighproject_tasks
Workflow Note
Related WorkflowProperty OverviewThis keeps the main app entry point aligned before any real property row exists.
Urgent task
In reviewDefine the first safe map-layer metadata labels
Maps / GISHighproject_tasks
Workflow Note
Related WorkflowMapsThis should stay strictly metadata-only and separate from any coordinate or file workflow.
Urgent task
Needs owner reviewSeparate tax readiness from payment handling
Finance / TaxesHighproject_tasks
Workflow Note
Related WorkflowFinance & TaxesThis helps the app stay practical while preserving its sample-only finance boundary.
Blocked Queue
Blocked task
Do not build yetHold hospitality-style revenue ideas outside the near-term queue
RevenueMediumproject_tasks
Workflow Note
Related WorkflowRevenue OpportunitiesThis keeps speculative concepts from crowding out practical next steps.
Blocked task
Blocked pending approvalWait on location-sensitive conservation follow-ups
ConservationMediumproject_tasks
Workflow Note
Related WorkflowConservation & Land HealthA useful queue can still exist without precise ecological or site detail.
Blocked task
Do not build yetDefer private file intake rules for the vault
Document vaultHighproject_tasks
Workflow Note
Related WorkflowDocumentsThis protects the vault from becoming a premature storage workflow.
Ready for Review
Review-ready task
SampleChoose the next revenue lane worth comparing
RevenueMediumproject_tasks
Workflow Note
Related WorkflowRevenue OpportunitiesThis makes the revenue board easier to use as a decision-support tool instead of a brainstorm list.
Review-ready task
Review laterPromote one visit follow-up into the shared queue pattern
Visit planningMediumproject_tasks
Workflow Note
Related WorkflowVisit PlanningThe queue should make field follow-ups easier to track without storing routes or family schedule data.
Review-ready task
Needs owner reviewVerify the map-source packet stays metadata-only
Document vaultMediumproject_tasks
Workflow Note
Related WorkflowDocumentsThis ties the vault and maps workflows together without weakening either safety boundary.
Later Queue
Later task
Future taskAdd a conservation-ready follow-up label set
ConservationLowproject_tasks
Workflow Note
Related WorkflowConservation & Land HealthThis can wait until the queue structure feels stable.
Later task
Future taskCreate one shared task wording pattern for cross-board follow-ups
Property overviewLowproject_tasks
Workflow Note
Related WorkflowProperty OverviewA consistent pattern will make future Supabase reads easier to drop in.
Category Coverage
Property overview
Property Overview
Keep the front door of the app centered on safe summary metadata and clear next actions.
Maps / GISMaps
Keep readiness labels and source questions visible while coordinates, geometry, and private files remain out of scope.
Finance / TaxesFinance & Taxes
Keep due windows, missing items, and review steps clear without drifting into payments or private records.
RevenueRevenue Opportunities
Use the queue to compare practical next-review ideas instead of keeping everything in a flat opportunity list.
ConservationConservation & Land Health
Let stewardship follow-ups stay visible without adding location-sensitive or official assessment detail.
Visit planningVisit Planning
Use visit follow-ups to create useful next steps without storing routes, schedules, or access instructions.
Document vaultDocuments
Keep document-related tasks centered on metadata, missing items, and review gates instead of storage or uploads.
Future Supabase Connection Path
project_tasks
Cross-board task title, category, priority, status, blocker or dependency summary, next action, linked workflow slug, and review-safe task metadata.
Next Safe Actions
Start with one shared task schema later
The first live queue integration should standardize title, category, priority, status, blocker, next action, linked workflow, and review timing.
Next Safe Action
Use read-only `project_tasks` metadata rows before adding any reminders, writes, or automation.
Keep board links simple and explicit
Every task should point back to the workflow where the owner can understand the issue in more context.
Next Safe Action
Preserve one clear related-workflow link on each task card when the static helper becomes a Supabase read.
Hold sensitive operational detail outside the queue
This queue should not become a place for routes, access notes, family scheduling, bank detail, or private owner instructions.
Next Safe Action
Keep the queue focused on sample-only summaries and safe next actions.
Page sample-data boundary
No real property data, routes, coordinates, parcel references, documents, tax records, bank details, payments, family schedules, private owner notes, or sensitive field-access details are included.