HOW AISX WORKS

Keep the context.
Move the work forward.

Clear communication, assigned responsibility and focused escalation help teams reduce avoidable delays, repeat work and the costs of misunderstanding.

COMMUNICATE IN YOUR OWN LANGUAGE

Write in yours.
Read in theirs.

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.

Illustrative two-way translation

One task. Two preferred languages.

A fixed example, not a live translation service.

Manager · balcony checklist

Please check the balcony drain before you leave.

Cleaner · task update

The drain is blocked. I have attached a photo for review.

Show original wording

Manager: Please check the balcony drain before you leave.

Cleaner: El desagüe está bloqueado. He adjuntado una foto para revisar.

Illustrative workflow · features and access vary by rollout stage
Read the video transcript

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

A useful dashboard
for every role.

The shared opening dashboard brings together relevant work across modules. Property and Marine dashboards provide the detail for each asset.

01

Choose people and assets

Create a property, vessel or general team. Select several assets, add members and identify the manager or captain.

02

Assign in either direction

Managers delegate work. Team members can assign an issue upward for review. An assignment asks for action; it does not grant broader access.

03

Keep personal lists personal

Private to-dos stay separate from shared team tasks. Shared work carries an owner, due date, status and attachments.

04

See the right workload

Show due and overdue tasks, approvals and blockers relevant to the signed-in person and their permissions.

05

Record the handover

Track the issue, review, next action and completion so responsibility remains clear across shifts.

06

Protect focus and context

Share the minimum job information needed across teams or businesses. A connected platform does not make everyone’s records public.

Illustrative workflow · features and access vary by rollout stage
Read the video transcript

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

Routine work stays routine.
Exceptions reach the decision-maker.

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.

Task owner + authorised team record

Completed and recorded.

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

The information follows
the job.

These examples explain the intended connected experience. Some steps are available in pilot modules; automation and third-party connections require staged activation.

01

Property → Trade → Hire

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.

02

Crew → Captain → Operations

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.

03

Workforce → Team → Task

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.

04

Quote → Stock → Order list

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.

05

Schedule → People onsite

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.

06

Invoice → Accounting

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.

Illustrative workflow · features and access vary by rollout stage
Read the video transcript

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

Useful when connected.
Clear when a connection is missing.

Supported offline capture, sync status and record history help with patchy reception. The wider resilience and integration programme is still being completed.

01

Offline where supported

Prepare the supported device and workflow before leaving coverage. Check pending changes have synced; not every feature works offline.

02

Backups with recovery checks

External backup and restore verification are part of the resilience plan. No zero-data-loss or uninterrupted-service guarantee is made.

03

Honest integration status

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.

See individual integration status

Make your next connexion.

Tell us about your community, business or team. Start with the tools you need.

Let’s talk AISX

Your next connexion.

Choose a platform. Existing sign-in and account permissions apply.

The apps open on their current hosting domains. This website does not sign you in or grant access.