Bylaw enforcement that follows section 135 every time

Intake that protects everyone

• Residents and staff report a suspected contravention with photos and a truth declaration; the desk can also paste an emailed complaint and deduplicate it.
• Each file gets a BV-#### number and the bylaw or rule it concerns, cited by text, never by a guessed division number.
• Respondent-facing letters never name the complainant.
• Notices go to the unit's registered owner (or their agent), with the tenant copied where the Act requires.

The section 135 ladder, enforced by the software

Before a fine can be imposed, the strata must have received a complaint, given the owner or tenant written particulars and a reasonable opportunity to answer — including a hearing if one is requested — and, for a tenant, notified the landlord. AryaPM will not let a file reach the fine stage until each step is recorded, and it timestamps the response window so nobody argues about dates.

• Stage dates drive sorting: the newest action floats to the top of the council's review desk.
• Council reviews the file, records its decision and the reason, and the decision letter is generated for review before sending.
• Continuing contraventions can be fined at the interval the Act permits, with the schedule visible on the file.
• Fines are recorded on the file and billed through your accounting system; the resident portal never invents a receivable.

Review before anything leaves

Every outbound letter is previewed exactly as it will send, with attachments, before a human confirms it. Files can be corrected or, where a case was opened in error and no money has moved, withdrawn and purged completely.

Ready for the AGM and the CRT

The council decision desk lists files awaiting a decision, files with fines outstanding, and files closed with no action. Each file prints as a PDF report with the complaint, the letters, the dates and the decision — the bundle a strata needs if the matter ever reaches the Civil Resolution Tribunal.