Requests cross channels
Maintenance details and next actions may be spread across email, calls, portals and existing management software. Confirm this pattern in interviews.
AUSTRALIA · RESEARCH · NOT LAUNCHED
Strata Maintenance
Follow-up.
A research concept for helping strata teams keep maintenance actions visible between request, contractor response and manager decision. It is not launched, not sold in Australia, and not an operational customer-facing SaaS.
Australia — research concept (not launched). There is no strata product, price or customer service in Australia today. This page and the local demonstration exist to test whether the workflow is useful before anything is built or sold.
PROPOSED WORKFLOW
A clearer queue
for the next action.
The workflow is a hypothesis to review with strata managers. Benefits below are expected outcomes to test, not measured results.
Review, assign, chase
A manager classifies a request, sets a due date, follows up with a contractor, records replies and prepares an update for the committee or owners.
Extract and draft
Turn a request into a reviewable task, flag a missed deadline, draft a contractor follow-up and assemble a weekly status report. A manager approves every draft.
HYPOTHESES TO VALIDATE
Potential value,
still unmeasured.
Fewer missed follow-up dates.
Less time rebuilding a weekly status view.
Clearer ownership of the next action.
More consistent contractor chasers.
SYNTHETIC DEMONSTRATION
Request → task → review
The local demo uses fictional buildings, contractors and dates. It extracts tasks, tracks deadlines, flags overdue items, creates contractor follow-up drafts, pauses at manager approval and produces a weekly status report.
All names and records are synthetic · Drafts only · Approval is recorded locally · Nothing is sent
FIT WITH EXISTING SYSTEMS
Start as a small
exception queue.
Existing strata platforms already manage maintenance, quotes and follow-ups. A small companion service may coexist if it handles only an agreed exception queue, fits the team's current process and avoids duplicate entry. That fit is unproven; a first discovery pilot should use synthetic or manually de-identified examples and should not become a second system of record.
Before any live trial: confirm the system owner, data permissions, privacy terms, security controls, export/import method, retention, escalation rules and manager sign-off.
RESEARCH DISCUSSION
Manage strata
maintenance?
If you work in Australian strata management and want to pressure-test this concept, tell us how follow-ups really run today. This is research, not a sales offer.