Tag: Patent Workflow Automation
-
Rule 56 to Reality: Automating Your Duty of Disclosure
If you’re building something big—tech that matters, a product that changes the game—you probably don’t want to get tripped up by a small legal rule most founders have never heard of. But here’s the thing: Rule 56 can make or break your patent. It’s not just a form. It’s not just a box to check.…
-
IDS Made Simple: A No-Stress Workflow for Busy Teams
When you’re building something new—especially at startup speed—the last thing you want is legal paperwork slowing you down. But when it comes to patents, there’s one thing you can’t ignore: the Information Disclosure Statement, or IDS. It sounds boring, and honestly, it kind of is. But it’s also one of the most important steps in…
-
103 Obviousness: Motivation to Combine—Build or Break It
You’ve built something new. Maybe it’s code. Maybe it’s hardware. Maybe it’s a new way of using existing tech. It’s working. It’s exciting. And now you’re thinking: should I patent this? Then someone throws out a scary phrase: “Section 103 obviousness.” What is “Motivation to Combine”? The Business Impact Behind the Legal Language For most…
-
Teaching Away & Unexpected Results: The 103 Evidence Pack
You’ve built something new. Maybe it’s a smarter way to process data, a clever algorithm, a unique machine learning model, or even just a better tool to solve a problem others gave up on. You know it works. You know it’s different. But how do you protect it? What is “Teaching Away” and Why Should…
-
Analogous Art in 103: Keep Out the Wrong References
If you’re building something new and want a patent, there’s one sneaky way your patent can get blocked before it even gets a chance: the examiner pulls in a reference from a totally different space. Something that sounds similar but has nothing to do with your invention. This is what we call analogous art in…
-
Ranges & Overlap: Winning 103 with Criticality
If you’re building something new and important, you need to protect it. That usually means patents. But there’s one big hurdle that trips up a lot of startups and inventors: the USPTO’s Section 103. It’s the rule that says your idea can’t just be new—it also has to be non-obvious. And that’s where things get…
-
112 Enablement: Wands Factors Checklist You Can Reuse
If you’re building something new—a product, a platform, a machine, or a breakthrough piece of tech—you probably care about speed. You want to move fast. Launch fast. Ship fast. And yes, protect fast. But when it comes to patents, there’s a part that can trip up even the smartest founders: Section 112 of U.S. patent…
-
112 Written Description: Showing Support Without Rewriting
There’s one part of the patent rulebook that quietly trips up a lot of smart founders and engineers. It’s not because it’s complicated. It’s because it’s often misunderstood. It’s called the written description requirement under Section 112 of the U.S. patent laws. What Section 112 Really Means (And Why It’s So Easy to Miss) The…
-
112 Indefiniteness: Fixing Fuzzy Terms Fast
Most founders don’t think about it until it’s too late. You file your patent. It seems fine. But later — maybe during funding, acquisition, or a legal review — someone finds it. A vague word. A fuzzy phrase. Something you thought was “clear enough.” What is 112 Indefiniteness — and Why It Can Blow Up…
-
Means-Plus-Function (112(f)): Build Support That Survives
Let’s get right to it. If you’re building something new—an invention, a product, a piece of software—you want protection. Real protection. The kind that actually holds up when someone tries to copy what you’ve built. That’s where patents come in. And there’s one part of patent law that can either be a secret weapon… or…