Including Patents and Pending Applications Accurately
Present patents and pending applications using verified status, named relationships and permitted disclosure without overstating ownership or grants.
TL;DR
- Answer the three verification questions before listing a matter: confirm current status, your recorded relationship, and permitted disclosure; label filings accurately and do not claim a grant without confirmation.
- Use status-specific wording and document approvals: label applications as applications, share only authorised details, and keep verification records so future revisions start from evidence.
- Respect confidentiality and maintain accuracy: omit or broadly describe matters when disclosure is not permitted, test public links, and update the resume if a status changes before reuse.
Start with the verified record
A patent-related resume entry should answer three separate questions: What is the current status of the matter? What is your recorded relationship to it? What information are you permitted to disclose? A strong technical contribution does not justify blurring any of those answers.
Use the appropriate official record and your organisation's authorised contact to verify the description. Do not rely on an old presentation that said a filing was planned. A planned application, an application that has actually been filed and a granted patent require different wording. This article concerns resume presentation, not a determination of patent rights or filing strategy.
If the record is unclear, keep the entry out of the submitted version until it is clarified. You can still describe permitted engineering or research work without attaching an unsupported patent label to it.
Separate inventorship from ownership
Being named as an inventor and owning patent rights are not interchangeable descriptions. The USPTO's guidance on managing a patent discusses ownership and assignments. For resume purposes, the practical lesson is to use the relationship that the verified record supports rather than casually saying “my patent” when that suggests ownership you have not established.
A person who tested a prototype, prepared drawings or coordinated documentation may have made an important contribution. Those actions do not by themselves authorise the person to claim named inventorship. Conversely, a named co-inventor should not erase the other inventors by presenting a shared invention as an entirely individual achievement.
Keep contribution evidence alongside the formal entry. The reader may care as much about the problem you solved and the decisions you made as the existence of a filing. Our resume accomplishments guide can help describe that work without converting every project outcome into a personal claim.
Use status-specific wording
For a granted patent that you may discuss, an entry can identify the title, jurisdiction, patent number, grant date and your verified role as a named inventor or co-inventor. Use the official details rather than constructing a number or abbreviated title from memory.
For an application, label it as an application and give only information you are authorised to share. Do not place it under a heading that implies every listed item is a granted patent. If both states appear, a heading such as “Patents and patent applications” can work when each item is clearly labelled.
The USPTO's provisional-application guidance explains that a provisional application can support use of the term patent pending in the described circumstances; it is not examined as a granted patent. Do not use that phrase indefinitely based on an old filing. Confirm the current status with the responsible person before representing it in an application.
Work through a fictional example
Imagine engineer Theo helped design a sensing mechanism. The employer's authorised record confirms that he is a named co-inventor on a filed application, and the employer approves a brief public description. Theo has no confirmation of a grant.
A suitable entry would identify the approved application title and accurately label its application status. Under his job, a separate bullet might explain that he developed and tested the permitted aspect of the sensing approach. It should not say “secured a patent” merely because the filing was completed.
Now change the facts: Theo helped test the prototype but is not a named inventor. He can describe the testing contribution where disclosure is permitted. He should not copy the inventorship entry from a colleague's resume. The underlying work can remain valuable even when its correct category is project experience rather than patents.
Keep confidentiality ahead of resume completeness
A public record does not automatically make every related internal discussion, prototype detail or commercial plan suitable for disclosure. An unpublished matter can require even greater care. Ask the appropriate employer or adviser what wording is allowed; do not use a job application as an informal disclosure experiment.
Where details cannot be shared, a broad approved description may be sufficient. If even that is not permitted, leave the matter out. Avoid uploading confidential documents to a resume tool to obtain more impressive wording.
Public links should point to the correct official record or another authorised source. Test the link and check that it matches the entry. A broken or unrelated record creates confusion even when the underlying claim is true.
Review the entry as circumstances change
Store the verification date and approved wording privately so that future revisions start from evidence. If a status changes, update the resume before reusing it. Do not silently convert an old application entry into a grant based on an assumption or an informal congratulations message.
Finally, consider relevance. One accurate entry connected to the target role can be more useful than a long list the reader cannot interpret. Use the resume length guide to balance formal records against the experience that explains them. The result should communicate technical contribution clearly while leaving legal status and ownership exactly as verified.