Intellectual Property Lawyers for Cedar Rapids, Iowa

Hi, Yes, intellectual property created by you as an employee, within the scope of your employment, under a work-for-hire agreement, probably belongs to your employer. To learn more about your rights under the agreement and any exceptions, you should consult with a qualified attorney.

A Patent Assignment Agreement transfers ownership of an invention or patent rights from the inventor, known as the assignor, to another party, often a company serving as the assignee. To protect your business and ensure enforceability, the agreement should cover specific provisions that make the transfer clear, complete, and legally sound. What Is the Core Assignment Clause? The assignment clause is the heart of the agreement. It should use present-tense language such as “hereby assigns, transfers, and conveys all right, title, and interest.” Courts and the USPTO treat this as an immediate transfer, while “will assign” is only a future promise. The clause should also cover continuation, divisional, or continuation-in-part applications, along with reissues, reexaminations, and foreign filings. What Rights Should Be Transferred? The assignee should receive the full bundle of rights granted under 35 U.S.C. § 154, including the right to make, use, sell, offer for sale, import, and license the invention. The agreement should also transfer the right to sue for past, present, and future infringement, so the company can recover damages even for activity that occurred before the assignment was signed. Do You Need Consideration? Every contract requires consideration, and patent assignments are no different. Even if the transfer is to your own company, the agreement should recite consideration. This can be nominal, such as “ten dollars and other good and valuable consideration,” or it can be tied to equity or to your role as founder. How Should the Patent Be Identified? The intellectual property should be identified with precision. If a patent has issued, include the number and issue date. For pending applications, list the application number, filing date, and invention title. If no application has been filed yet, provide a detailed description and later update the record once official filing details exist. What Warranties and Representations Are Common? The assignor should warrant ownership of the rights, authority to assign, and absence of liens or conflicting assignments. Over-warranting should be avoided. Do not guarantee novelty or validity, since those are determined by the USPTO and courts. Be cautious about warranting sole inventorship unless you are certain no other inventors contributed, since misstatements on inventorship can create validity problems. What Other Provisions Should Be Included? Other common provisions include further assurances requiring the inventor to assist with future filings, litigation, or USPTO actions, a limited power of attorney for patent prosecution and enforcement, and improvements clauses that attempt to capture future modifications or developments. Improvements provisions must be drafted carefully, as vague scope language can lead to disputes. The agreement should also address corporate authority, ensuring the company has approval under bylaws or state law before accepting the assignment. What Administrative Details Matter? The agreement should contain standard contract terms such as governing law, entire agreement, amendment requirements, successors and assigns, and dispute resolution through arbitration or mediation. Both the inventor and the company should sign, and notarization is advisable because it makes USPTO recordation smoother. Do You Need to Record with the USPTO? After execution, the assignment should be recorded with the USPTO through the Electronic Patent Assignment System. Recordation should occur promptly after execution to establish clear priority and maintain a clean chain of title. While recordation is not required for validity between the parties, it protects ownership against third-party claims. The USPTO currently charges little or no fee for electronic filings, so this step is inexpensive and essential. Should You Assign or License? An assignment transfers complete ownership, which investors generally expect. A license keeps ownership with the inventor while granting defined rights to the company. Licensing may be useful when the inventor wants to retain control, license the technology to multiple companies, or test the market before giving up ownership. For most startups, assignment is the preferred approach. What About Tax Considerations? Assignments can have tax consequences, especially when IP is transferred for equity or other forms of consideration. Professional tax advice is essential to evaluate both immediate tax effects and ongoing obligations. This is particularly important if the company later earns royalties or sells the patent. What Are the Next Steps? The implementation process should include drafting the agreement with qualified legal counsel, executing it with proper corporate authority and notarization where possible, recording it promptly with the USPTO using EPAS, and consulting a tax professional to address both the transfer itself and any ongoing obligations. If you need help drafting or reviewing a Patent Assignment Agreement, the attorneys on Contracts Counsel can guide you through the process so that your company’s rights are fully protected.

