The problem today
Notices are forwarded by email or word of mouth. Owner, deadline and progress do not always sit together.
What the module does
Tasks arise from signals, emails or manual entry and get an owner, deadline and status. Recurring processes are documented as workflows. Knowledge stays in the platform. The module is in testing; access on request.
- Record tasks with an owner in testing.
- Set deadlines for follow-up.
- Make progress visible.
- Link originating notices and emails.
- Document recurring processes in testing.
What it looks like
Review group and rate
| Owner | Deadline | Status |
|---|---|---|
| Revenue team | 26.10.2026 | Open |
What it replaces
To-do lists, chat messages and verbal agreements.
Data sources and integration
Signals and messages from the platform.
Roles and permissions
Visibility follows approved hotels, hotel groups and platform-core roles. Administration manages assignments; commercial works within its approved hotel context.
Frequently asked questions
Is the module available now?
In testing, access on request. The scope described here is being reviewed on staging and may change.
Does the module replace our PMS or RMS?
No. RD030 is the shared work and control layer above them. Decisions and changes take place in the systems approved for them.
Which data may be connected?
Only official APIs, approved data access, report and file imports, and exports you provide.
Status and outlook
In testingIn testing, access on request. The scope described here is being reviewed on staging and may change.
Price
Pricing on request