Handel IT

Why Domestic Violence Programs Need More Than Basic Case Tracking

Tiffany Edmonds — Mon, 19 Oct 2026 10:00:59 +0000

A domestic violence or victim advocacy program does a lot more than open a case, document an interaction, and close a file. Behind every case are conversations, services, referrals, follow-ups, and often multiple people working to support an individual’s needs. An advocate might help someone develop a safety plan, connect them with housing resources, arrange financial assistance, or navigate other available services. And those needs can change over time.

It’s a lot to keep track of, especially when staff are balancing direct services with documentation, community outreach, and program responsibilities. That’s why effective domestic violence case management is about more than maintaining a list of clients and case notes. Programs need a way to manage the many moving pieces involved in providing support, while keeping the focus on the people they’re serving.

A Case Is More Than a Collection of Notes

Case notes are an important part of documenting services, but they don’t always tell the whole story.

Consider an individual who reaches out to a victim advocacy program for assistance. During that initial interaction, an advocate may identify several needs. Some may require immediate attention, while others could involve ongoing services or future follow-ups. Over time, the program may need to document referrals, assistance provided, changes to a safety plan, and progress toward established goals. If all of that information lives in individual case notes, it can become difficult to get a clear picture of what’s happening without reading through an entire case history.

A more structured approach helps programs organize different activities and services while maintaining the context of each individual’s experience. Instead of only asking, “What happened during this interaction?” programs can also consider:

What services have been requested or provided?
Are there outstanding referrals or follow-up activities?
What goals has the individual identified?
What assistance has already been provided?
What information does the advocate need for the next interaction?

Having these details organized can make it easier for staff to understand where things stand and determine what may need attention next. Of course, a person’s needs and choices should always guide the process. Case management tools should support advocates and the individuals they serve, not force every situation into the same predetermined workflow.

Coordinating Services Without Losing Sight of the Individual

Domestic violence and victim advocacy programs often help individuals navigate needs that extend beyond one specific service. Someone seeking assistance may also need access to housing, transportation, legal resources, counseling, financial support, or other community services. Meeting those needs may involve several organizations or departments, each providing a different kind of assistance.

The U.S. Department of Justice’s Office on Violence Against Women (OVW ) has emphasized the importance of coordinated community responses that bring together advocates, service providers, and community partners to support survivors. But coordinating services doesn’t mean every organization needs access to the same information. Programs must still follow applicable confidentiality requirements and respect each individual’s choices regarding referrals and information sharing.

From a case management perspective, it can be helpful to document which referrals have been made, what services were requested, and whether additional follow-up is appropriate. For example, if an advocate connects someone with a housing resource, the program may want to track that referral and any subsequent assistance without unnecessarily collecting or sharing sensitive information. The goal isn’t to create more paperwork. It’s to help advocates stay organized as they support individuals whose needs may involve several different services.

Supporting Ongoing Advocacy and Follow-Ups

Not every service is completed in a single interaction. Some individuals may receive assistance over an extended period, while others may return to a program as their circumstances change. That means advocates often have to balance immediate needs with longer-term activities. Depending on the program, this could include monitoring progress toward advocacy goals, documenting additional services, revisiting referrals, or maintaining action plans. When those activities are scattered across notes, spreadsheets, calendars, and other records, it can be harder to see what has already been completed and what still needs attention.

Organizing these activities within a case management process can help staff maintain continuity without relying entirely on memory or manually searching through multiple sources. No two individuals will have the exact same needs, and the appropriate next step isn’t always predictable. Programs need processes that allow staff to document changing circumstances and adjust their approach without unnecessarily complicating their work. Good case management should help advocates remain organized while leaving room for professional judgment and survivor-directed decisions.

Program Management Extends Beyond Individual Cases

Another part of victim advocacy that can be easy to overlook is everything happening outside direct client interactions. In addition to traditional victim services, many programs also coordinate community education, outreach activities, advocate training, hotline services, and other initiatives. These activities may not always fit neatly into an individual client record, but they’re still important parts of how a program operates.

For example, a program may need to document community education events, track staff training activities, or maintain information about shelter services and other assistance provided. When these activities are managed separately from the rest of the program’s information, staff may find themselves switching between different systems, documents, or tracking methods to understand overall program activity. Having a more organized approach can help program leadership understand the different services being provided, identify areas that need attention, and maintain records that support planning and reporting. It also reinforces an important point: managing a victim advocacy program involves more than managing individual cases. It involves supporting the advocates, services, activities, and resources that make that work possible.

Finding Case Management Software That Supports the Work

With so many responsibilities, domestic violence programs should be able to expect more from their technology than a place to store names and case notes.

The right domestic violence case management software should support the different aspects of a program’s work without creating unnecessary complexity. That means helping staff manage ongoing cases, document services, coordinate referrals, track program activities, and prepare for reporting requirements, all while maintaining appropriate security and confidentiality practices.

At Handel, we’ve worked with Tribal and public-sector programs for nearly three decades, developing RiteTrack to support the needs of organizations that provide essential community services.

RiteTrack’s Domestic Violence and Victim Advocacy solution goes beyond basic case tracking with functionality for documenting referrals, safety plans, financial assistance, shelter services, advocacy goals, and community outreach activities. The platform also supports program-specific reporting and offers configurable functionality that can be adapted to an organization’s particular processes and requirements.

But the important thing isn’t simply having more software features. It’s having tools that reflect the work staff actually do. Domestic violence and victim advocacy programs already balance a wide range of responsibilities, often with limited time and resources. When information is organized, services are documented consistently, and follow-up activities are easier to track, staff can spend less time piecing together information and more time providing meaningful support.

Ultimately, effective domestic violence case management isn’t just about keeping better records. It’s about helping programs manage the work behind the services they provide, so advocates can focus on the individuals and communities who rely on them.

LEARN MORE ABOUT RITETRACK

The post Why Domestic Violence Programs Need More Than Basic Case Tracking appeared first on Handel IT.

Ute Indian Tribe Selects RiteTrack to Modernize Tribal Court and Prosecutor’s Office Case Management

Tiffany Edmonds — Wed, 14 Oct 2026 18:31:23 +0000

Handel Information Technologies is pleased to welcome the Ute Indian Tribe as a new RiteTrack customer. Located on the Uintah and Ouray Reservation in northeastern Utah—the second-largest Indian reservation in the United States, covering more than 4.5 million acres—the Ute Indian Tribe will implement RiteTrack within both its Tribal Court and Tribal Court Prosecutor’s Office.

The implementation represents two significant transitions. The Tribal Court will replace its current court management system with RiteTrack, while the Prosecutor’s Office will move from a primarily paper-based record system toward digital case management.

A New Case Management System for the Tribal Court

The Ute Indian Tribe Tribal Court began exploring new tribal court case management software after determining that its current system was no longer meeting its needs. As staff prepare for implementation, the transition of historical case information into RiteTrack will be an important part of the process.

During the evaluation process, Court staff were particularly interested in the amount and variety of information that can be maintained within RiteTrack, including areas such as drug testing and other case activity. RiteTrack’s Tribal Court Module supports the management of multiple case types, criminal charges, hearings and records of action, case notes and documents, court dockets, drug tests, warrants and bonds, protection orders, financial obligations, and statistical reporting.

The Tribe will host RiteTrack within its own environment, allowing the Court to maintain the system using its existing internal technology infrastructure.

Helping the Prosecutor’s Office Move from Paper to Digital

The Tribal Court Prosecutor’s Office came to Handel with a different challenge. Staff were looking for prosecution case management software that could help transition the office from paper files to a more organized digital system.

