Eight parks, one morning, one console.
A tier above the parks with its own roles, while every park underneath still runs its own bookings, its own rates and its own folios.
Portfolio dashboard
Month to date across eight parks. Revenue and NOI are limited to owner, admin and finance.
| Park | Occ | ADR | RevPAS | Revenue | NOI |
|---|---|---|---|---|---|
| Pine Hollow OH, 86 sites | 88% | $62 | $54.56 | $140,800 | $52,100 |
| Lakeside Meadows OH, 72 sites | 94% | $58 | $54.52 | $117,800 | $42,400 |
| Cedar Bend MI, 74 sites | 71% | $54 | $38.34 | $85,100 | $24,700 |
| Riverbank MI, 64 sites | 64% | $49 | $31.36 | $60,200 | $12,000 |
| Sandy Cove IN, 70 sites | 100% | $71 | $71.00 | $149,100 | $59,600 |
| Elk Ridge KY, 68 sites | 76% | $57 | $43.32 | $88,400 | $28,300 |
| Harbor Point Marina MI, 64 sites | 83% | $45 | $37.35 | $71,700 | $25,800 |
| Dunes Landing IN, 66 sites | 79% | $66 | $52.14 | $103,200 | $36,100 |
| Portfolio 564 sites | 82% | $59 | $48.24 | $816,300 | $281,000 |
Share your parks' anonymized metrics into the peer comp set to unlock peer benchmarks in return. Your parks are never shown individually to anyone.
Switch the role to Ops and watch the money columns and the ledger disappear.
areas in the console, from the dashboard to corporate settings
org roles, each seeing a different console
chart of accounts across your legal entities
parks that lose control of their own board
The three things a group cannot do with park logins.
Anyone can open eight tabs. The problem is what you cannot see when you do.
Overflow from a sold out park, six miles away.
Central reservations searches every park at once, ranked by fit and by distance, then books through that park’s own system at that park’s own rates onto that park’s own folio.
An agent never has to know which park has a Thursday free. The console answers that before they pick up the phone.
See the grid it books ontoDrag across a few empty nights on any row to take a booking.
A consolidated set of books, not eight exports.
Parks are legal entities under a shared chart of accounts with a single general ledger behind them. Intercompany management fees eliminate on consolidation rather than being backed out in a spreadsheet.
Owner statements and distributions run from the same ledger, and an investor sees only their own stakes in their own portal.
See the books underneathResolve the flagged arrival, then close the day.
One inbox, with a clock on it.
Guest messages from every park land in one queue with assignment and first response timers, so nobody finds out in September that a park stopped answering in July.
Unassigned and overdue have their own queues, and portfolio campaigns respect the same opt outs each park already honours.
See guest messagingTap a quick reply to answer without typing.
Monday morning across eight parks.
What the console tells you before anybody has called you.
Portfolio wide and per park, with revenue per available site beside it.
Against an opt in peer set rather than against your own best park.
A sold out weekend sent to a sister park nine miles away, booked on that park's system.
Down into every park, leaving the overrides a park has deliberately held.
Park override beats org default beats system default, and a compliance view lists who has deviated.
Read only, with intercompany eliminations already applied.
Twenty two things that only exist above the parks.
Everything else stays exactly where your managers already know to find it.
22 things listed right there. Ask about any of them and we will show you it working on your own park, not on a slide.
Owner, admin, finance, ops, viewer and central reservations agents each see a different console. Money columns are owner, admin and finance only.
Central reservations books through each park's own system, priced by that park's own rates, onto that park's own folio.
Dashboard, reservations, inbox, campaigns, rates, guests, financials, owners, team access and corporate settings.
Questions owner groups ask.
Can a park still set its own rates?
Yes. Org rate plans push down into each park, and a park can hold an override that the push leaves alone.
What do investors see?
Their own stakes, statements and distributions in a separate portal. Never the org ledger.
Can we lock a policy across every park?
Corporate settings run park override beats org default beats system default, and any setting can be locked so parks cannot deviate. A compliance view lists who has.