STRATABOT / MANAGED STRATA OPERATIONS

Stratabot.
One platform for the whole strata.

Documents, maintenance, council issues, resident requests, announcements, voting, compliance, registry, amenities, fees, and cited answers—inside one private, modular operating system.

AVAILABLE TODAY11 modules
CONFIGURATIONEnable only what fits
ACCESSResident · council · manager
OPERATORBuilt and operated by 1730
THE OPERATING RECORD

Council work should not disappear into inboxes.

A strata is a building, a corporation, a council, a resident community, and a long-lived record—all at once. Generic file sharing or a collection of single-purpose portals only covers fragments.

Stratabot connects the record to the work: a resident report can become a council issue; an issue can carry steps, decisions, and engineering records; a deadline can stay visible; and the next council can inherit the full history.

RECORDS01

From incoming file to usable record.

Email or upload minutes, bylaws, reports, drawings, and correspondence. Review the classification, set the audience, file it, and find it again by full-text search.

COUNCIL WORK02

From report to accountable resolution.

Residents report a problem in a structured form. Council triages it, promotes it to an issue, adds steps and owners, links the relevant records, and keeps the decision trail.

COMMUNITY03

One dependable resident front door.

Publish announcements, gather responses, run ballots, receive maintenance reports, share permitted documents, and coordinate amenities without rebuilding the audience each time.

OPERATIONS04

Recurring obligations stay in view.

Bring compliance dates, asset assignments, contractors, bookings, fees, levies, and unit balances into the same corporation-scoped system as the records behind them.

THE MODULE CATALOGUE

Enable what your strata needs. Leave the rest off.

The core organization, buildings, units, people, memberships, and audit record are always present. Every other capability is a real module with its own routes, data, permissions, and interface.

Records01

Document Vault

Forward or upload records, review the filing, control the audience, and search the full text later.

Council02

Issues

Move leaks, repairs, claims, disputes, and governance work through steps, owners, linked records, and a timeline.

Residents03

Maintenance & Reports

Give residents a structured way to report problems; council can triage a report into a tracked issue.

Residents04

Requests & Polls

Collect leak details, surveys, RSVPs, acknowledgements, and other structured responses in one place.

Residents05

Announcements

Publish and pin notices from council or management without relying on a long reply-all thread.

Governance06

Voting & AGM

Run resolutions and polls with one ballot per strata lot, live quorum, and electronic ballots.

Council07

Compliance Calendar

Track recurring AGM windows, depreciation reports, insurance renewals, and other due-date workflows.

Operations08

Registry

Know who has each parking stall, storage locker, fob, or key, alongside the contractor directory.

Residents09

Amenity Booking

Manage overlap-free reservations for shared spaces, guest suites, EV chargers, and other amenities.

Finance10

Fees & Levies

Track unit fees, charges, levies, payments, balances, and a simple annual operating budget.

Records11

AI Concierge

Optionally answer questions from the strata’s own permitted documents, with citations back to the record.

ACCESS & PRIVACY

One corporation. Different views.

Residents should not see council-only records. A council member should not need an administrator’s interface. A manager can work across the modules the corporation enables. Stratabot resolves the membership first, then the role, then the permitted module and record audience.

RESIDENTCOUNCILMANAGERADMIN
01

Separated by corporation

Every organization route checks membership, and every domain record belongs to its strata corporation.

02

Role-based by design

Resident, council, manager, and administrative capabilities are explicit—not hidden by convention.

03

Auditable changes

Mutations create an audit event so the operating record includes who changed what and when.

04

Private data stays private

Personal information is structurally separated, and the public edge serves the application—not resident data.

PRACTICAL ONBOARDING

Start with the workflow that hurts.

A council does not have to replace every process on day one. 1730 helps establish the corporation, roles, modules, and initial records around a real operating need.

  1. 01

    Choose the first operating problem

    Document retrieval, maintenance intake, an active issue, compliance dates, resident requests, or another concrete workflow.

  2. 02

    Configure the corporation and access

    Set up buildings, units, members, roles, audiences, and only the modules needed for the first release.

  3. 03

    Bring across the useful record

    Load the records that matter, review the filing, and connect them to current work instead of importing clutter blindly.

  4. 04

    Operate, learn, and add modules

    Use the workflow with council and residents, improve the handoff, and enable more of the platform when it earns its place.

WHO IT IS FOR

Built for the people carrying the record.

SELF-MANAGED STRATAS

Give volunteer councils continuity.

Keep the corporation’s record and active work in the system instead of in one council member’s inbox, drive, or memory.

MANAGER-SUPPORTED STRATAS

Give everyone one operating view.

Connect council context, resident workflows, records, dates, and decisions while keeping professional roles and permissions clear.

COMMON QUESTIONS

Before the walkthrough.

What does the Stratabot platform include?+

A core corporation, building, unit, people, membership, and audit layer sits underneath 11 available modules. A strata enables only the modules it needs; disabled modules disappear from the interface and their routes are unavailable.

Does Stratabot replace a strata manager?+

No. Stratabot is operating software for councils, residents, and strata managers. It organizes records and workflows; it does not replace licensed property-management, legal, engineering, or accounting advice.

Can a self-managed strata use it?+

Yes. The product is designed so a council can start with the modules it actually needs, while a manager role is available when a professional manager is involved.

What happens to private council records?+

Every corporation is separated in the platform. Membership and role checks control access, document audiences can be limited to council, owners, or all members, and mutations are written to an audit trail.

Does the AI concierge make council decisions?+

No. It retrieves answers from the strata’s own permitted records and cites the underlying documents. It is an evidence tool for people, not an autonomous decision-maker.

Can we begin with only documents or issue tracking?+

Yes. Stratabot is modular. A practical onboarding can start with one high-friction workflow and add other modules after the council is comfortable.

What can residents do in Stratabot?+

Their view depends on the modules and permissions the corporation enables. It can include announcements, maintenance reports, requests, documents intended for members, voting, amenity bookings, balances, and cited answers from permitted records.

PRODUCT WALKTHROUGH

See your own council inside it.

Tell us where the record or workflow breaks today. We will show the relevant Stratabot modules and outline a practical first onboarding—without forcing a full-platform rollout.

Already a client? Sign in at stratabot.ca ↗
One sentence is enoughCurrent state · desired outcome · timing

A senior practitioner will reply directly.