Document management was a major consideration. The office works with a wide range of case materials, including Word documents, PDFs, images, and video evidence, and currently maintains much of its record through paper-based processes.

With RiteTrack, the Prosecutor’s Office will begin establishing a centralized digital approach to maintaining prosecution case information and supporting documentation. Moving existing records into the new system will be an important part of that transition, particularly as staff work through the substantial amount of documentation currently maintained outside of a case management platform.

Building a Stronger Digital Foundation for Tribal Justice

By implementing RiteTrack in both the Tribal Court and Prosecutor’s Office, the Ute Indian Tribe is establishing a common technology foundation that can be configured around the distinct responsibilities and workflows of each office.

For the Court, that means moving to tribal court case management software that supports detailed case tracking, documentation, court activity, and reporting. For the Prosecutor’s Office, it means taking an important step away from paper records and toward a more centralized digital case management process. With the two systems integrated using appropriate security controls, staff will also be able to reduce duplicate data entry while maintaining the separation and permissions required for their respective roles.

Handel is proud to partner with the Ute Indian Tribe as Court and Prosecutor’s Office staff prepare for the transition and implementation of RiteTrack.

About RiteTrack

Founded in 1997, Handel Information Technologies has nearly three decades of experience developing case management technology for justice, human services, and Tribal programs. Handel is the creator of RiteTrack, a configurable, web-based case management platform designed to help organizations centralize information, manage documentation, support day-to-day workflows, and improve reporting. Today, RiteTrack is used by Tribal programs and justice and human services organizations across the country.

The post Ute Indian Tribe Selects RiteTrack to Modernize Tribal Court and Prosecutor’s Office Case Management appeared first on Handel IT.

Managing Sensitive Information in Domestic Violence Programs

Tiffany Edmonds — Mon, 12 Oct 2026 15:59:37 +0000

For domestic violence and victim advocacy programs, information is more than just something to document and organize. It can be deeply personal, sensitive, and, in some situations, directly connected to someone’s safety.

Advocates and caseworkers may work with everything from personal histories and service requests to safety plans, referrals, and ongoing case notes. This information helps programs provide meaningful support, but it also comes with a significant responsibility to protect the people behind those records.

That’s what makes domestic violence case management different from many other types of program management. Staff need access to the information necessary to do their jobs, but that access must be balanced with strong confidentiality practices and reliable security measures.

So, what does responsible information management look like for domestic violence and victim advocacy programs?

Confidentiality Goes Beyond Keeping Records Secure

When we think about protecting sensitive information, the first things that often come to mind are passwords, secure storage, and limiting access to records. Those are important, but confidentiality involves much more than technology. It also involves understanding when information can be shared, who is authorized to receive it, and how those decisions affect the individuals receiving services.

For programs receiving certain federal funding, confidentiality is also a legal requirement. The U.S. Department of Justice’s Office on Violence Against Women (OVW) outlines protections for personally identifying and individual information collected in connection with services. These protections generally restrict disclosure, with specific exceptions involving informed written consent or legally compelled disclosure.

In practice, that means programs need clear policies and procedures for handling sensitive information, not just a secure place to store it. And importantly, confidentiality isn’t just about following regulations. It’s about creating an environment where individuals can seek assistance with greater confidence that their personal information will be respected and protected.

Not Every Staff Member Needs Access to Every Record

One of the challenges of domestic violence case management is determining who should have access to different types of information.

A program director may need access to overall program activity and reporting information. An advocate may need detailed information about the individuals they’re working with. Administrative staff may need certain demographic or service information without necessarily needing access to sensitive case notes.

Even within the same organization, different responsibilities can call for different levels of access.

This is where role-based access and well-defined internal procedures become important.

Rather than treating every record as equally accessible to everyone, programs should consider what information staff actually need to perform their responsibilities.

It’s also worth revisiting these permissions as responsibilities change. A staff member who moves into a new role may need different access than they had previously.

This is also an important consideration when choosing case management software. Systems with customizable user-security groups allow organizations to establish permissions based on staff responsibilities rather than providing everyone with the same level of access.

For example, RiteTrack uses role-based security groups to control what individual users can view, create, edit, or delete within the system. Permissions can even be managed at the individual field level, giving organizations greater control over who can access sensitive information. You can learn more about these capabilities in our article, Inside the RiteTrack Admin Interface: Tools for Configuration, Security, and Control.

The goal is to make necessary information available to the right people while reducing unnecessary exposure of sensitive records.

Sharing Information Requires Careful Consideration

Domestic violence and victim advocacy programs rarely operate in complete isolation. Depending on the program, staff may coordinate with community organizations, social services, legal advocates, housing resources, and other service providers. These relationships can be important for helping individuals access assistance.

However, coordinating services doesn’t automatically mean sharing client information. Before disclosing information, programs need to consider applicable confidentiality laws, funding requirements, consent procedures, and their own established policies. Even when organizations are working toward a shared goal, they may not have the same authority to access an individual’s records.

For Tribal programs, this can be especially relevant when domestic violence services operate alongside other Tribal departments. While coordinated services may offer benefits, information sharing should still be carefully controlled and consistent with applicable confidentiality requirements.

Thoughtful coordination means finding ways to support individuals without unnecessarily compromising their privacy.

Good Documentation Should Support Both Service Delivery and Privacy

Maintaining accurate records is an important part of domestic violence case management.

Case notes, service histories, referrals, and follow-up activities can help staff maintain continuity and understand what assistance has already been provided. But more documentation isn’t always better. Programs should consider what information is actually necessary to support their work and meet applicable requirements. Recording unnecessary personal details can create additional privacy concerns without necessarily improving services.

Consistency also matters.

Clear documentation practices help staff understand what should be recorded, how information should be maintained, and what details require additional protection. For example, programs can benefit from establishing internal expectations around:

What information is necessary to document services
How sensitive case notes should be handled
Who is authorized to access or update records
When information may be shared and what consent is required
How records should be maintained and retained

These practices should be guided by the program’s legal obligations, funding requirements, and organizational policies. Ultimately, good documentation should help staff do their jobs without collecting or exposing more information than necessary.

Building Security Into Everyday Case Management

Strong confidentiality practices should be supported by equally strong security measures. For domestic violence and victim advocacy programs, that means looking beyond whether a system can store case notes or generate reports. It’s also important to consider how information is protected, who can access it, and how activity within the system is monitored.

Some important security features to look for in domestic violence case management software include role-based permissions, encryption, audit trails, secure hosting options, and additional authentication measures. At Handel protecting sensitive information has been a priority throughout our nearly 30 years of developing case management software for Tribal programs and public-sector agencies. Our RiteTrack platform incorporates multiple layers of security, including user-security groups, detailed audit logs, encryption for data in transit, and optional two-factor authentication. Organizations can also choose between Handel-hosted and self-hosted deployments depending on their infrastructure and security needs. These capabilities help organizations maintain control over their information while giving authorized staff the access they need to perform their responsibilities.

Of course, technology is only one piece of the puzzle. Even the most secure software needs to be supported by clear policies, proper staff training, and consistent confidentiality practices. The goal isn’t simply to protect information from outside threats. It’s to help programs manage sensitive records responsibly throughout their everyday work.

Keeping the Focus on the People Behind the Records

At the end of the day, domestic violence and victim advocacy programs aren’t simply managing cases. They’re supporting individuals who may be navigating difficult, sensitive, and sometimes dangerous circumstances. The information collected throughout that process deserves careful attention.

