Konetic One Australian Community Services Management Platform Logo
Outcomes and funding

DEX SCORE outcomes for family and relationship services

SCORE was designed to be quick. In practice, most services collect it on paper weeks after the session it describes, then key it into the Data Exchange portal under deadline pressure, and it fails validation more often than anyone likes to admit.

At a glance

3
Standard SCORE collection points, intake, review and exit
0
Separate spreadsheets between the session and the DEX upload
Continuous
DEX field validation, not a once off pre-submission scramble

What is SCORE and how does it feed the Data Exchange?

SCORE, the Standard Client Outcomes Reporting Evaluation, is the standardised outcomes tool used across programs reporting into the Australian Government Data Exchange, commonly called DEX. Family and relationship services, family support, Reconnect, Communities for Children and many other programs funded by the Department of Social Services use SCORE to measure client progress against goal areas such as personal and family safety, family functioning, financial resilience and connection to community. Providers score clients at the start, during, and at the close of a support period, and those scores are uploaded to DEX alongside client, case and service activity data to acquit funding. Konetic One captures SCORE inside the session and validates the entire DEX record continuously rather than at the deadline.

What the case file has to hold

Where this breaks down in practice.

  1. 1

    SCORE is collected too late to be useful

    A worker means to score the client at the end of the session but does not get to it until the following week, by which point the score reflects a fading memory rather than the actual conversation.

  2. 2

    Paper forms and a second data entry step

    SCORE recorded on paper has to be transcribed into a system or spreadsheet before it reaches DEX, doubling the effort and introducing transcription errors into a national data collection.

  3. 3

    DEX validation failures at the worst possible time

    Providers discover missing consent flags, incomplete support period fields or mismatched client identifiers when the DEX portal rejects the file, often days before an acquittal deadline.

  4. 4

    SCORE without a story

    A numeric SCORE change is more persuasive to a funder when it sits next to the qualitative case narrative that explains it, but the two are usually stored in entirely separate systems.

SCORE inside the session, not after it

Konetic One presents the SCORE domains relevant to the client's program and goal areas directly inside the session record, so the worker rates progress against personal and family safety, family functioning, or whichever domains apply, while the conversation is fresh. The tool prompts the correct collection point, intake, a defined review point, or exit, based on where the client sits in their support period.

Because the score sits next to the case note that explains it, a supervisor or funder reviewing a client's progress sees the number and the reasoning behind it on the same screen, not in two different systems that have to be manually cross referenced.

  • SCORE domains presented against the client's actual program and goal areas
  • Collection point, intake, review or exit, determined automatically by the support period stage
  • Score sits alongside the session note that explains the change
  • Missed collection points surface on the worker's worklist before the period closes

Validating the whole DEX record continuously

SCORE is only one part of the DEX submission. Client and consent fields, case and support period details, service activity, and outcome fields all have to be complete, correctly coded and internally consistent before an upload will pass. Konetic One runs these checks continuously as records are created, not as a single pre-submission event.

A DEX readiness view shows the proportion of records that would pass validation right now, broken down by the same categories DEX itself checks, so a team leader can close small gaps steadily across the month instead of discovering a wall of errors at acquittal time.

DEX record categories and typical validation issues resolved before upload
CategoryTypical issueResolution point
Client and consentMissing consent to be recorded, incomplete demographic fieldsClient intake record
Case and support periodSupport period left open, referral source missingCase record
Service activitySession recorded outside the support period datesSession record
SCORE outcomesReview or exit score missing after an intake score was recordedClient outcome tab
Statistical linkage keyIncomplete or inconsistent identifying fields across recordsClient profile
DEX record categories and typical validation issues resolved before upload

Reporting that a program manager can actually use

Beyond the upload itself, program managers running family and relationship services need to know how a cohort is tracking against SCORE domains in something close to real time, not only at the end of a funding period. Konetic One aggregates SCORE change across a program, a site or a funding stream, and lets a manager filter by goal area, referral source or demographic group.

This turns SCORE from a compliance obligation into a genuine practice signal. A domain that is not improving across a cohort, for example family functioning in a particular site, is visible early enough for a program manager to ask why, rather than discovered in a annual report review long after the funding period it describes has closed.

  • Cohort level SCORE trend by program, site or funding stream
  • Filter by goal domain, referral source or priority population
  • Historic submissions retained with the exact extract sent to DEX
  • Exportable evidence pack for board or funder reporting

Multiple funding streams, one clean split

Many family and relationship services hold several DSS or state funded programs at once, sometimes delivering similar work under different contracts. Konetic One attaches program and funding line to each case, so activity and SCORE outcomes split correctly for DEX and for any parallel state reporting obligation without a worker needing to remember which spreadsheet a client belongs in.

Questions

DEX SCORE outcomes, answered.

Sign in Book demo