Planner login
Each planner signs in to see only their own groups, contracts, rooming lists and balances.
A customer portal website for boutique hotels gives group planners and corporate clients a secure login for contracts, rooming lists, event orders and deposits. The sales team stops chasing documents by email, and every planner sees the current version.
A group booking account holds activity across a long planning year, with contracts, cutoffs and room lists changing along the way. A corporate retreat planner or an event manager may handle several hotels at once, so an event planner portal keeps their paperwork out of one crowded inbox.
Without an account, each change becomes another email with an attachment. A rooming list sent in the wrong version, or a contract marked signed in one thread and unsigned in another, costs staff time and invites disputes at check-in.
Secure contract sharing keeps the signed agreement, the deposit receipt and the latest rooming list in one place. The planner logs in to see what is confirmed, and the hotel works from the same version.
Rooming lists hold guest names, arrival details and sometimes travel document details for international groups. Keep that data out of general files, limit access to the planner and the named hotel contact, and set a retention period for closed events.
Card payments should go through a hosted processor that is PCI DSS compliant, so the portal stores a receipt rather than card numbers. Where guests live in California or the European Union, privacy laws such as the California Consumer Privacy Act or the GDPR may apply. Card holds for no-show protection can be set per group.
Accessibility applies to the portal too. Planners who use screen readers should be able to read contracts, forms and status messages, and WCAG 2.1 AA is a sensible working standard.
Group business has its own calendar. Contracts go out early, cutoff dates release unused room blocks, and rooming lists arrive closer to the event. The portal should show each of those dates on one timeline the planner can read at a glance.
Between events the portal still earns its keep. It holds the next group's proposal, reminds the planner before each cutoff and keeps past contracts available for the hotel's records. Regular use keeps the account current.
When several groups share one peak weekend, staff need one queue sorted by cutoff date, so the nearest deadline is never buried under a later event. A flag on the dashboard can mark the cutoffs due within the next few days.
Each planner signs in to see only their own groups, contracts, rooming lists and balances.
Proposals and signed agreements are stored with versions, so nobody works from an outdated copy.
Planners upload lists in the hotel's template, and each file is checked before it reaches reservations.
Dates for room block releases and final counts appear on one timeline, with reminders sent in advance.
Payments go through a hosted processor, and each receipt is stored on the group account.
The fee falls within a $300 to $2,200 range and follows scope. The number of planner roles, document types and links to a property management or event system adds build work, and each one is priced before it is built.
Rates, room inventory and event details often live in separate systems, which makes data mapping the longest task. A written plan follows the scoping call and lists which inputs the hotel must supply.
Hold scope by launching with contracts, rooming lists and deposits. Loyalty benefits and planner dashboards can follow later, once the core flow is working well. Keep the owner's contact on every account for urgent issues.
A portal only works if planners log in. Start with the groups already on the books, sending each planner a welcome email that explains what the account shows and how to upload a rooming list.
The sales team should send every contract and proposal through the account rather than as an attachment. Replies belong in the portal too, so the record stays complete. Planners can also see which step is waiting on them.
Run the portal beside the email process for the first events, then stop attaching files once planners are comfortable. Post-launch support covers the questions that appear in that first stretch.
Track how many contracts get signed through the portal and how many days pass between a proposal and a signature. Also count how many rooming lists arrive in the correct template on the first try.
Watch disputes and corrections. Fewer late changes to room blocks and fewer arguments about what was agreed show the record is working.
Ask planners after each event whether the portal made the paperwork easier to follow. Their answers point to the next small improvement.
Not necessarily. The portal sits in front of the systems the hotel already uses, so the team keeps its event and reservation software. Where that software offers a connection we can use it, and where it does not we document the manual step between the two.
The upload checks the file against the hotel's template, flags missing names or dates, and asks the planner to fix them before submission. Reservations sees only checked lists. A planner who uploads a corrected list can see the change history on the account.
Only the planner the group account names and the hotel contacts assigned to it. Access is set by role and checked before launch. Guest details are kept out of general files and removed on the retention schedule.
The fee sits within the $300 to $2,200 range, and the number of roles, document types and property links sets where your project lands. Pricing is agreed in writing once the free scoping call is complete. Post-launch support covers new group types later.
Ask for the free scoping call to go through your group types, documents and cutoffs, with the price agreed in writing first.