Strong confidentiality practices, thoughtful documentation, appropriate access controls, and clear information-sharing procedures all contribute to a more responsible approach to managing sensitive records. And while every program may have different workflows, resources, and requirements, the underlying goal remains the same: protect sensitive information while ensuring staff have what they need to provide meaningful support.

Supporting the Work of Domestic Violence and Victim Advocacy Programs

At Handel Information Technologies, we understand that domestic violence and victim advocacy programs have unique case management, security, and reporting needs. Explore RiteTrack’s Domestic Violence and Victim Advocacy solution to learn how our software supports secure record management, service tracking, and program reporting.

EXPLORE THE SOLUTION

The post Managing Sensitive Information in Domestic Violence Programs appeared first on Handel IT.

Before You Build Your Own Data Management System

Tiffany Edmonds — Mon, 05 Oct 2026 07:26:47 +0000

AI has changed what it takes to build software.

Tasks that once required significant development experience can now be accelerated with AI. Developers can use AI to help generate code, create interfaces, troubleshoot problems, structure databases, and develop applications much faster than before. For organizations looking at the cost of an established data management system, that can make building something internally seem much more realistic. And in some cases, it may be.

But building an application is only one part of creating a dependable data management system. Once staff rely on that system every day, the organization also has to maintain, secure, support, update, and improve it over time. For Tribal programs, courts, probation departments, social service agencies, public-sector organizations, and other teams managing operational information, those responsibilities can quickly become substantial.

AI Has Lowered the Barrier to Building Software, but Building is Only the Beginning

The question of whether to build your own data management system is not new. Organizations have always had the option to develop something internally if they had the technical resources to do it. AI simply makes that option more accessible.

A developer can now move from an idea to a working prototype much faster. Smaller teams can accomplish work that previously required considerably more development time. Organizations may also be able to create tools around very specific internal processes.

Those are real advantages. The challenge comes after the first version is built.

Once staff begin depending on a system to manage people, cases, services, documents, applications, eligibility, payments, court activity, program data, reporting, or other information, someone has to take responsibility for everything behind it. That goes well beyond the original code.

Who Owns the System After It Is Built?

One of the biggest questions organizations should ask is not simply: Can we build this?

It is: Who is going to own it five years from now?

An internally developed data management system needs someone to manage updates, troubleshoot problems, respond to users, make changes, maintain documentation, test new functionality, address security concerns, and ensure the system continues working as the organization changes. If the employee or contractor who originally developed the system leaves, someone else needs to understand what was built and why. If a reporting requirement changes, someone has to update the system. If staff identify a workflow that could be improved, someone has to design and test that change. If a technical dependency changes or a vulnerability is identified, someone has to respond.

Security itself also extends well beyond the initial build. The National Institute of Standards and Technology’s Secure Software Development Framework (SSDF) outlines secure development as an ongoing process that includes preparing the organization, protecting software, producing secure software, and responding to vulnerabilities. AI can help with many of those responsibilities, but it does not eliminate them.

What a Strong Data Management System Should Look Like

A good data management system has to do more than work well in a demo. It should support the way an organization actually operates day to day, including the exceptions, changing requirements, different user roles, and reporting needs that come with real programs.

That means the system should be built to handle things like role-based access, historical data, changing workflows, organized documents, consistent data entry, and different views of information for different types of users. Front-line staff may need quick access to individual records and day-to-day tasks, while leadership may be more focused on trends, outcomes, and reporting.

It should also be able to evolve. Staff roles change. Programs add services. Reporting requirements shift. New processes are introduced. A data management system should be able to adapt without requiring the organization to rebuild major parts of it every time something changes.

Reporting is a good example. A strong system should not simply store information and hope it can be pulled together later. Data should be structured in a way that makes reporting reliable and useful from the start. That includes maintaining clear relationships between records, supporting consistent data entry, and making it easier for staff to retrieve the information they need for federal, state, Tribal, grant, or internal reporting.

Support should be part of that picture as well. When a workflow changes, a report needs to be updated, or staff have questions, there should be a clear process for addressing it. A system becomes much more valuable when organizations are not left to figure out every technical issue on their own.

The same principles apply when AI is introduced. AI can help summarize, analyze, or surface information, but it still depends on the quality and organization of the data underneath it. We have written before about why organizations should focus on data quality before AI. The better organized the underlying data is, the more useful tools built on top of it can become.

That is the kind of foundation organizations should be looking for: a system that is organized, adaptable, supportable, and built to keep working as the organization grows and changes.

Experience Is Hard to Build From Scratch

An established data management platform also comes with something that cannot be generated as quickly as code: experience.

When a new organization implements RiteTrack, it is not the first time our team has encountered complicated workflows, reporting requirements, role-based access, historical data migration, multiple departments, or program-specific processes. RiteTrack has been developed and refined over decades of working with Tribal programs, justice organizations, human services agencies, and other public-sector programs. That experience influences more than the features available in the software. It also helps our team understand the questions that need to be asked during implementation, where organizations may need additional flexibility, and how different pieces of information need to work together.

Some organizations use RiteTrack primarily for case management. Others use it more broadly for data management, program tracking, reporting, document management, eligibility, services, financial information, court activity, or other operational processes. Instead of starting with a blank database and deciding how every part of the system should work, organizations can start with an established platform and configure it around their own processes.

The Support Team Is Part of the System

Software comparisons tend to focus heavily on functionality, but functionality is only part of what an organization is choosing. With RiteTrack, customers also have a team behind the platform.

Our team works with organizations during implementation to understand what they need to track, how their current processes work, how staff interact with information, and how RiteTrack should be configured.That relationship continues after implementation. When customers have questions, need changes, want to improve a workflow, add functionality, or rethink how they are managing information, they have a team they can work with. RiteTrack support includes access to an assigned project manager, staff training, data requests, and regular system updates.

With an internally developed system, the organization itself takes on those responsibilities.

That may be a good fit for an organization with the staff, resources, and technical infrastructure to support it long term. But the true investment goes well beyond the time it takes to develop the first version.

Established Does Not Have to Mean Inflexible

One reason organizations may consider building their own data management system is flexibility. They do not want to change the way they operate simply to fit software that was designed for someone else. That is why RiteTrack was designed to be configurable because organizations and programs operate differently. Customers can configure what information they track, how workflows operate, who can access information, how reports are structured, and other areas of the system around their needs. When additional functionality is necessary, our team can also work with customers on customization. That gives organizations the ability to shape the software around their operations without taking on the responsibility of building and maintaining an entire data management platform themselves.

AI May Make a Strong Data Foundation Even More Valuable

As AI becomes easier to integrate into everyday work, organized and reliable data becomes even more useful.

Organizations still need to think about how data is structured, where it is stored, who has access to it, how consistently it is entered, and how staff can use it. We see AI as another tool that can work alongside good data management, not as a replacement for it.

That approach is also behind RiteTrack Assistant, our AI-enabled add-on within RiteTrack. Rather than creating a separate AI tool disconnected from an organization’s data management platform, RiteTrack Assistant works within RiteTrack and respects the user’s existing roles and permissions. It can help users interact with RiteTrack data, summarize case notes, suggest potentially useful dashboard tiles and reports, provide general AI assistance, and escalate unresolved RiteTrack-specific questions to the customer’s project manager.

In other words, the AI is being added to an existing system where the data, user access, workflows, reporting, and support structure are already in place. That relationship between technology and professional expertise is where AI can become genuinely useful.

The Question Is Bigger Than Build Versus Buy

Organizations absolutely can build their own software, and AI will continue making development faster and more accessible.

