SocialNote for Georgia Districts

How SocialNote helps school social work teams document everyday practice, organize Georgia-aligned data, and prepare reliable district reporting.

The Georgia reporting need

Georgia’s Student Record collection is an end-of-year record of student demographics, program participation, and other educational activity. For school social work teams, dependable reporting starts much earlier: practitioners need a consistent way to record who was served, why support was provided, what happened, where time was spent, and which referrals or broader efforts followed.

Reporting-year basis: FY2025 specifications, confirmed unchanged for FY2026

SocialNote’s current Georgia element labels and crosswalk were developed from the FY2025 Student Record Data Element Detail and School File Layout PDFs retained by the SocialNote team. On August 10, 2026, Dr. Lindsey Oliver, GaDOE School Social Work Specialist, confirmed directly to SocialNote that there were no changes for FY2026. The FY2025 crosswalk therefore remains the current FY2026 baseline. GaDOE’s public site provides a high-level State Reporting page and a general Data Elements dashboard, but the SocialNote team has not located public FY2026 versions of those two detailed technical files.

SocialNote is the documentation and reporting-readiness layer.

It brings student support activity into connected, reviewable records so a district can examine its work before translating approved totals into its official state-reporting process.

This guide describes current SocialNote capabilities and product direction. It is not legal advice, GaDOE certification, or a guarantee that a district’s records satisfy every local or state requirement. District reporting staff remain responsible for the definitions, validation rules, timelines, and submission method in effect for the reporting year.

What SocialNote supports today

Connected practice recordsCases, service logs, referrals, groups, crises, goals, and macro-level efforts share a district and student context.

Georgia mapping metadataThe system-default service catalog includes Georgia DOE element mappings that can support district review and future export work.

Auditable summariesAuthorized users can filter reports by time period, school, staff member, and report-specific dimensions.

Capability	How it helps a Georgia district
Service logs	Record the date, duration, delivery method, service code, student, case, Goal, notes, and follow-up for individual support.
Cases and Goals	Organize episodes of care and, when appropriate, connect measurable outcomes without requiring a formal Treatment Plan for every Case.
Outbound referrals	Document coordination with DFCS, courts, mental-health providers, health services, community agencies, and other destinations.
Groups, crises, and macro efforts	Capture delivered group sessions, crisis response, team activity, community collaboration, special programs, and systems-level work.
Reporting	Review cases, interventions, referrals, unduplicated students, caseloads, time, service codes, demographics, groups, crises, and Goal outcomes.
Custom service codes	Let district administrators add local categories and codes or manage availability while preserving historical records.

How SocialNote records align with Georgia-oriented reporting

SocialNote’s model separates the people served from the work performed. That distinction is important when a district needs both an unduplicated student count and counts of cases, referrals, or interventions.

Georgia-oriented reporting area	Primary SocialNote source	Examples of documented activity
Students served	Students connected to individual services, delivered group sessions, or crisis activity	One student is counted once in an unduplicated view even when several activities exist.
Cases	Cases and their categories	Academic, attendance/dropout prevention, behavior/discipline, family, health, special education, mental health, homelessness, foster care, or child-protection support.
Services and interventions	Service logs, group sessions, crisis logs, and macro-level efforts	Student or family conferences, staff consultation, home visits, group interventions, crisis response, agency contact, and community participation.
Referrals	Outbound referrals and their destination categories	DFCS, juvenile or other court, mental-health services, health services, community agencies, and district-defined destinations.
Context and outcomes	Case status, Goals, progress entries, referral outcomes, closure data, and timelines	Why support began, the response delivered, progress observed, and how the work concluded.

A local code is not automatically a state-reporting category.

When a district adds or changes a service code, its reporting team should decide how that code belongs in the district’s Georgia crosswalk. Historical mappings and current-year GaDOE definitions should be reviewed before totals are submitted.

A practical district workflow

