An administrator’s guide to tailoring the service-code catalog while preserving shared definitions and historical records.
Service codes give a district a consistent vocabulary for describing completed support. The available catalog appears when staff code time in student service logs, group sessions, and macro-level efforts.
System-default codes also provide a starting crosswalk to Georgia reporting, Texas school mental health, MTSS, SSWAA, and ASCA. Read Framework Alignment before treating a code or tier as evidence for an external standard or report.
| Catalog element | What it controls |
|---|---|
| Category | Groups related codes and reserves the numeric range those codes may use. |
| Code number | Provides the unique identifier used in selectors, records, and reporting. |
| Description | Explains the specific service or activity staff should select. |
| Delivery type | Optionally classifies the service as direct or indirect. |
| MTSS tier | Optionally associates the service with Tier 1, 2, or 3 reporting. |
| Availability | Determines whether the definition may be selected for new entries. |
Search the system-default catalog first. A district code is most useful when it represents a local program, required reporting term, or service that is not already described clearly by a shared code.
District administrators and organization administrators with a district assignment can open Settings → Service Codes. Standard users can select available codes while documenting services, but they cannot change the catalog.
Agree on naming, numbering, delivery type, and tier before publishing a custom code. A short review process prevents near-duplicates and keeps reports understandable.
The settings area has separate Service Codes and Categories tabs. Together they show the district’s effective catalog: SocialNote’s shared system defaults plus definitions created specifically for the district.
| Ownership | What administrators may do |
|---|---|
| System default | Use the shared definition as provided, or hide and later restore an individual code for this district. |
| District custom | Create and edit the category or code, including its active and visible state. |
Use search and filters to narrow codes by description or number, ownership, availability, and category. Availability labels explain why a code cannot be used for a new entry, including Inactive, Hidden, Category inactive, and Hidden for district.
Making a category or code unavailable removes it from new-entry selectors. Existing service records keep their original code links so prior documentation and reporting remain intact.
Every category owns a numeric range, and every code in that category must fall inside it. A district range cannot overlap a system range or another district range.
When editing a district category, the updated range must still contain every code assigned to it. Move or revise the affected codes before narrowing the range.
| Field | Example | Guidance |
|---|---|---|
| Name | District Attendance Programs | Use a stable program family, not a person’s name or a temporary initiative label. |
| Short name | Attendance Programs | Keep it recognizable when space is limited. |
| Description | District-defined attendance and re-engagement programs. | State what belongs here and what does not. |
| Range | 2000–2099 | Reserve enough room for future related codes. |
| Active | Selected | Clear it only when the whole category should disappear from new-entry selectors. |
A district code cannot reuse a number already assigned to a system code or another district code, even when the descriptions differ.
| Action | Use it when | Result |
|---|---|---|
| Hide for District | A system-default code should not appear in this district. | The shared code is suppressed only for the current district and may be restored later. |
| Clear Visible | A district code should be hidden from new selectors without changing its active definition. | The code remains in settings and historical records with a Hidden label. |
| Clear Active | A district code has been retired or should no longer be used operationally. | The code remains in history but is labeled Inactive and excluded from new entries. |
| Deactivate category | An entire district-defined program family is no longer available. | Its codes remain intact but are excluded from new entries while the category is inactive. |
| Restore | A previously suppressed system code is needed again. | The system code returns to new-entry selectors when its shared definition and category are available. |
Do not change an established code number to mean a different service. Make the old district code inactive and create a new definition so historical entries retain their original meaning.
A district operates an attendance success center and wants its staff to identify those check-ins separately from the broader system-default attendance services.
After the code is created, staff can select 2001 — Attendance success center check-in in new service logs, group sessions, and macro-level efforts. If the program ends, the administrator should make code 2001 inactive rather than reuse it for a different activity.
| Action | Standard user | District administrator | Organization administrator |
|---|---|---|---|
| Select available codes in new records | Yes | Yes | Yes |
| View service-code settings | No | Yes | Yes |
| Create or edit district categories and codes | No | Yes | Yes |
| Edit system-default definitions | No | No | No |
| Hide or restore a system code for the district | No | Yes | Yes |
| Change another district’s catalog | No | No | No |
See Service Logs for the day-to-day coding workflow, or use the Service Code Reference to search SocialNote’s system-default taxonomy.