| Client information is spread across systems, spreadsheets, inboxes and paper records, making it difficult to maintain a complete and current view of each person. | Centralised client and participant record | Must Have | ☐ | ☐ | ✔ | MYP provides a single client record connecting contacts, relationships, services, tasks, documents, goals, schedules, forms, opportunities, and history. Teams can access the information they need from one central profile rather than working across disconnected systems. |
| Staff may have access to information beyond what is required for their role, increasing privacy and information-governance risk. | Role-based access and permissions | Must Have | ☐ | ☐ | ✔ | Role-based permissions control who can view, add or update client information. Access can be aligned with staff responsibilities so sensitive records remain available only to authorised users. |
| Enquiries and referrals are captured inconsistently, making it difficult to track follow-up, eligibility, waitlists, conversion and referral outcomes. | Enquiry, referral and prospective client management | Must Have | ☐ | ☐ | ✔ | MYP captures enquiries and referrals as prospective client records and opportunities. Website and digital forms can feed information into a structured pipeline, helping teams manage follow-up, monitor waitlists and track conversion from initial enquiry through to service commencement. |
| Quoting, funding allocation and proposed service schedules are often prepared separately, creating duplication and inconsistencies before services commence. | Quote, budget and Schedule of Supports management | Must Have | ☐ | ☐ | ✔ | MYP connects quotes, budgets and the proposed Schedule of Supports/Service Plans within the client engagement. Teams can prepare and send quotes directly from the platform, then carry the agreed services and funding arrangements forward into service delivery. |
| Service agreements are manually prepared, emailed and stored, with limited visibility of whether the services delivered remain aligned with what was agreed. | Digital service agreement generation and signatures | Must Have | ☐ | ☐ | ✔ | Approved engagements can be converted into service agreements and issued electronically for review and signature. The agreement remains connected to the client record, care planning, rostering, funding and service delivery workflows, helping ensure that what was agreed is reflected in what is delivered. |
| Providers operating across several programs must manage different funding arrangements, terminology, reporting requirements and service rules. | Multi-program and multi-funding support | Must Have | ☐ | ☐ | ✔ | MYP supports the management of services across programs including the NDIS, Support at Home, CHSP and other funded or privately delivered services. Funding information remains connected to the relevant client, service and financial workflows. |
| Care and support plans are stored as static documents, making them difficult to update, monitor and use in day-to-day service delivery. | Structured digital care and support plans | Must Have | ☐ | ☐ | ✔ | MYP uses structured digital forms to capture care plans, support plans, assessments and other client-specific information. Records can be reviewed and updated as needs change, with relevant information available to support operational service delivery. |
| Case notes are entered late, stored inconsistently or disconnected from the service delivered, limiting oversight and evidence of care. | Point-of-care case notes | Must Have | ☐ | ☐ | ✔ | Staff can record case notes against the client and relevant service activity, creating a real-time care record from the point of service delivery through to the office. This supports proof of service, continuity of care, incident follow-up and early identification of emerging risks. |
| Goals are documented but not consistently connected to services, progress or measurable client outcomes. | Goals and outcomes tracking | Must Have | ☐ | ☐ | ✔ | Client goals and objectives are maintained within the participant record and connected to the services being delivered. Progress can be documented over time, giving teams greater visibility of how supports contribute to intended outcomes. |
| Frontline workers do not always receive current information about client needs, preferences, risks or support requirements before delivering a service. | Client information connected to frontline service delivery | Must Have | ☐ | ☐ | ✔ | Relevant client information flows into frontline service delivery workflows so workers can understand the person’s needs, goals, preferences and support requirements at the point of care. This reduces reliance on separate handovers and disconnected records. |
| Service, communication and support history is fragmented, making it difficult to understand previous activity or respond consistently. | Complete client and participant history | Must Have | ☐ | ☐ | ✔ | MYP maintains a connected history of services, notes, communications, documents, forms, tasks and changes within the client record. Authorised staff can review previous activity without searching across multiple systems. |
| Care plans, service agreements and supporting records are stored in separate drives or folders, creating version-control and retrieval issues. | Client document and version management | Must Have | ☐ | ☐ | ✔ | Client documents, including care plans, support plans and service agreements, can be stored against the relevant client record. Version and change history helps teams identify the current document while maintaining an auditable record of previous updates. |
| Emails, SMS messages and other communications are managed outside the client record, leaving an incomplete history of interactions. | Client communication tools and history | Should Have | ☐ | ☐ | ✔ | MYP supports email, SMS and broader communication being shared from the platform, with activity retained against the client record. This provides teams with a clearer history of interactions and reduces communication being isolated in individual staff inboxes. |
| Follow-ups, reviews and administrative actions rely on staff remembering dates or maintaining separate task lists. | Workflow automation, reminders and task management | Must Have | ☐ | ☐ | ✔ | Tasks, reminders and workflow actions can be connected to client records and operational processes. This supports consistent follow-up for reviews, missing information, expiring documents, service actions and other time-sensitive activities. |
| Providers lack timely visibility of budget usage, increasing the risk of overspend, underspend or services continuing without sufficient available funding. | Real-time client budget and utilisation monitoring | Must Have | ☐ | ☐ | ✔ | Client funding is connected to budgets, planned services, actual service delivery, invoicing and claiming workflows. Teams can monitor utilisation and remaining funding to support more informed service planning and earlier intervention when usage moves outside expectations. |