# About Service Agreements
A **Service Agreement** is the written agreement between your Organisation and a Client about the supports you will deliver. In Comm.care it is the record of what was agreed: which services, for how long, funded by whom and with what budget.
Create one for each Circle, for each funding source. A Client can have more than one, including several for the same funding source.
> **Roadmap is now Service Agreement.** Service Agreements replace the Roadmap. Your existing Roadmaps have been moved across for you. See [What changed: Roadmaps are now Service Agreements](roadmaps-are-now-service-agreements.md).
## What a Service Agreement contains
- **Agreement details:** a name, the funding source, the **From** and **To** dates, and a state (**Plan**, **Active** or **Inactive**). A new agreement starts as **Active**.
- **Budgets:** one or more **Buckets**. Each Bucket is one budget, such as Core. NDIS Buckets can have **Funding Periods** with their own dates and budgets.
- **Services:** the supports you deliver, each in one Bucket. Each Service carries its own claim settings, such as **Paid by** and travel for NDIS.
- **Claims:** who receives the claim emails for each payer (**Claim Recipient** and **Claim CC**). You set them once per payer in the **Claims** section, and every Service with that payer shares them.
- **Funding source details:** extra information the funding source needs, such as DSS clients and Outlet Activities, or the MDS referral source.
- **Renewal reminder:** an optional reminder before the agreement ends.
Comm.care uses it in several places. Progress notes draw down the budget of the Bucket their Service is in. It also feeds claims, reports and DEX submissions, so it is essential for accurate reporting.
The **Service Agreements section** of a Circle's Activity page shows every agreement for that Client, past, current and future. Each row shows the funding source as a short badge (**NDIS**, **DSS**, **MDS**, **CF4S**), the dates, the state and, when the renewal reminder is on, the date it is due. It also shows **Spent**, **Remaining** and **Days left**. Spend is worked out overnight, so the figures are as of last night. Select a row to see each Bucket's figures and its Services.

## How a Service Agreement is organised
A Service Agreement has three levels:
1. **The Service Agreement** is the contract. It has a name, a funding source, a start and end date, and a state.
2. **Buckets** hold the budget. Each Bucket is one budget, such as Core.
3. **Services** are the supports you deliver. Each Service sits in one Bucket. Progress notes draw down the budget of the Bucket their Service is in.
### Buckets by funding source
Comm.care creates the Buckets for you when you choose the funding source.
| Funding source | Buckets |
|---|---|
| **NDIS** | Three: **Core**, **Capacity Building** and **Capital** |
| **DSS (CHSP)** | One for each Outlet Activity. Use **+ Add Activity** for another |
| **Other sources** (Client fee for service, MDS, Home Care Packages, grants) | One **General** Bucket |
An NDIS Service goes in the Bucket that matches the support item. When you add a Service to the Core Bucket, you only see Core items.
## Before you add a Service Agreement
Check that the service is listed under your Organisation in Comm.care, or it will not appear in the form. To add a service, see [Managing Services](../../setup-and-configuration/services-configuration/managing-services.md). Then follow [Add Services to a Service Agreement](adding-services-to-a-service-agreement.md).
## Budgets
Add a budget to a Bucket to:
1. Show a Client's total available funding;
2. Keep track of actual spend (Comm.care fills this in from **progress notes**);
3. Monitor the budget utilisation rate;
4. See how much time is left to use the remaining budget.
You can leave a budget blank when you do not know the figure. This is common when a plan manager or the Client manages the funds. Comm.care then tracks spend only. It does not work out a utilisation rate or show an overspend warning. Enter **0** only when the budget really is zero.
Adding a budget also lets you filter your Circles by budget utilisation, so you can find Clients who need attention.
> _We call this the budget **utilisation rate**: the closer it is to 100%, the closer your spending is to the length of time you are contracted to deliver the service. It is updated every evening. Say you have spent 20% of the budget and you are 20% of the way through a year-long contract. The utilisation rate is 100, and you are on track. Under 100% means you have delivered less than expected by that point. The rate assumes you deliver evenly across the contract, so treat it as a guide._
Each Bucket header shows **$ remaining** and **days remaining**, so you can see at a glance whether funds are being used too slowly or too quickly. In an NDIS Bucket, the **Funding Periods** table shows **Spent**, **Remaining** and **Days left** for each period, with a **Total** row when there is more than one.

