{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Patent Pending Made Simple","title":"32. The Most Important Legal Requirement for Independent Inventors - Enablement","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/dc6252bf\"></iframe>","width":"100%","height":180,"duration":1391,"description":"What does “enablement” really mean in patents — and why does it kill so many applications? Many inventors focus only on novelty, but enablement is just as critical. In this episode, attorneys Samar Shah and Jamie Brophy explain the enablement requirement, why it exists, and how to avoid rejections that can derail your patent.\nHere’s what you’ll learn:\nThe legal standard for enablement: teaching others to make and use your invention without undue experimentation.\nWhy functional claiming (“configured to…”) often triggers enablement problems.\nHow prototypes can help identify weak spots in your disclosure.\nClues that your application might be missing critical detail.\nReal examples: Velcro vs. novel closures, mechanical assemblies, and classic cases like perpetual motion.\nPractical strategies for writing applications that withstand examiner scrutiny.\nWhat to do if you get an enablement rejection — and why prevention is better than cure.\nWhy it matters: A patent isn’t valuable if it can’t survive examination or litigation. Understanding enablement helps inventors, startups, and attorneys write applications that actually protect innovation — and stand up in court or licensing deals.\nChapter 1: What Enablement Really Means\nUnpack the rule: disclose enough detail so others can practice your invention without undue experimentation.\nChapter 2: Why the Rule Exists\nSee how enablement supports progress — disclosure today fuels tomorrow’s innovation.\nChapter 3: Functional Language Pitfalls\nUnderstand why “configured to” claims often fail and how to draft stronger claims.\nChapter 4: Prototype or Not?\nWhen building a prototype helps — and when it’s unnecessary.\nChapter 5: Spotting Enablement Red Flags\nClues in your invention and claims that suggest detail is missing.\nChapter 6: Overcoming Enablement Rejections\nExplore practical responses, arguments, and why prevention saves money.\nChapter 7: Classic Examples\nTime machines, perpetual motion, and other enablement failures...","thumbnail_url":"https://img.transistorcdn.com/6SowMnDXncCFLIwQcsr96oP7axHpU8YcUqd8Hz8baVE/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS84NWNi/ZmI0Njg4MzJlNjI1/MzkwMTgyOTAzNWNl/NzQzYS5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}