{"id":1003,"date":"2026-07-01T15:09:56","date_gmt":"2026-07-01T09:39:56","guid":{"rendered":"https:\/\/legalfirms.in\/magazine\/?p=1003"},"modified":"2026-07-01T15:09:56","modified_gmt":"2026-07-01T09:39:56","slug":"the-ai-defence-will-not-save-you","status":"publish","type":"post","link":"https:\/\/legalfirms.in\/magazine\/2026\/07\/01\/the-ai-defence-will-not-save-you\/","title":{"rendered":"The AI Defence Will Not Save You"},"content":{"rendered":"<p>&#039;The tool generated it&#039; is becoming a common explanation. Courts have already signalled that it is not a defence. Responsibility stays with the person.<\/p>\n<p>A new excuse has entered disputes, and it is worth understanding why it fails. As AI tools spread into everyday work, people increasingly explain a mistake by pointing at the machine. The draft cited a fake case because the software produced it. The message went out because an automated system sent it. The document was wrong because the tool drafted it. The instinct is to treat the tool as the responsible party. The law does not.<\/p>\n<p>The Person Who Acts Is Accountable<\/p>\n<p>The clearest signal came from the courts themselves. When the Supreme Court addressed lawyers filing fabricated, AI-generated citations, it did not treat the AI as the wrongdoer. It treated the person who filed without checking as responsible, and called the conduct misconduct rather than an innocent error. The principle generalises well beyond lawyers. If you put your name to something, you own its contents, including the parts a machine produced.<\/p>\n<p>Convenience Does Not Transfer Liability<\/p>\n<p>This matters in ordinary settings too. An employee who sends an automated or AI-drafted communication that is misleading, abusive or defamatory does not escape responsibility because a tool helped write it. A person who relies on an AI summary of a contract and acts on it cannot shift the loss to the software when the summary was wrong. Using a tool is a choice. The responsibility for that choice, and for verifying its output, stays with the user.<\/p>\n<p>Intent Is Not the Whole Story<\/p>\n<p>As earlier issues have noted, in many situations intent is only one part of liability. Saying you did not mean for the AI to invent something, or did not realise the output was false, addresses your state of mind but not the effect of your action. Context, the duty to check, and the consequences of what you filed or sent all weigh in. The reasonable expectation now forming is simple: if you use these tools, you are expected to verify what they produce.<\/p>\n<p>Disclosure Is Becoming the Norm<\/p>\n<p>The draft court rules point toward a future where AI use must be disclosed, not hidden. That is a sensible posture to adopt early, well beyond courtrooms. In professional work, being transparent about where a tool was used, and demonstrating that a human reviewed the output, is becoming the responsible default. Quiet reliance on a tool you did not check is precisely the behaviour the new rules are designed to discourage.<\/p>\n<p>The Old Boundary Has Moved Again<\/p>\n<p>Recent issues described how the line between private and public conduct has shifted in the digital age. The arrival of AI moves another line. People are discovering that delegating a task to a machine does not delegate the responsibility for it. The work may be automated. The accountability is not. Anyone using these tools in serious matters would do well to internalise that before a dispute makes the point for them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#039;The tool generated it&#039; is becoming a common explanation. Courts have already signalled that it is not a defence. Responsibility stays with the person. A new excuse has entered disputes, and it is worth understanding why it fails. As AI tools spread into everyday work, people increasingly explain a mistake by pointing at the machine.&hellip;<\/p>\n","protected":false},"author":2,"featured_media":1004,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[33,74],"tags":[43],"thb-sponsors":[],"class_list":["post-1003","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-33","category-july","tag-his-rights"],"jetpack_featured_media_url":"https:\/\/legalfirms.in\/magazine\/wp-content\/uploads\/2026\/07\/The-AI-Defence-Will-Not-Save-You-1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/posts\/1003","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/comments?post=1003"}],"version-history":[{"count":1,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/posts\/1003\/revisions"}],"predecessor-version":[{"id":1027,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/posts\/1003\/revisions\/1027"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/media\/1004"}],"wp:attachment":[{"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/media?parent=1003"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/categories?post=1003"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/tags?post=1003"},{"taxonomy":"thb-sponsors","embeddable":true,"href":"https:\/\/legalfirms.in\/magazine\/wp-json\/wp\/v2\/thb-sponsors?post=1003"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}