Navigating Parenting Orders in High-Conflict Cases

Australian family law, guided by the Family Law Act 1975 (Cth) (“Act”), addresses complex issues related to high conflict parenting orders. These orders determine child custody, visitation, and parental responsibilities. In recent years, several significant cases and legislative changes have shaped the court’s approach in managing these disputes, particularly where parental conflict is high.

The Role of Parenting Orders

Parenting orders are decisions made by the Federal Circuit and Family Court of Australia (“Court”), specifying the arrangements for a child’s care, including who the child will live with and how much time they will spend with each parent. The primary consideration in these decisions is the “best interests of the child,” as mandated by section 60CA of the Act. The Act prioritises two factors: the benefit of the child maintaining a meaningful relationship with both parents and the need to protect the child from harm, including exposure to family violence.

Challenges in High-Conflict Cases

High-conflict cases often involve allegations of violence, abuse, or severe parental alienation, creating a challenging environment for courts to navigate. A landmark case, M v M (1988) 166 CLR 69, highlighted the Court’s duty to intervene in such situations to protect the child’s welfare, even if it means limiting a parent’s contact with the child. This decision reinforced the principle that child safety is paramount, even at the cost of reducing contact with one parent.

Legislative Changes and Their Impact

The Family Law Amendment (Shared Parental Responsibility) Act 2006 promoted shared parental involvement but also introduced complexities in high-conflict situations. In Goode v Goode (2006) FLC 93-286, the Full Court clarified that shared parental responsibility does not imply equal time with both parents, particularly when conflict or risk of harm is present.

Further changes came with the Family Law Amendment (Family Violence and Other Measures) Act 2011, which emphasised protecting children from harm, responding to concerns that the 2006 reforms may have exposed children to unsafe situations. This amendment aligned with the principles established in M v M (1988), stressing child safety over shared time.

Future Directions

The Family Law Amendment Bill 2023 proposes further reforms to prioritise child safety and well-being. It suggests clearer guidelines for judges to assess potential risks in high-conflict situations and incorporates more therapeutic, non-adversarial approaches to resolving disputes. These proposed changes aim to ensure that the child’s best interests remain the focus of all family law proceedings.

Conclusion

The approach to parenting orders in high-conflict cases under Australian family law has significantly evolved. The Court continues to prioritise child safety over shared parenting time, reflecting a commitment to safeguarding children’s welfare in all circumstances. Future reforms are likely to enhance this focus, ensuring that family law proceedings better protect the most vulnerable.

If you require advice regarding a family law matter, contact us here.

Our family lawyers act in high-conflict parenting matters.

Related Articles

- End", entire site, priority AFTER 8417. * * What it does: * 1. On load, reads gclid + utm_* from the URL and stores them in a * first-party cookie for 90 days (only overwrites gclid when a new one * is present, so a later organic visit does not wipe the paid click). * 2. Appends those params to every calendly.com link and to any inline * Calendly embed, so a completed booking carries them into Calendly and * onward to the RedRain integration. */ (function () { 'use strict'; var COOKIE = 'jm_attr'; var MAXAGE = 60 * 60 * 24 * 90; // 90 days var UTM_KEYS = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_content', 'utm_term']; function readCookie(name) { var m = document.cookie.match('(?:^|; )' + name + '=([^;]*)'); return m ? decodeURIComponent(m[1]) : ''; } function writeCookie(name, val) { document.cookie = name + '=' + encodeURIComponent(val) + '; path=/; max-age=' + MAXAGE + '; SameSite=Lax; Secure'; } // ---- 1. capture from URL, merge with stored ---- function capture() { var url = new URLSearchParams(window.location.search); var stored = {}; try { stored = JSON.parse(readCookie(COOKIE) || '{}'); } catch (e) { stored = {}; } var incomingGclid = url.get('gclid'); if (incomingGclid) { stored.gclid = incomingGclid; } // only overwrite on a fresh click UTM_KEYS.forEach(function (k) { var v = url.get(k); if (v) { stored[k] = v; } }); // if a gclid arrived but no utm_source, tag the source so RedRain is not blank if (incomingGclid && !stored.utm_source) { stored.utm_source = 'google'; stored.utm_medium = 'cpc'; } if (Object.keys(stored).length) { writeCookie(COOKIE, JSON.stringify(stored)); } return stored; } var attr = capture(); if (!attr || (!attr.gclid && !attr.utm_source)) { return; } // nothing to forward // ---- 2. build a query string for Calendly ---- function calendlyParams() { var p = new URLSearchParams(); UTM_KEYS.forEach(function (k) { if (attr[k]) { p.set(k, attr[k]); } }); // carry the raw gclid too. utm_content is the safe carrier RedRain can map // if its Calendly field mapping does not expose a native gclid slot. if (attr.gclid) { p.set('gclid', attr.gclid); if (!p.get('utm_content')) { p.set('utm_content', 'gclid:' + attr.gclid); } } return p.toString(); } function withParams(href) { if (!href || href.indexOf('calendly.com') === -1) { return href; } var qs = calendlyParams(); if (!qs) { return href; } // don't double-append if (href.indexOf('utm_source=') !== -1 || href.indexOf('gclid=') !== -1) { return href; } return href + (href.indexOf('?') === -1 ? '?' : '&') + qs; } // ---- 3a. rewrite anchor links (covers the popup/booking click path) ---- function rewriteLinks() { var links = document.querySelectorAll('a[href*="calendly.com"]'); for (var i = 0; i < links.length; i++) { var a = links[i]; if (a.getAttribute('data-jm-attr') === '1') { continue; } a.setAttribute('href', withParams(a.getAttribute('href'))); a.setAttribute('data-jm-attr', '1'); } } // ---- 3b. rewrite inline embeds. Must run before Calendly widget.js reads // data-url; if the widget already initialised, re-point and let it // re-read on next interaction. Most bookings go via the link path. ---- function rewriteEmbeds() { var w = document.querySelectorAll('.calendly-inline-widget[data-url]'); for (var i = 0; i < w.length; i++) { var el = w[i]; if (el.getAttribute('data-jm-attr') === '1') { continue; } el.setAttribute('data-url', withParams(el.getAttribute('data-url'))); el.setAttribute('data-jm-attr', '1'); } } function run() { rewriteLinks(); rewriteEmbeds(); } if (document.readyState === 'loading') { document.addEventListener('DOMContentLoaded', run); } else { run(); } // catch links injected later (Elementor popups, lazy content) if (window.MutationObserver) { var mo = new MutationObserver(function () { rewriteLinks(); }); mo.observe(document.documentElement, { childList: true, subtree: true }); } })();