Annual Management Plan (AMP) Generation
Annual Management Plan (AMP) Generation
Introduced in: v1.0.31
Overview
The Annual Management Plan (AMP) is a statutory document that Owners' Management Companies (OMCs) are required to produce under Section 17 of the Multi-Unit Developments (MUD) Act. It sets out the planned works, budget, insurance arrangements, and compliance objectives for the forthcoming year.
This feature is distinct from the existing annual budget module. While the budget module covers financial allocations, the AMP is a broader statutory artefact that incorporates multiple dimensions of forward planning for a development.
What an AMP Contains
An Annual Management Plan must document the following for the year ahead:
| Section | Description |
|---|---|
| Planned Works | Scheduled maintenance, capital works, and repair programmes |
| Budget | Estimated costs and service charge allocation for planned activities |
| Insurance | Review of current coverage and objectives for the forthcoming year |
| Compliance Objectives | Regulatory and legislative compliance targets and actions |
Legal Context
Under MUD Act Section 17, an OMC has a statutory obligation to prepare an Annual Management Plan. Failure to do so may expose the OMC and its directors to legal risk. This feature ensures the platform can generate and store a compliant AMP artefact for each managed development.
Note: The annual budget module in the platform is a related but separate tool. An AMP references budgetary information but additionally covers insurance, compliance, and planned works in a single statutory document.
Relationship to Other Modules
- Annual Budget Module — Provides the financial data that feeds into the budget section of an AMP, but does not on its own constitute an AMP.
- Compliance Module — Compliance objectives recorded in the platform can be referenced when compiling the compliance section of an AMP.
- Maintenance & Works — Planned works and maintenance schedules form a core section of every AMP.
Status
This feature was identified as a high-severity mission gap — it was listed as in-progress in the platform manifest but had no schema, router, page, or background function implemented. v1.0.31 introduces the foundational implementation.
Further iterations will expand the AMP module with additional capabilities such as templating, owner distribution, and archival.