But deciding whether to build your own data management system requires more than comparing the cost of an established platform with the cost of creating an application. It also means deciding who will maintain it, secure it, document it, improve it, train users on it, preserve institutional knowledge, support staff, respond when something goes wrong, and keep the system useful as the organization changes.

For some organizations, owning all of those responsibilities internally may make sense. Others may prefer to keep their internal teams focused on their programs, operations, and communities while an experienced software partner focuses on the technology supporting that work.

At Handel, we have spent decades developing, implementing, supporting, and improving RiteTrack alongside the organizations that use it. New technology gives us more tools to build with, but it does not replace the experience, support, and long-term work required to turn software into a system an organization can depend on.

Interested in learning more about how an established, configurable platform can support your organization’s data management needs?

START A CONVERSATION

The post Before You Build Your Own Data Management System appeared first on Handel IT.

Human Judgment Still Matters: AI as Support, Not a Substitute

Tiffany Edmonds — Tue, 29 Sep 2026 07:36:34 +0000

Artificial intelligence can process information quickly. It can summarize lengthy notes, organize information, identify patterns, and help users navigate large amounts of data.

What it cannot do is replace the experience, context, relationships, and professional judgment of the people doing the work.

Tribal programs, courts, probation departments, juvenile facilities, victim services programs, social services agencies, and other public-sector organizations work with situations that are rarely simple. The information stored in a case management system may help inform a decision, but it is only one part of the picture. People understand circumstances that data alone may not fully capture.

That is why human oversight in AI should remain a central part of how organizations think about using artificial intelligence in case management.

AI Can Help Make Information More Manageable

Case management systems can contain a significant amount of information. Depending on the program, staff may work with case notes, service histories, demographic information, assessments, court activity, appointments, tasks, documents, deadlines, outcomes, referrals, and reporting data. Finding and understanding the right information can take time, particularly when a case has a long history or staff are managing large caseloads.

AI can help reduce some of that information burden. But helping someone understand information is different from deciding what that information means. A summary can provide a starting point. It should not become the final word.

The Same Information Can Mean Different Things in Different Cases

Case management work depends heavily on context. Two cases with similar information in a database may require very different responses based on circumstances that are difficult to reduce to fields, categories, or individual notes.

A probation officer may know important context from conversations with a participant. A caseworker may understand a family’s history and current circumstances. Court staff may recognize procedural considerations that are not obvious from a summary of the record. A victim advocate may understand safety concerns, relationships, or circumstances that require particular care.

Program staff also understand their own policies, community expectations, workflows, and responsibilities. AI does not replace that knowledge. This is one reason human oversight in AI becomes particularly important when technology is used around sensitive or high-impact work. Staff need to remain responsible for reviewing information and determining what is relevant to the situation in front of them.

A Summary Is Still a Summary

AI-generated summaries are a good example of where the distinction between assistance and judgment matters. When a case contains months or years of notes, being able to quickly summarize that information may help someone get oriented before reviewing the record more closely. That can save time, but a summary necessarily condenses information. Details may carry different levels of importance depending on the person reviewing the case and the decision being made.

Something that appears minor in a broad summary could be significant to an experienced caseworker, probation officer, advocate, or court professional. For that reason, AI-generated information should be treated as a tool for navigating the underlying record rather than a replacement for it. The original information still matters, and staff judgment still matters.

Professional Judgment Includes More Than Data

Good case management is not simply a matter of collecting enough information and arriving at an answer. It often involves understanding people.

Staff build relationships with clients, participants, families, community members, and other agencies. They learn how an individual’s circumstances have changed over time. They understand program requirements while also recognizing situations that may require additional attention or discussion.

In Tribal programs, that context may also include the Nation’s own policies, priorities, governance structures, and community knowledge. Those elements are difficult to capture completely in software—and they should not be treated as though they can simply be automated away.

Technology can provide information to the people responsible for the work. The people responsible for the work must still interpret it.

Human Review Also Provides an Important Check

Keeping people involved is not only about professional expertise. It is also an important safeguard.

AI-generated responses can be incomplete, inaccurate, or based on an imperfect understanding of the information available to them. The quality of the underlying data matters, as we discussed earlier in this series, but even well-maintained information does not eliminate the need for review.

Staff should be able to look at what an AI tool provides and ask:

Does this match the information in the case?
Is important context missing?
Is this relevant to what I am trying to accomplish?
Do I need to review the original records before acting on it?
Does this align with our program’s policies and procedures?

Those questions reinforce an important principle: AI output should be evaluated, not automatically accepted. Human oversight in AI helps preserve accountability by keeping staff actively involved in how information is interpreted and used.

The Goal Should Be Better Support for Staff

Much of the conversation around artificial intelligence focuses on what AI might eventually be able to do instead of considering where it can be useful today.

In case management, one of the more practical opportunities is much simpler: helping staff work more effectively with information. That is the approach behind RiteTrack Assistant.

RiteTrack Assistant is an AI-enabled add-on within RiteTrack that can interact with RiteTrack data and provide general AI assistance. It can help summarize case notes, identify dashboard tiles users may find useful based on their data, suggest reports that may be helpful based on available information, and escalate unresolved RiteTrack-specific questions to the customer’s project manager.

Those capabilities are intended to assist the user—not take the user’s place.

A suggested report is still a suggestion. A case note summary still requires appropriate review. Information surfaced by an assistant still has to be considered by someone who understands the program and the situation. The value is in helping staff get to useful information more efficiently while keeping them at the center of the process.

AI Should Complement Expertise, Not Compete With It

At Handel, we believe the value of AI in case management comes from helping people work more effectively with information—not from separating organizations from control of that information. That perspective has shaped how we think about RiteTrack Assistant, our AI-enabled add-on within RiteTrack.

RiteTrack Assistant is designed to interact with RiteTrack data and provide AI assistance within the case management environment. Among its capabilities, it can summarize case notes, help users identify dashboard tiles they may find useful based on their data, suggest useful reports based on available data, provide general AI assistance, and escalate unresolved RiteTrack-specific questions to the customer’s project manager.

Those capabilities illustrate why the larger governance conversation matters. AI becomes more useful when it can work with relevant information. But as its access to information becomes more meaningful, questions of ownership, privacy, permissions, transparency, and control become more meaningful as well. The goal should not be to introduce AI simply because the technology is available. The goal should be to determine where AI can provide practical value while maintaining appropriate control over the information on which Tribal programs depend.

Keeping Sovereignty at the Center

Artificial intelligence will continue to change how organizations interact with data. The technology will evolve, new capabilities will emerge, and AI will likely become increasingly integrated into the systems people use every day.

The principles surrounding Tribal data should not become secondary as that happens. For Tribal Nations, AI and Tribal data sovereignty belong in the same conversation. AI can provide new ways to understand and use information, but technology providers should not be the ones determining what control means for a Tribal Nation. Tribes should remain central to decisions about their data, including how emerging technologies interact with it. That means keeping ownership, governance, privacy, permissions, transparency, and responsible use in view as AI capabilities develop.

The most useful technology is not simply technology that can do more. It is technology that supports the people and organizations using it while respecting their authority over the information that makes that work possible.

Interested in how AI can fit into case management without losing sight of data control? Learn more about RiteTrack Assistant and how we’re approaching AI within RiteTrack.

Learn more about RiteTrack Assistant

The post Human Judgment Still Matters: AI as Support, Not a Substitute appeared first on Handel IT.

The Truth About Juvenile Justice Data Collection

Drew Shover — Thu, 24 Sep 2026 16:35:25 +0000

