Children's Advocacy Centre Software: Coordinating Five Agencies Around One Child Without Losing the Record

One child, five agencies, five systems, one record that has to survive cross examination

A referral comes in. Within days a forensic interviewer, a detective, a child protection investigator, a prosecutor, a medical provider, a mental health clinician and a victim advocate will each touch the same child's case. They work for different organisations. They have different legal authorities, different confidentiality obligations and different record systems. Your centre exists specifically to coordinate them, and the coordination itself has to be documented, because your accreditation depends on demonstrating that the team actually functioned as a team.

The operational reality in most centres is a shared calendar, a case tracking database, a whiteboard, a stack of case review agendas, and email threads that contain details nobody should be emailing. Case review happens on a schedule, decisions are captured in someone's notes, and the follow up items from three months ago are wherever that person filed them. When a prosecutor asks two years later what the team decided about a case and when, the answer is a search through minutes.

The second reality is that this record is evidentiary. A forensic interview recording is potential evidence in a criminal prosecution. Who accessed it, when, whether a copy was made, and who received it are questions that can be asked in court. A shared drive folder with permissions somebody set up in 2019 is not an acceptable answer, and every centre director knows it.

What NCAtrak covers, and when a centre outgrows it

NCAtrak was built for this model, understands multidisciplinary team case tracking and the reporting accredited centres need, and is used across the field. If you run a single centre with one partner set, use it. A custom build would take money away from services to reproduce something that already exists and already fits.

Centres run past it in identifiable situations. The first is scale and geography: a centre covering six counties works with six sheriff's offices, several police departments, multiple child protection regions and two prosecutor offices, each with different practices and different access needs, plus satellite interview sites. Managing that as a single flat case list means access control becomes a manual discipline.

The second is clinical integration. Hospital based programmes need the medical evaluation to live in or connect to the health record, which brings clinical interoperability and health privacy requirements that a standalone case tracker does not attempt.

The third is a state chapter deploying consistently across member centres, where the value is comparable data and shared accreditation evidence across the state rather than any single centre's workflow. That is the situation where the economics of a build actually work, because the cost is spread and the benefit is aggregate.

Problem one: access control across organisations that are not yours

A detective should see the investigative record for their case. They should not see the mental health treatment notes. A clinician needs the clinical record and enough case context to work safely, not the investigative detail. A prosecutor needs the case file for cases they are handling. Child protection has statutory access to their own material and negotiated access to the rest.

Build this as a model, not as permissions applied case by case. Each agency has a role definition with a data scope. Each person's access to a specific case derives from their assignment to that case, and it ends when their involvement ends rather than when someone remembers to remove it. Sensitive record categories, particularly mental health and medical, sit behind an additional boundary that requires an explicit basis to cross. And every access to a case record is logged with user, time and record type, because that log is what you produce when access is questioned.

Getting the offboarding path right matters more than the onboarding path. Detectives transfer, prosecutors move offices, contract clinicians finish their term. A system where access decays automatically with case involvement is materially safer than one that depends on someone sending an email.

Problem two: recordings and chain of custody

A forensic interview recording moves from the recording system to storage, then possibly to a prosecutor, a defence disclosure process, and an appellate record years later. What has to be provable is that the file is the original, that any copy is accounted for, and that access is documented.

The technical requirements are unglamorous and specific. Compute a hash at ingest and verify it on every retrieval so integrity is demonstrable rather than assumed. Store recordings encrypted with keys your organisation controls. Make every view, download and transfer an immutable log entry that includes the recipient and the purpose. Support a formal release workflow so a copy provided to a prosecutor is a recorded event with an authorisation behind it. Retain according to your state's requirements and your policy, with legal hold that suspends any deletion, and confirm those retention periods with your counsel rather than with any general guidance.

Do not let a build put recordings in a general purpose file sharing service because it is convenient. That decision is the one most likely to be raised as a problem later.

Problem three: case review has to be a record, not a meeting

Accreditation standards require documented multidisciplinary team case review, and the evidence question is not whether reviews happened but whether every case was reviewed within your stated timeframe with the required disciplines present. A build should generate the review agenda from cases meeting your criteria, record attendance by discipline, capture decisions and action items with owners and due dates, and carry unresolved items to the next review automatically.

The reporting that falls out of this is what makes an accreditation site visit straightforward: cases reviewed within timeframe, discipline attendance rates, open action items by age. Those figures are hard to assemble from meeting minutes and trivial to produce from structured records, and the difference is a week of a director's time every accreditation cycle.

Problem four: what happened to the case afterwards

Centres are regularly asked about prosecution outcomes, and most cannot answer well, because the outcome happens in a court system they do not control and often months or years after the child's services concluded. Capturing charge status, disposition and sentencing depends either on a periodic exchange with the prosecutor's office or on a person checking court records.

The honest design is to make outcome a structured field with a source and a date, updated through whatever mechanism your partners will actually support, rather than pretending an automatic integration exists where it does not. Even a manual quarterly update from the prosecutor becomes valuable once it is structured and joinable to case characteristics, because it lets your centre answer questions about its work with evidence instead of impressions.

Cost, timeline and what drives it

In Digital Heroes delivery experience, a first release covering the case record with cross agency access control, interview scheduling, recording chain of custody and case review documentation runs $65,000 to $140,000 and ships in 12 to 18 weeks. Adding medical and mental health tracking, victim advocacy services, prosecution outcomes, accreditation evidence packs, satellite sites and any clinical system integration takes the programme to $160,000 to $340,000 over 8 to 13 months.

Price drivers: the number of partner agencies and how much their access rules differ. Satellite and mobile interview sites, which bring connectivity and device management questions. Clinical integration for hospital based programmes, which is the single largest cost multiplier here. Security work, which should include penetration testing before go live and should not be trimmed. Multi centre deployment for a state chapter, which is where the cost per centre falls dramatically. And migration from an existing case system, where historical records and recordings both need to move with their integrity intact.

What keeps it down: launching with the case record, scheduling and case review, keeping outcomes and clinical integration for later phases, and using established managed infrastructure with strong controls rather than anything bespoke.

When buying is the right decision

Buy if you are a single accredited centre with one county's partner agencies and standard reporting. NCAtrak exists for exactly this and the money is better spent on interviewers and therapists. We would tell you the same thing if you called us, and we have.

Build when a state chapter wants one consistent system across member centres with comparable data, when a centre covers multiple counties with materially different partner agencies and satellite sites, when a hospital based programme has to integrate the medical evaluation with clinical systems, or when your access control has become a manual discipline that depends on someone remembering to remove a detective who transferred last spring. The trigger is cross organisational complexity, not case volume.

How to choose a developer

Ask how they would model access so that a detective assigned to a case sees the investigative record and never the mental health notes, and so that access ends when the assignment ends. If the answer is user roles and case permissions set manually, ask what happens when the detective transfers.

Ask what they would do to make a recording's integrity provable two years later. Hashing at ingest, verification on retrieval, immutable access logs and a formal release workflow should come back without prompting.

Ask whether they have built systems where records may be produced in a criminal proceeding, and how that shaped their logging and retention design.

Ask specifically what they will do for security review before go live, and require that no real case data appears in any development or test environment. Then settle ownership before kickoff: the repository, the cloud accounts and the right to hire another firm should be yours in writing. At Digital Heroes the client owns the code from the first commit, and for records tied to child protection and criminal prosecution, dependence on a supplier for access is not an acceptable position for a centre to be in.