---
## Agreement states
Every Service Agreement has a **State**:
- **Plan:** an agreement you are preparing, or one that has not started.
- **Active:** the agreement is in force.
- **Inactive:** the agreement has ended or been stopped.
A new Service Agreement starts as **Active**. If the plan is not signed off yet, set it to **Plan** before you save. An active DSS agreement needs at least one client before it can be saved.
Comm.care does not change the state for you when the end date passes. Change it yourself when the agreement ends. A plan review that runs a few days late then does not switch anything off.
When you set an active agreement to **Inactive** or **Plan**, Comm.care disables its future reminders and appointments. Group appointments stay for the other participants. Progress notes and claims you have already made are not affected.
Only **Active** agreements appear when you choose a service for a new progress note or appointment. Inactive agreements are hidden from the list, but their past notes and appointments still open.
Inactive agreements are hidden on the Activity page. Turn on **Show inactive (n)** under the list to see them.
## Renewal reminder
Turn on the **Renewal reminder** beside the **To** date to be reminded before the agreement ends, and enter the number of days before the end date. The date of the reminder shows next to it, and on the Activity page as **renew on** that date. Comm.care adds a task to the calendar. To start a new agreement from an existing one, see [Renew a Service Agreement](renewing-a-service-agreement.md).
---
## NDIS Funding Periods
NDIS Buckets can have **Funding Periods**: shorter budget windows, such as quarterly. They let you track how well a Client's budget is being used right now, not just across the whole plan.
Each Bucket can hold one or more Funding Periods. Each has its own dates and budget.

When you create an NDIS Service Agreement, each Bucket starts with one period that runs for three months from today. Change the dates and budget to match the plan.
Only NDIS Buckets have Funding Periods. Other funding sources show one budget row, with its **Spent**, **Remaining** and **Days left**.
### Fields
| Field | Details |
|---|---|
| **From** | The first day of the period. |
| **To** | The last day of the period. It cannot be later than the Service Agreement's **To** date. |
| **Budget** | The budget for this period. Leave it blank if unknown. |
| **Spent** | Total spend from progress notes in the period. You cannot edit it. Comm.care updates it each night. A new period that has already started shows **Overnight** until then. |
| **Remaining** | The budget less what has been spent. Blank (**—**) when the budget is blank. |
| **Days left** | Days until the period ends. |
Each progress note counts towards one period only. If two periods overlap, the progress note counts towards the one that started most recently.
Every period is a row of the table. The current period is highlighted, with a blue bar on its left. A period that has spent more than its budget shows **⚠ $ 500 over** in red.
Comm.care marks period dates that need checking:
- **Amber:** the period overlaps another, or starts before the agreement. You can still save.
- **Red:** the period ends after the agreement. The agreement cannot be saved until you fix it.

### Adding a Funding Period
When a period ends, or you want to plan ahead, you do not need a new Service Agreement. Select **Add Period** under the table. The new period starts the day after the latest one ends and lasts as long, up to the agreement's **To** date. Check the dates and enter the budget.
### Removing a Funding Period
Select the bin icon (**Remove period**) on its row.
---
## Related Tutorials
- [Add Services to a Service Agreement](adding-services-to-a-service-agreement.md)
- [Add Group Support Services to a Service Agreement](adding-group-services-service-agreement.md)
- [Renew a Service Agreement](renewing-a-service-agreement.md)
- [What changed: Roadmaps are now Service Agreements](roadmaps-are-now-service-agreements.md)
- [About Circle of Care](overview.md)
- [How to Create Circle of Care](creating-circles.md)