When you're dealing with a technology transfer agreement, it's important to understand that you're not selling your software. You're licensing it. That might seem like a small difference, but it really isn't. Licensing means you're keeping ownership of your intellectual property while letting someone else use it under clearly defined terms. If you're based in Arizona, you've got a legal system that takes written contracts seriously and generally holds both parties to exactly what’s spelled out. So clarity matters—a lot. Be Specific About What's Being Licensed Don't just say you're licensing "software." Spell out what that includes. Are you talking about the source code? Object code? Documentation? APIs? Maybe there's configuration data, algorithms, or some embedded proprietary know-how. Lay it all out. Also, be clear on whether things like updates, bug fixes, or patches are part of the deal or if those require separate terms. Courts in Arizona won't guess what you meant. They’ll go by what’s in the document. Keep Your IP Rights Locked Down Make sure the agreement says you're not transferring ownership. You're only granting the rights specifically listed in the license. Anything not spelled out stays with you. Without that language, you could run into disputes later—especially if the licensee makes improvements. Want to avoid headaches? Clearly state that you own any enhancements unless you decide otherwise. Be Intentional About the License Structure Think through how you’re structuring the license. Is it exclusive, non-exclusive, or somewhere in between? An exclusive license can be powerful, but it limits your flexibility. If you're giving up other opportunities, it's reasonable to ask for higher compensation and make sure the licensee meets clear performance targets. On the flip side, a non-exclusive license gives you room to work with others. You can also narrow the license by geography, industry, or even specific use cases. And don’t forget to address sublicensing. If it’s allowed, include approval rights and make sure you’re compensated fairly if they sublicense to others. Choose a Payment Model That Reflects Value There’s no one-size-fits-all way to get paid. You might go with an upfront fee for past development work, ongoing royalties based on sales, or milestone payments tied to things like product launches or regulatory approval. Each has its pros and cons. Whatever you choose, protect yourself with audit rights. You want access to the licensee’s records if something seems off. That usually means giving them notice, checking things during business hours, and shifting the audit costs if the discrepancies are significant. Protect Your Work from Unintended Use If you’ve used open-source components, you need to disclose that—and understand how those licenses impact what you can legally offer. GPL code, for example, can bring in obligations that might not work with your business model. Copyright registration isn’t mandatory, but it gives you the ability to sue in federal court and can unlock statutory damages and legal fees. If you've developed novel algorithms, you might consider a patent—but only if the innovation meets the standards. It's not always worth the cost, so weigh that carefully. Make Sure the Licensee Does Something with Your Tech If you’re giving someone exclusive rights, set performance expectations. What does commercialization look like to you? It might mean releasing a product by a certain date, hitting minimum sales, or committing to a marketing budget. If those things don’t happen, you need a remedy—like converting the license to non-exclusive or ending the agreement altogether. The goal is to make sure your technology doesn’t sit unused. Clarify Support and Ongoing Involvement Are you expected to provide support? If so, spell out exactly what that means. Documentation, training, installation help, bug fixes, future updates—whatever it is, define it. Also decide whether that’s included in the license or billed separately. If you’re providing source code, put strict confidentiality and usage terms in place. In some cases, a source code escrow might be appropriate, with release conditions like your bankruptcy or failure to maintain the code. Limit Your Liability Arizona has adopted the Uniform Commercial Code, so if you don’t include specific disclaimers, you might be stuck with certain implied warranties. That includes things like fitness for a particular purpose. You’ll want to limit that while still affirming that you own the software and that it generally works as described. Also, set a cap on liability. Most developers limit it to the total fees paid under the agreement and exclude indirect or punitive damages. You don’t want to be held responsible for how someone else uses your tech. Mutual Indemnification Matters If someone accuses your software of infringing their intellectual property, you might agree to cover the licensee’s costs. But it needs to go both ways. They should indemnify you too—especially if they modify your code or use it in a regulated environment where compliance issues could come up. You don’t want to be liable for something outside your control. Don’t Skip Export Control Compliance Yes, export control rules apply even to downloadable software. If your product includes encryption or certain types of AI or analytics, it may fall under specific federal regulations. Many tools qualify for License Exception ENC, but that’s not automatic. Misclassification can lead to serious fines. If you're licensing internationally—or even just to a foreign-owned company based in the U.S.—you need to get this right before moving forward. Understand How Arizona Law Will Handle Your Agreement Arizona courts usually enforce what’s written. If it’s not in the contract, don’t expect the court to fill in the gaps. That makes detailed drafting essential. Arizona also supports reasonable non-competes and confidentiality terms, which isn’t true in every state. Just make sure any restrictions are tied to legitimate business interests and kept within reasonable limits for time and geography. Spell Out What Happens at the End Termination clauses are your safety net. Cover scenarios like breach, bankruptcy, missed milestones, or even changes in company control. Include cure periods where appropriate. Be specific about what happens when the agreement ends—does the licensee have to stop using the software immediately? Can they finish selling what’s already been produced? Make that clear. Also, specify which obligations survive termination. Usually, confidentiality and IP rights continue, even after the main agreement ends. Plan Ahead for Disputes Choose Arizona law to govern the agreement. If your licensee is in another state or country, decide where and how disputes will be handled. Arbitration can be quicker and cheaper, but it might limit your access to things like injunctive relief. Consider requiring mediation first to give both sides a shot at resolving issues early. And don’t forget a prevailing party clause—Arizona courts do enforce them, and it could help you recover attorneys’ fees if you end up in a legal fight. The Final Analysis Technology licensing isn't just about protecting your IP. It's about setting clear, enforceable expectations from the start. Arizona law gives you the tools to do that, but it only works if your agreement is well-drafted and forward looking. Define what you're licensing, retain ownership, protect your downside, and make sure the deal drives results, not just risk. If you're a software developer navigating a tech transfer deal or reviewing an agreement someone else drafted, don’t go it alone. Having the right legal language in place from day one can prevent years of headaches down the road.

It would be a good idea for you to have the agreement reviewed by an attorney. You said there's no explicit language regarding termination or notice - is there something implied? With no language regarding termination, most likely either party can terminate at any time, with just a moment's notice, and no reason given. You have asked a lot of questions - I suggest that you post a project here on Contracts Counsel, and ask for an attorney well versed in intellectual property (not me) to discuss your rights, as that is probably the most important issue. An attorney who can also review the language of the entire agreement would be very helpful. (I'm sorry, but I'm not available for this project).

Hello, I wanted to express my interest in helping you understand your trademark rights and the trademark transfer proposal you received. As brief background, I am a US-licensed trademark attorney and have helped clients in similar situations buy, sell, and otherwise transfer trademark rights through transfer agreements. I can also help you prepare and file a federal trademark registration to protect your unique brand name and logo throughout the US. I'd be glad to set up a brief call to learn more about your business and see how I can help. Thanks for your consideration. Best, Roman Vayner (c) 414.628.9099 (e) rvayner@vaynerlegal.com www.vaynerlegal.com VaynerLegal, LLC