Juvenile justice data collection at the local and state levels remain challenging because of lack of data implementation strategy and buy-in from officers. Both state and local jurisdictions strive to improve their practices but still face barriers to collecting consistent information. However, jurisdictions do not prioritize juvenile justice data collection because they are consumed with issues within their community, leaving data entry for when they can complete it. This often leaves us questioning the accuracy of the reports or whether we should bother collecting it.

Juvenile probation officers face community and case management challenges daily. They must preserve public safety and rehabilitate the individuals in their care while juggling multiple tasks, making data entry an unwanted burden. At the probation administrative level, their roles focus on managing office duties, turnover, supporting officers, case management, and overseeing outcomes for their community and elected officials. As one can infer, probation administrative officers regularly need to evaluate outcomes using data systems to perform well in their roles. Unfortunately, they are often in survival mode, and managing outcomes often falls to the bottom of the list. This challenge can become even more complicated when information and processes are disconnected between probation and juvenile facilities, something we’ve explored in more detail in Where Probation and Insitutions Disconnect–and Why It Matters.

Probation administrators interview prospective officers who say, “I want to help people.” This is true for anyone entering a public service role. However, after being hired, officers quickly learn that the position is far more complex than simply helping people. Once on the job, they must follow policies and procedures, including juvenile justice data collection, that disconnect them from what brought them to the profession. As a result, staff seem to have no middle ground. Data entry becomes daunting and stressful, causing frustration and conflict across the organization.

Collecting statewide juvenile justice data is also essential to support evidence-based practices, policy, lawmaking, assess trends and patterns, ensure accountability, promote equity and equality, evaluate racial disparities, and secure funding opportunities for the state. Controversially, the state may overlook user feedback when systems are cumbersome and not user friendly. However, jurisdictions do not always account for the state’s jurisdictional diversity, which makes it difficult to build a system that serves all areas of the state. As a result, they reach an impasse, and the two entities may disengage despite relying on each other.

Both areas within the juvenile justice system are staffed by inquisitive, hard-working, and dedicated personnel who may not reap the fruits of their labor. Probation staff may lose sight of the analytical benefits of data collection, and the state may not receive the data it needs to understand jurisdictional challenges. Consequently, state-developed systems may lack buy-in because staff do not want to use them and are not informed of the specific purpose of juvenile justice data collection.

Building a Data Culture That Works

Data does not enter itself, and the only way to match numbers with stories is to have holistic data management. This involves training, supporting, cleaning, and dissemination to define purpose. Each area is vital to understanding commonalities and differences within groups and sharing accurate information with all community partners. However, this cannot happen without the right people overseeing the data. Without proper support, it becomes numbers on a report.

Data integrity lives and breathes within a jurisdiction. The state cannot assume responsibility for local information collection; each jurisdiction must choose how to collect and apply its data to strengthen its organizational data culture through leadership.

When building a progressive data culture within a jurisdiction, leadership must be prepared to answer a few simple questions from their stakeholders:

How is our data being used to serve our community and families?
How do we monitor the data for accuracy?
What does the data we collect mean?
How does this system help me?

Jurisdictions overlook data culture as a workplace barrier, and it requires direct attention. They lack insight into how a poor data culture prevents data entry, and they must attend to their primary daily duties. This causes administrators to miss opportunities to engage their entire, multi-generational teams.

All generations of juvenile officers need leadership to share knowledge, help them understand the “why” behind their requirements, train them according to their learning modalities, and lead them as purpose-driven professionals. Consequently, if we cannot answer the above questions, officers default to their own collection methods, and data entry is no longer a priority.

Making Dual Entry Work

It is an interesting conversation about how juvenile justice organizations collect their data. Their responses trouble those who oversee data collection systems. In these discussions, officers are very proud of their spreadsheets, binders, and wall-mounted dry-erase boards. Agreeably, they should be proud of these methods because they take the initiative to track their work and document their efforts as juvenile officers. However, the information stays with each officer. Ultimately, the jurisdiction lacks a shared centralized juvenile justice data collection method, and those who collect the information may not know how to interpret it.

Analytics professionals analyze data to identify jurisdictional trends and patterns and apply them to the community’s needs. State data professionals interpret what is received. However, they may not know the data’s accuracy and take it at face value. By contrast, local jurisdictions lack a system to export information immediately to identify inaccuracies, and they may need training to evaluate the data. As a common response, the jurisdiction requests information from the state and receives it in an unfamiliar format that requires additional time to explain, thereby exacerbating the issue of using a system that cannot accommodate the organization’s needs.

When jurisdictions receive state reports, they recognize the data’s complexity. Jurisdictions must collect, clean, evaluate, and apply data strategically. This requires teams of professionals to work toward the same goal and share outcomes with external sources. For this to happen, the system must be user-friendly, leadership must be open to discussing how trends emerge, and the information must be verified as accurate through feedback and outcomes. Local areas have an idea of their outcomes from their experience but may not fully understand the magnitude of their community issues until the data is matched with their experience.

Statewide systems generally do not isolate community needs at the micro level. The information sought from the state includes standard demographics, offenses, dispositions, and post-adjudication completion data. Each state must trust that case management follows best practices because it lacks the personnel to oversee these areas. This leads jurisdictions to seek more refined products to meet their specific needs. However, this investment in their community can produce rapid results and inform better outcomes for those who need them immediately.

Allocating resources to another system is difficult. It’s frustrating to have to purchase something that should be provided. However, once the decision is made to invest in a user- friendly system, it raises the question, “Why do we need to input in two systems now? and that seems to defeat the purpose. If one system isn’t being used, then two systems will be even harder to convince personnel that it is a better option for the organization. However, it depends on how systems are implemented and managed, especially as they relate to our essential duties if systems cannot talk.

Integration may be an option, but for most it is not because of the labor hours involved with making two systems talk and moving a large amount of information from one system to the other. If data is valued as a means of improving the agency’s awareness of immediate outcomes, then the dual-entry methods must be explored. This is not a preferred method because organizations feel it distracts them from the population they serve by requiring unnecessary data entry. However, once implemented, dual-entry can allow jurisdictions to use tailored systems to produce real-time outcomes and apply them immediately to serve their population more efficiently.

The concept of dual entry is simple and less taxing than one might expect. To make it feasible, we must identify and enter the data the state needs, then move to the tailored system for your reports and details. If jurisdictions enter the information within a reasonable time frame in their state system, they can use their preferred system to monitor and disseminate outcomes instantly. This eliminates the need to request data from the state and interpret reports, creates opportunities to build data visualizations, and immediately validates existing data across systems.

That said, juvenile justice data collection is relative. Juvenile justice professionals already perform multiple tasks by duplicating information across spreadsheets, or (if a strong data culture does not exist within our organization) we settle into complacency and fail to collect vital information to better serve our population. We must decide, because people depend on local justice systems to improve their communities. Our options boil down to continuing on an aimless data path and overlooking the importance of our data. Attempt to integrate our information into mass systems and spend money to save minimal time on data entry? Or will we develop organizational strategies and use a tailored system to export our information into usable data while creating new strategies to make it less of a task and more of a tool?

How RiteTrack Can Help

If your organization is looking for ways to improve juvenile justice data collection, RiteTrack can help bring case information, reporting, and day-to-day workflows into one place. Because RiteTrack can be configured around your organization’s processes, staff can capture the information they need while giving leadership better access to the data they use to understand trends, monitor outcomes, and support decision-making.

Learn more about RiteTrack

The post The Truth About Juvenile Justice Data Collection appeared first on Handel IT.

AI and Tribal Data Sovereignty: Why Control Matters

