Choose people and assets
Create a property, vessel or general team. Select several assets, add members and identify the manager or captain.
HOW AISX WORKS
Clear communication, assigned responsibility and focused escalation help teams reduce avoidable delays, repeat work and the costs of misunderstanding.
COMMUNICATE IN YOUR OWN LANGUAGE
A manager’s English task can be shown in Spanish; the cleaner’s Spanish reply can come back in English. Names, photos, asset links and the original message remain part of the record.
A fixed example, not a live translation service.
Clear work starts with clear communication. The AISX multilingual workflow is designed to let each person use their preferred supported language. A cleaning manager writes, please check the balcony drain before you leave. A Spanish speaking cleaner reads that instruction in Spanish, then replies in Spanish with a photo of a blockage. The manager receives the update in English, attached to the same task and property. The original wording stays available, so a translation can be checked. Checklists, task notes and supported messages share the context, reducing the need to retype instructions into a separate translation app. Language coverage depends on the connected translation service, and important instructions still need acknowledgement. The aim is fewer misunderstandings, less repeat work and more consistent quality. Translation is being rolled out across supported workflows.
Rolling out across supported checklists, task notes and messaging. Language coverage is provider-dependent; “all languages” is not guaranteed. Translation supports communication and does not replace review of safety-critical or contractual instructions.
TEAMS & TASKS
The shared opening dashboard brings together relevant work across modules. Property and Marine dashboards provide the detail for each asset.
Create a property, vessel or general team. Select several assets, add members and identify the manager or captain.
Managers delegate work. Team members can assign an issue upward for review. An assignment asks for action; it does not grant broader access.
Private to-dos stay separate from shared team tasks. Shared work carries an owner, due date, status and attachments.
Show due and overdue tasks, approvals and blockers relevant to the signed-in person and their permissions.
Track the issue, review, next action and completion so responsibility remains clear across shifts.
Share the minimum job information needed across teams or businesses. A connected platform does not make everyone’s records public.
A busy team needs clear responsibility. In AISX, teams can be organised around properties, vessels, or a mixture of assets. Give each task an owner, a due date and the context needed to complete it. Personal lists keep private reminders separate from shared team work. Relevant tasks appear in the person's dashboard, while managers retain the oversight their role allows. A routine completion stays in the job history. A blocked task or approval request goes to the nominated manager. For a vessel, that might be a deckhand flagging an issue to the captain, who then assigns a decision to operations. For a property, a cleaner can raise an issue to the property manager. The escalation workflow is designed to surface the exceptions that need action, with a recorded handover and outcome. Less notification noise. Clearer accountability. Fewer missed details. Availability depends on the module and rollout stage.
ESCALATION WITH A PURPOSE
Route a cleaner’s issue to the property manager, or a deckhand’s flag to the captain. The next escalation reaches operations when the rule or decision requires it.
A completed routine check stays with the asset and task history. It does not need a new alert to every manager.
Example rule: record completion; include it in the relevant summary.
Illustrative rules. Actual recipients, urgency and escalation timing must be configured for each organisation. Managers retain authorised oversight.
CROSS-MODULE EXAMPLES
These examples explain the intended connected experience. Some steps are available in pilot modules; automation and third-party connections require staged activation.
An inspection identifies a repair. A manager reviews photos and scope, starts a trade request and arranges equipment separately. Completion evidence returns to the authorised asset record.
Role-based checklists help deckhands, hosts and guides report their part of the day. A captain reviews flags and passes spending or operational decisions to management.
Find a worker by skills and availability. After hiring and access checks, assign them to a team and the properties or vessels they will work on.
Planned business tools reserve available stock on approval, show shortages by job, and record actual use or release. A reservation reduces available stock; physical stock changes when issued or consumed.
The planned onsite view combines authorised schedules and manual attendance updates. Relevant cleaners and maintenance workers can coordinate directly. It is not live location tracking.
The MYOB roadmap includes invoices, supporting job receipts and mapped accounts. Labour sales and material sales remain income; material purchases/costs are mapped separately, with review and duplicate checks.
One issue can involve several parts of a business. AISX is designed to keep the context connected. A property inspection identifies a repair. The manager reviews the photos, agrees the scope, and assigns the next step. Trade workflows bring the brief, quote and job conversation together. Hire can help arrange the equipment required, with availability and booking confirmed separately. In the business roadmap, approved quotes reserve stock for a job, shortages become an order list, and actual use records what left the shelf. On the water, crew checklists and captain flags support vessel maintenance and handovers. Supported calendars help teams plan around guests and departures. Planned accounting connections aim to carry invoices and supporting receipts into the right accounts after mapping and review. These are connected workflow examples, not a promise that every integration is active. The result we are building towards is less duplicate entry and a clearer path from issue to completion.
CONNECTIONS & CONTINUITY
Supported offline capture, sync status and record history help with patchy reception. The wider resilience and integration programme is still being completed.
Prepare the supported device and workflow before leaving coverage. Check pending changes have synced; not every feature works offline.
External backup and restore verification are part of the resilience plan. No zero-data-loss or uninterrupted-service guarantee is made.
Calendar feeds, payments and existing AIS workflows have different setup requirements. MYOB, Deputy and broader automation are roadmap items until a live connection is verified.
Tell us about your community, business or team. Start with the tools you need.