Chapter 06 of 10 · Oversight across members and properties
The Farm Stay console
Running a marketplace means holding a lot of small decisions at once. The console is built around queues and exceptions rather than dashboards nobody acts on: applications waiting, listings incomplete, bookings at risk, campaigns awaiting approval, cases breaching service levels.
Membership lifecycle
From first enquiry to renewal, the membership record carries its category, its units, its documents and its status.
- Applications, checks, approvals and renewals
- Membership categories, unit allowances and fees
- Agreements and required documentation
- Listing and membership status, with clear reasons
- Regional groups, training and events
Listing quality and approvals
The marketplace's credibility depends on the standard of what is published. Quality is scored, visible, and fixed before it goes live, not after a guest complains.
- Property, unit and listing approvals
- Content quality, image standards and data completeness
- Accessibility information required, not optional
- Aging and expiry rules for photos and offers
Booking, marketing and support oversight
Three operational surfaces, one place to see the state of the business each morning.
- Booking volumes, cancellations and exception queues
- Marketing requests, campaign plans and member approvals
- Support cases, service levels and escalations
- Member communications, newsletters and announcements
Access, audit and performance
Not everyone should see everything. Roles are set by what the job needs, and changes to the things that matter are recorded permanently.
- Roles for administrators, marketing, support and regional representatives
- Audit history of who changed a listing, price or policy
- Member and property performance reporting
- Segments for targeted member communication
The design decision
The console works in queues. Each team gets a worklist that empties, with an audit trail, rather than a wall of charts that requires interpretation.