Tiffany Edmonds — Tue, 22 Sep 2026 10:06:58 +0000

Artificial intelligence is creating new opportunities for organizations to work with information in different ways. AI can help summarize large amounts of text, identify relevant information, assist with everyday tasks, and make complex datasets easier to navigate.

For Tribal Nations and Tribal programs, however, the conversation cannot begin and end with what AI can do. It also has to include who controls the data AI interacts with, how that information is accessed, what it is used for, and what role the Tribe has in determining those boundaries.

That makes AI and Tribal data sovereignty closely connected conversations.

Tribal programs may manage information related to families, children, court involvement, victim services, financial assistance, employment, elder services, probation, enrollment, and many other areas of Tribal government. Much of that information is sensitive. Some of it may also have significance beyond the individual record because it relates to Tribal citizens, communities, programs, and governance. As AI becomes more common in the technology used by governments and service organizations, maintaining control over that information matters.

Data Sovereignty Is About More Than Data Security

Data security is important, but Tribal data sovereignty is a broader issue.

The Native Nations Institute describes Indigenous data sovereignty as the right of a nation to govern the collection, ownership, and application of its own data. That right derives from the inherent sovereignty of Tribal Nations to govern their peoples, lands, and resources.

A conversation about security might focus on whether information is protected from unauthorized access. A sovereignty conversation goes further. It considers who has authority over the data in the first place and who gets to determine how that information may be collected, accessed, analyzed, shared, and used.

AI introduces another layer to those decisions because data may no longer simply be stored or retrieved. An AI-enabled system may also be able to interact with information to summarize it, identify patterns within it, or help a user locate relevant information. For a Tribal Nation, adopting that type of technology should not mean giving up control over the data that makes those capabilities possible.

AI Changes How We Interact With Information

Traditional case management systems generally rely on users to navigate records, search for information, review case notes, run reports, and interpret what they find. AI can create a different kind of interaction. Instead of manually reviewing multiple pieces of information, for example, a user might ask an AI assistant to summarize existing case notes. AI may also help users identify useful ways to view or report on data already within a system.

That can make information easier to work with. But it also means organizations need to think carefully about what information an AI tool can access and what happens when it does. This is one reason AI and Tribal data sovereignty should be considered together rather than treating AI implementation as a purely technical project.

The important issue is not simply whether an AI tool can interact with data. It is whether that interaction happens within boundaries established and understood by the organization responsible for that data.

Control Should Extend to AI Access

Most case management systems already involve decisions about access.

A staff member working in one program may need different information than a supervisor. Court staff may have different responsibilities than probation staff. A victim services program may manage information that requires particularly careful controls. Tribal governments may operate multiple programs that need to collaborate in some areas while maintaining clear boundaries in others.

Introducing AI does not eliminate the need for those distinctions. If anything, it makes them more important. Organizations need a clear understanding of what information an AI capability can interact with and under what circumstances.

That includes thinking about areas such as:

What information is available to the AI capability?
Which users are permitted to use AI-enabled functions?
What information can a particular user access through those functions?
What happens to information when it is processed by an AI service?
How does the technology provider handle and protect that information?
Are the boundaries around AI access understandable to the organization using the system?
Can the organization establish governance policies around appropriate AI use?

The answers will not necessarily be identical for every Tribal Nation or every program. And that is part of the point. Data governance should reflect the priorities, policies, responsibilities, and circumstances of the organization governing the data—not simply the capabilities of the technology.

Privacy and Sovereignty Are Related, but They Are Not Identical

AI discussions frequently focus on privacy, and appropriately so. Programs working with children, families, court participants, victims, elders, or individuals receiving assistance have substantial reasons to think carefully about sensitive information. But an individual privacy framework does not necessarily address every concern associated with Indigenous data.

The Global Indigenous Data Alliance’s CARE Principles for Indigenous Data Governance emphasize Collective Benefit, Authority to Control, Responsibility, and Ethics. The framework recognizes that Indigenous data governance involves collective rights and interests in addition to individual considerations.

That provides an important perspective for emerging technologies. Protecting an individual record from inappropriate disclosure is important. So is recognizing the authority of Tribal Nations to determine how information concerning their citizens, programs, communities, and governments is managed and used. For technology providers working with Tribal governments, respecting that distinction requires more than applying a standard privacy message to every customer. It requires recognizing that control itself matters.

Transparency From Technology Providers Matters

Organizations cannot make informed decisions about AI when they do not understand how it works with their information.

Technology providers do not need to turn every conversation into a highly technical explanation of artificial intelligence. But they should be able to clearly explain how their AI capabilities relate to customer data.

That becomes especially important when an AI feature is connected to a system containing case information rather than being used as a completely separate general-purpose tool. Tribal programs should be able to understand what role the AI technology plays, what information it can interact with, and where the responsibilities of the technology provider begin and end.

Transparency also helps organizations develop their own policies.

A Tribal Nation cannot effectively establish expectations around AI use if staff and leadership do not understand what the technology is actually doing. Governance becomes much more difficult when AI is treated as a mysterious feature operating somewhere in the background. Responsible implementation should make the technology easier to understand—not harder.

Governance Is an Organizational Decision, Not Just a Technology Setting

There is another important side to AI and Tribal data sovereignty: technology alone cannot establish good governance. Software can provide tools and controls, but each organization still determines how technology fits within its own policies and operations.

A Tribal court may approach AI differently than a TANF program. An ICW or ICWA program may have different considerations than an elder support department. Victim services programs, Tribal probation departments, and administrative programs may each work with different information, responsibilities, and levels of sensitivity. There may not be one AI policy that makes sense across every department.

Governance can include determining when AI assistance is appropriate, what information staff should or should not provide to an AI tool, when AI-generated information requires additional review, and who is responsible for establishing those expectations. Those decisions should remain grounded in the Tribe’s own priorities and governance structures.

This is also why conversations about responsible AI should involve more than an IT department. Depending on the organization, program leadership, administrators, legal counsel, information technology staff, records personnel, and the people doing the day-to-day work may all bring important perspectives to how AI should be used.

AI Should Work Within the Relationship an Organization Has With Its Data

Keeping Sovereignty at the Center

Interested in how AI can fit into case management without losing sight of data control? Learn more about RiteTrack Assistant and how we’re approaching AI within RiteTrack.

Learn more about RiteTrack Assistant

The post AI and Tribal Data Sovereignty: Why Control Matters appeared first on Handel IT.

Child Care Reporting Starts Long Before the Report Is Due

Tiffany Edmonds — Fri, 18 Sep 2026 07:11:16 +0000

For Child Care programs, reporting may happen at specific times throughout the year, but the information behind those reports is being created every day. Every application processed, eligibility decision made, provider record updated, subsidy recorded, and document added becomes part of the bigger picture of the program. When that information is spread across spreadsheets, folders, separate databases, or individual staff processes, reporting can quickly become a project of its own. Better Tribal child care data management starts much earlier. It starts with keeping the information staff use every day organized in a way that also supports the reporting they will eventually need to complete.

Better Reporting Starts Before the Deadline

It is easy to think about reporting as something that happens at the end of a quarter, fiscal year, or reporting period. In reality, good reporting depends on what happens between those deadlines. Staff need to be able to consistently capture information about applications, families, providers, services, payments, and eligibility as the work takes place. When that information is maintained in one centralized system, programs have a much stronger foundation for reporting later. Instead of piecing information together when a report is due, staff can work from records that have already been maintained throughout the normal course of their work.

