In short
What is the difference between MARAM, CRAF and DVSAT?
MARAM, the Family Violence Multi Agency Risk Assessment and Management framework, is Victoria's structured approach, defining responsibility levels for different practitioner types and prescribing common risk indicators, protective factors and information sharing obligations. The Common Risk and Safety Framework, used in New South Wales, and the Domestic Violence Safety Assessment Tool, DVSAT, used by NSW Police and referral partners, serve a similar function with different indicator sets and thresholds. Konetic One models each framework's indicator set, scoring logic and required actions as configuration, so a service operating under one jurisdiction's model gets the correct tool without a bespoke build, and a service crossing borders can run more than one framework on the same client record without duplication.
What this has to solve for
- 1
Assessment lives in a document, not the record
A worker completes a MARAM aligned assessment as a Word document, saves it to a folder, and the risk level it produced never reaches the client's actual case file, so the next worker starts from nothing.
- 2
Risk level goes stale
A risk level set six months ago is still the number showing on a dashboard, because nothing in the workflow prompts a reassessment when circumstances change, a court date passes, or a perpetrator is released.
- 3
Different roles, different obligations, one form
MARAM sets different assessment responsibilities for specialist family violence practitioners, generalist services and organisations with a lower level of responsibility. A single generic form cannot reflect that without becoming unusable for the people who only need a screen.
- 4
No defensible trail
When a serious incident review or coronial process asks what was known and when, services need to reconstruct an assessment history from memory and scattered paper, months or years after the fact.
Configure the framework your jurisdiction actually uses
Konetic One does not force a single national risk model. The assessment form, indicator list, weighting and output categories are configured per framework, so a Victorian specialist family violence service runs a MARAM aligned comprehensive assessment with the correct indicators of serious risk, while a NSW partner service runs the Common Risk and Safety Framework or a DVSAT screen, and both produce a structured risk level that lands on the same underlying client record architecture.
Where an organisation operates across jurisdictions, or works alongside police, courts and child protection services that use a different tool again, the platform lets each assessment type sit against the client's timeline in the tool that produced it, with a plain language summary that a worker from a different service can read without needing to be trained in someone else's framework.
- Framework specific indicator sets and scoring logic held as configuration, not custom code
- Responsibility level determines which assessment a worker's role can complete
- Comprehensive and initial or screening assessments both modelled, matching real practice
- Cross jurisdiction clients can carry more than one framework's assessment history
Make the current risk level impossible to miss
A risk level that only exists inside a completed assessment form is invisible in daily practice. Konetic One promotes the current risk level, whichever framework produced it, to the client banner, the worker's caseload list and any handover note, with the date it was set and who set it.
When risk indicators change materially, such as a change in the perpetrator's access, a pending intervention order hearing, or a disclosure of escalating controlling behaviour, the worker records the change against the client and the platform prompts a reassessment rather than leaving the old level standing unchallenged.
| Where it appears | What it shows | Who sees it |
|---|---|---|
| Client banner | Current risk level, date set, framework used | Any worker opening the client record |
| Caseload dashboard | Risk level distribution across an active caseload | Case managers, team leaders |
| Handover note | Risk level and any active safety flags | Next shift or on call worker |
| Reassessment worklist | Assessments due against the framework's review cadence | The assigned worker and supervisor |
Keep the assessment history intact and explainable
Every completed assessment is retained as its own dated record, not overwritten by the next one. A supervisor or an external reviewer can see the full sequence, comprehensive assessment, screening reassessment, incident triggered reassessment, in order, with the indicators recorded at each point and the risk level each one produced.
That sequence is what a serious incident review, a coronial brief or an internal quality audit actually needs. Konetic One is not producing that evidence after the fact, it is simply not deleting the trail that the framework already generates.
- Every assessment version retained with a timestamp and completing worker
- Risk level change log separate from the narrative case notes
- Assessment PDF export formatted to match the source framework's own template
- Supervisor sign off recorded against comprehensive assessments where the framework requires it