Session data entered twice
A case manager logs a contact in the case file, then someone else re-enters the same contact into a DEX upload spreadsheet weeks later, often losing detail in translation.
The DSS Data Exchange is the reporting backbone for most Commonwealth community services funding, including SETS. Providers that treat DEX as a monthly export exercise spend days reconciling client counts against session logs. Providers that build it into the case record spend minutes.
The DSS Data Exchange, known as DEX, is the data collection and reporting system the Department of Social Services uses across most of its community grants programs, including SETS. Providers report client details, service contacts called sessions, and for some programs a partnership approach outcomes tool called SCORE. Reports are due on a quarterly cycle through the DEX portal or via a compatible upload. Konetic One builds the session and client records DEX requires as case managers work, then produces a submission ready extract.
What providers tell us
Every case contact, whether a full case management session, a brief phone check in, or a group activity attendance, is captured in the format DEX expects, with service type, delivery mode and duration recorded at the point of contact rather than reconstructed afterwards.
Client demographic fields required by DEX, country of birth, main language, visa pathway, Indigenous status, are captured once at intake and reused across every program the client touches, rather than asked again for each funding stream.
For programs using the partnership approach, the SCORE outcomes tool is presented inside the case management workflow at the points DEX expects it, typically at commencement and at exit or review, so the case manager and client complete it as part of the conversation about progress rather than as an administrative add on.
Because SCORE responses sit against the same goal plan the case manager is already using, the outcome data reflects the actual work rather than a best guess filled in under deadline pressure.
| Point in the case | SCORE activity | Who completes it |
|---|---|---|
| Commencement | Baseline domain scores against presenting circumstances | Client with case manager |
| Review | Optional interim score where the case is long running | Client with case manager |
| Exit | Final domain scores, closure reason | Client with case manager |
The DEX extract generated from Konetic One is validated against current DEX field rules before it leaves the building, and the exact file submitted is retained. If a program review or an audit asks why a figure looks a certain way, the underlying case record is one click away, not a forensic exercise in an old spreadsheet.
Multi program organisations can generate DEX extracts per organisation identifier and per program without cross contaminating activity from a neighbouring contract.
Questions
How Konetic One holds needs assessment, goal plans, referrals and case notes for Settlement Engagement.
ReadTrack community strengthening activities, employment pathway referrals and refugee health follow up alongside individual settlement case files.
ReadTrack Humanitarian Settlement Program early settlement milestones, visa subclass and eligibility evidence.
ReadWe will map your SETS streams, DEX reporting and language access needs against the platform and show you the record it produces.