That matters for federal reporting, too. The Child Care Technical Assistance Network provides guidance to Tribal Child Care and Development Fund (CCDF) grantees on collecting, managing, analyzing, and reporting child care administrative data, including the ACF-700 Annual Report. For programs responsible for the ACF-700, having accurate information captured throughout the year can make the reporting process much more manageable.

Keep the Application Process Connected

An application can involve much more than a name and an approval or denial. Programs may need to maintain demographic and eligibility information, supporting documentation, application status changes, income verification, subsidy information, parent co-pays, and other details associated with the family.Those pieces are more useful when they remain connected.

A centralized approach to Tribal child care data management allows staff to follow an application from intake through eligibility and ongoing program participation without relying on separate files to understand what has happened along the way. That also creates a clearer history when staff need to revisit a record later.

Provider Information Matters Too

Family and application information is only one side of Child Care program management. Programs also work with provider information, including applications, licensing information, negotiated rates, renewals, documentation, payments, and services a provider may offer. Keeping those records organized can help staff see the relationship between the families receiving assistance and the providers delivering care.

It also reduces the need to maintain separate tracking methods simply because the information belongs to a different part of the program. The goal is not just to put more information into a database. It is to make sure the information staff need is organized in a way that makes sense for the work they are doing. Support should be part of that picture as well. When a workflow changes, a report needs to be updated, or staff have questions, there should be a clear process for addressing it. A system becomes much more valuable when organizations are not left to figure out every technical issue on their own.

That is the kind of foundation organizations should be looking for: a system that is organized, adaptable, supportable, and built to keep working as the organization grows and changes.

Documents Should Be Easy to Find

Child Care programs can accumulate a significant amount of supporting documentation. Application materials, receipts, letters, income verification, provider licensing documents, and renewal information all need to remain connected to the appropriate records. When those documents live in separate folders or locations, even a simple question can turn into a search. Keeping documents alongside the program information they support gives staff a more complete view of a family, application, or provider without having to move between multiple systems. That becomes especially important when information needs to be reviewed later for reporting, program monitoring, or internal follow-up.

Make the Information Useful Before Reporting Season

Reporting is one important reason to improve data management, but it should not be the only one. The same information programs collect for reporting can also help staff understand what is happening within the program throughout the year.

How many applications are being received?
Where are applications in the process?
What subsidy and co-pay information has been recorded?
What payments are associated with providers?
Are required documents available?

When program information is consistently captured and organized, staff do not have to wait for a reporting deadline to start answering those kinds of questions. The data becomes useful for everyday program management, not just compliance.

From Application Through Reporting

That is the approach behind RiteTrack for Child Care.

RiteTrack brings application management, eligibility and demographic information, documentation, subsidy and co-pay information, provider records, licensing information, renewals, provider payments, and other Child Care program information into one configurable system. The system also supports ACF-700 reporting, allowing programs to generate reports using information already maintained through their day-to-day work. RiteTrack also supports P.L. 102-477 reporting related to child care and development activities.

Rather than treating reporting as a separate process, the goal is to connect it to the work staff are already doing.

For Tribes looking beyond a single department, RiteTrack can also be used as a standalone solution or integrated across multiple Tribal programs, helping organizations centralize information while configuring each program around its own workflows and needs.

Because when the information is organized from the beginning, reporting does not have to start with tracking down spreadsheets, documents, and disconnected records.

It starts with the data your program has been building all along.

See How RiteTrack Supports Child Care Programs

The post Child Care Reporting Starts Long Before the Report Is Due appeared first on Handel IT.

How RiteTrack Assistant Helps Turn Information Overload Into Actionable Insight

Tiffany Edmonds — Thu, 17 Sep 2026 15:59:44 +0000

Case management systems are designed to capture information, and over time, that information builds up. Case notes document interactions and changing circumstances. Service histories show what support has been provided. Reports help programs understand activity and outcomes. Dashboards can highlight important information at a glance. Depending on the program, staff may also be managing demographic information, deadlines, eligibility details, court activity, assessments, referrals, payments, program participation, or other case-specific data.

All of that information serves a purpose. But as the amount of data within a system grows, another challenge emerges: helping users quickly understand what is relevant to the work in front of them. That is one of the areas where AI assistance can become useful.

RiteTrack Assistant is an AI case management assistant being introduced within RiteTrack to help users interact with information already available in their case management environment. Rather than treating AI as a separate destination or another technology staff have to learn how to fit into their work, the goal is to provide assistance where that work is already happening. The emphasis is not on replacing the information within RiteTrack. It is on helping users make better use of it.

The Challenge Is Not Always a Lack of Data

Public-sector and Tribal programs often spend significant time collecting information because that information is necessary for delivering services, documenting activity, maintaining case histories, and completing required reporting. The challenge is that more information does not automatically mean more clarity.

Consider case notes. A single case may contain months or years of documentation from multiple interactions. Each note may be important, but reviewing a lengthy history to understand what has happened can take time.

The same is true at a broader level. A program may already have valuable information available for dashboards and reports, but users may not always know which views of that information would be the most useful to them.

A case management system should not simply become a place where information accumulates. The information within it should also help staff understand their work. RiteTrack Assistant is intended to help bridge that gap.

Helping Staff Make Sense of Case Information

Case notes are an important part of many case management environments. They can document services provided, conversations with clients, follow-up activity, changes in circumstances, progress, concerns, and other information relevant to a case.

They can also become extensive.

RiteTrack Assistant can help summarize case notes, giving users another way to review the information that has already been documented within RiteTrack. This is one example of how an AI case management assistant can help users navigate a large amount of existing information without replacing the underlying record.

That does not make the original notes less important. A summary is not a replacement for the underlying record, and it should not replace professional review when the details matter. Instead, summarization can provide a useful starting point.

For someone returning to a case after time away, reviewing a long case history, or trying to get oriented to recent activity, a summary can help bring important information into a more manageable view before the user decides where additional review is necessary. The goal is not to remove people from the process. It is to help people navigate the information available to them.

Finding More Useful Ways to View Data

Dashboards can provide staff with an at-a-glance view of information that matters to their work. But what matters can vary significantly between programs—and even between users within the same program.

A program administrator may be interested in different information than a caseworker. Court staff may need a very different view than probation staff. A TANF or 477 program may focus on different activity than a victim services or Elder Support program.

RiteTrack Assistant can help users identify dashboard tiles they may find useful based on the data available to them. The value here is not simply having more dashboard tiles. It is helping users think about which information could be useful to surface more prominently.

When organizations collect significant amounts of data, some of the most useful information may already exist within the system but may not be part of the user’s everyday view. AI assistance can help make those possibilities easier to discover.

Connecting Available Data to Reporting

Case management systems can contain a wide range of information, but users may not always know which reports could help answer a particular operational question or provide additional insight into their program.

RiteTrack Assistant can suggest reports users may find useful based on the data available within RiteTrack. Again, the goal is not for AI to decide what a program should measure. Programs still determine which information matters, which outcomes they are responsible for tracking, and which reporting requirements they must meet. Instead, AI assistance can help users better understand the reporting options that may already be available to them.

For example, a user who knows what they want to understand but is unsure how to get there may benefit from assistance identifying a report that uses the information their program is already collecting.

That can help turn reporting from something users simply produce into something they can use to better understand their work.

Making AI Part of the Existing Workflow

One of the biggest considerations when introducing any new technology is how it fits into day-to-day operations.

Staff in courts, Tribal programs, probation departments, juvenile facilities, victim services programs, social service agencies, and other public-sector organizations already work across complicated processes. Their technology should reduce unnecessary friction rather than create another disconnected step.