Confirm the reporting year. For FY2026, use the crosswalk confirmed unchanged from FY2025 while district reporting and student-support leaders verify collection dates and local responsibilities. Revalidate the crosswalk before applying it to FY2027 or later.
Agree on the crosswalk. Review the SocialNote service catalog and determine how system-default and local codes should roll up for Georgia-oriented reporting.
Document work where it happens. Practitioners record services, cases, referrals, group sessions, crises, Goals, and macro efforts throughout the year instead of reconstructing activity at year end.
Review completeness regularly. Use reporting filters to check missing categories, unusually low volume, unresolved referrals, uncategorized Cases, and differences between people served and interventions delivered.
Reconcile with district systems. Compare authorized SocialNote summaries with enrollment, school, staff, and state-reporting source systems using the district’s established validation process.
Approve and submit externally. The district’s designated reporting staff apply the current GaDOE rules and complete submission through the district’s approved state-reporting workflow.

Worked example: attendance support

Scenario: A seventh-grade student has a pattern of unexcused absences. The school social worker coordinates with the student, family, attendance team, and a community transportation provider.

SocialNote record	Example entry	Reporting value
Case	Attendance stabilization, categorized for attendance/dropout prevention; opened August 18.	Preserves the episode-of-care context without requiring a formal Treatment Plan.
Goal	Reduce unexcused absences from four per month to one or fewer per month by December 15.	Adds a measurable outcome when the practitioner and student need one.
Service logs	Student conference, parent/guardian conference, staff consultation, and home visit, each with its actual date and duration.	Separates intervention activity from the unduplicated student count.
Referral	Outbound referral to a community transportation provider, with coordination and follow-up recorded.	Documents the destination, status, response, and outcome of external coordination.
Progress and closure	Monthly attendance outcome, final result, closure reason, and next steps.	Connects service volume to the student outcome and explains why the Case ended.

Record each fact once, in the record designed for it.

The Case explains the episode, the Goal measures change, service logs record delivered work, and the referral captures outside coordination. Reports can then summarize those connected facts without relying on duplicate narrative.

District review and validation

Confirm the reporting period, school, and staff scope shown on every report.
Compare unduplicated student counts with intervention counts; they answer different questions.
Review local service codes and retired codes before applying a Georgia crosswalk.
Investigate missing categories at the source record rather than editing a total.
Use Case, referral, and crisis timelines to trace aggregate results back to authorized documentation.
Apply district suppression, privacy, retention, and approval rules before sharing student-level or low-volume information.
Have the designated district reporting owner verify current GaDOE definitions and submission rules.

Current Georgia export status

The dedicated GaDOE Student Record export is not currently released.

SocialNote contains a Georgia-only report prototype and Georgia element mappings, but the prototype is disabled because its displayed totals are not yet generated from production records. Districts should use the released reporting tools for review and continue their approved state-submission process outside SocialNote until a validated export is announced.

Available now	Not represented as available now
Structured documentation across core school social work workflows.	A certified, one-click GaDOE upload file.
Georgia mapping metadata in the default service-code catalog.	Automatic approval of district-defined codes or mappings.
Authorized reports for cases, interventions, referrals, unduplicated students, time, caseload, demographics, crises, groups, and outcomes.	A replacement for the district’s SIS, state-reporting owner, or GaDOE validation process.

Privacy and access

Georgia identifies student data privacy and security as a state responsibility, and FERPA governs access to and disclosure of education records. In SocialNote, report scope follows the signed-in user’s district, role, and authorized school access. Districts should still apply their own access review, retention, disclosure, records-request, and data-sharing procedures.

Use synthetic data in demonstrations and outreach.

Do not place names, GTIDs, dates of birth, contact details, crisis narratives, or other personally identifiable student information in screenshots, support messages, or external presentations.

Who can do what

Role	Typical responsibility
Practitioner	Document services and connected workflows accurately and review reports within assigned access.
School or district administrator	Monitor data quality, manage authorized access, configure local service codes, and coordinate the reporting crosswalk.
District state-reporting owner	Interpret current GaDOE definitions, reconcile district source systems, approve totals, and complete official submission.
SocialNote team	Support implementation, explain product behavior, and collaborate on validated Georgia reporting requirements.

Official Georgia resources

Requirements change. Before each reporting cycle, use the current resources published by the Georgia Department of Education:

FY2025 technical references used for this crosswalk

If the current Student Record Data Element Detail or School File Layout is not publicly available, the district reporting owner should use the district’s authorized GaDOE channels to obtain or validate the applicable specification before submission.

For feature-level instructions, continue with Working With Reporting, Service Logs, Cases, Referrals, and Configuring Service Codes.