That is why the idea of an embedded AI case management assistant is important. RiteTrack Assistant exists within RiteTrack and can interact with RiteTrack data. It can also provide general AI assistance, allowing users to work with an AI assistant without treating it as an entirely separate tool from the case management environment where much of their work already occurs. And because not every question can or should be answered by AI, RiteTrack Assistant can escalate unresolved RiteTrack-specific questions to the customer’s project manager. That reflects a broader principle we believe is important when introducing AI into case management: technology should know where its role ends.

Information Still Requires Context

AI can make information easier to navigate, but information alone never tells the entire story. A summarized case history does not understand a client relationship the way a caseworker does. A suggested report does not understand every operational priority of a program. A dashboard cannot capture every circumstance influencing a person, family, case, or community. That context remains with the people doing the work. For organizations managing sensitive information and serving people in complex circumstances, that distinction is especially important. Broader guidance, including the NIST AI Risk Management Framework, also emphasizes the importance of managing AI risk and trustworthiness throughout the use of AI systems.

AI assistance can organize information, summarize what has been documented, and help users discover ways to view their data. Staff still bring the experience, judgment, relationships, and program knowledge necessary to determine what that information means and what should happen next. Used that way, AI becomes less about automation for its own sake and more about helping people work with information more effectively.

From More Information to More Useful Information

Case management technology has made it possible for organizations to maintain increasingly detailed records of their work. The next challenge is helping people use that information well.

RiteTrack Assistant is designed to help users work with the information already available to them—whether that means summarizing case notes, discovering dashboard tiles that could provide a useful view of their data, identifying reports that may be relevant, or accessing general AI assistance from within RiteTrack. As an AI case management assistant, its role is not to replace the people who understand the cases, programs, communities, and responsibilities behind the data. It is to help those people work more effectively with the information already available to them. It is about making the information they have already worked hard to collect easier to navigate and use.

Because ultimately, the value of a case management system is not measured by how much information it can hold. It is measured by how effectively that information can support the people doing the work.

Learn More About How RiteTrack Assistant Can Help Your Program

The post How RiteTrack Assistant Helps Turn Information Overload Into Actionable Insight appeared first on Handel IT.

One Family, Many Programs: Why Coordinated Tribal Services Matter More Than Ever

Josh Becker — Tue, 15 Sep 2026 20:25:05 +0000

A family doesn’t experience life one government program at a time. A child involved with a Tribal child welfare program may also have a parent receiving employment assistance. That same family may need housing support, transportation, behavioral health services, childcare, or help navigating the Tribal court system. To the family, those needs are connected. Inside government, they are often handled by separate programs. That isn’t necessarily a flaw in the system. Tribal programs have different funding sources, eligibility requirements, reporting obligations, confidentiality rules, and responsibilities. In many cases, there are very good reasons for keeping certain information separate.

Still, after working with Tribal governments for many years, I think there is an important question worth asking: how easy is it for a family that needs help to actually navigate all of the services available to them? That question feels especially relevant right now.

In July, Senators Lisa Murkowski and Brian Schatz introduced the bipartisan Native Children’s Commission Implementation Act of 2026. The legislation grew out of years of work by the Alyce Spotted Bear and Walter Soboleff Commission on Native Children and covers a wide range of issues affecting Native youth and families, including child welfare, juvenile justice, housing, education, childcare, workforce development, nutrition, physical health, and behavioral health.

The legislation is still working its way through the process, and no one knows what the final outcome will be. But I think the broader idea behind it is important regardless of what happens in Congress.

Families don’t fit neatly into departmental boundaries, and that is why coordinated tribal services matter more than ever. A parent may walk into a Tribal office looking for help with one issue, but during that conversation it becomes clear there are several other challenges affecting the household. Maybe they recently lost a job. Maybe transportation is preventing them from getting to work. Maybe housing has become unstable. Maybe their children qualify for additional services. The staff member helping that person may know other programs are available, but that doesn’t always mean the connection is easy to make. The family may have to visit another office, fill out another application, provide the same information again, or explain their situation to a new person from the beginning. The first program may have no way to know whether the referral resulted in services.

Most of these barriers weren’t intentionally created. They are often the result of programs developing separately over many years. Federal funding plays a big role in that. Tribal governments may receive funding from several different agencies to serve many of the same families, while each funding source comes with its own rules, deadlines, eligibility requirements, and reporting obligations. The challenge for Tribal staff is taking all of those separate requirements and turning them into an experience that makes sense for the person sitting across the desk.

I also think it is important to be careful when we talk about tribal service coordination. Better tribal service coordination does not mean every department should have access to every piece of information. There are records involving child welfare, courts, domestic violence, behavioral health, finances, and other sensitive matters that absolutely need appropriate protections. Tribal Nations also have their own laws, policies, and expectations governing how information should be handled. The goal should not be to eliminate every wall between programs. Some walls are there for a reason. The opportunity is to figure out where separation protects people and where it simply makes it harder to serve them.

Sometimes better coordination may be as simple as allowing an employee to see that another program is already helping a family without seeing the confidential details of that case. In other situations, it may mean creating a better referral process between departments or giving leadership a broader, aggregated view of community needs. That broader view can be extremely valuable. One Tribal department may see an increase in requests for food assistance. Another may see more families struggling with housing. Another may see growing demand for behavioral health services. If those programs are viewed completely independently, those may look like three separate issues. Taken together, they may tell a much bigger story about what is happening in the community. That kind of information can help leadership decide where resources are needed, identify gaps in services, pursue funding, and plan for the future.

Technology can help with some of this, but I don’t believe technology should determine how a Tribal government operates. The opposite should be true.

The Tribe should decide how its programs work together, what information can be shared, what needs to remain separate, and who should have access. The technology should be flexible enough to support those decisions. That is something I have come to believe strongly through our work with Tribal governments. There is no single model that will work for every Nation, and there shouldn’t be.

Some Tribes may want programs to remain largely independent. Others may want closer tribal service coordination across several departments. Some may create a more integrated family-services approach. Those decisions belong to the Tribe.

For Nations interested in looking at this issue, I don’t think it necessarily has to begin with a major technology project or organizational restructuring. It could begin with a much simpler exercise: follow the experience of a family that comes to the Tribe for help. Where do they have to provide the same information more than once? Where are employees relying on phone calls, email, spreadsheets, or personal relationships to make referrals? Where do confidentiality rules appropriately prevent information sharing? Where are there opportunities to make things easier without compromising privacy? Those questions can uncover a lot.

There is a great deal of discussion right now about how the federal government, Tribal Nations, and service providers can improve outcomes for Native children and families. Programs and funding will continue to evolve, but I think one principle should remain consistent.

The people being served should be at the center of the system. A child is not simply an ICWA case. A parent is not simply a TANF case. A survivor is not simply a victim-services case. They are people and families whose lives often cross many of the boundaries government programs use to organize services. Those boundaries may be necessary, but they shouldn’t make it unnecessarily difficult for people to get help. If Tribal governments can make those connections easier while still protecting sovereignty, privacy, and program integrity, that seems like progress worth pursuing.

How RiteTrack Can Help

If your Tribe is looking for ways to improve tribal service coordination across programs while still protecting privacy and program-specific information, RiteTrack can help support that approach.

RiteTrack is configurable to reflect how your programs actually operate, including what information should be shared, what should remain separate, and who should have access.

Learn more about how RiteTrack supports Tribal programs.

The post One Family, Many Programs: Why Coordinated Tribal Services Matter More Than Ever appeared first on Handel IT.