IP Intelligence
Written For Your Situation
The same law reads differently to a founder, an engineer, a researcher and an enterprise IP team.
Engineer
IP for engineers and R&D
For the people who actually build the thing, and who decide - often without knowing it - what can be protected.
Open source and patents: what founders should know
Publishing code is a public disclosure with a date, and several open source licences carry patent grants or termination provisions. Both need to be checked before yo…
How to spot the patentable feature in your own work
The part that solves a technical problem in a way the field would not have expected - not the part you are proudest of, and usually not the whole system.
How to write an invention disclosure a drafter can use
The problem, what was tried before, the mechanism with numbers, the alternatives you rejected, where it stops working, and any comparative data - with dates and name…
What counts as a technical effect
Something measurable that improves in the machine, the system or the process - not something that improves for the user or the business.
Why to describe versions you never built
Yes. Amendments can only recite what was disclosed on filing, so the alternatives you describe today are the only fallback positions you will have in three years.
The experiment that answers the objection
The comparison against the closest prior art, and - in chemistry and life sciences - the specific comparisons that sections 3(d) and 3(e) require. Design those exper…
Architecture, implementation, and which one to claim
Claim the level at which the invention actually lives - which is usually the functional relationship, not the specific implementation and not the abstract idea.
The ways engineering teams disclose inventions by accident
Public repositories, conference talks, papers, job adverts, supplier drawings, customer demos and support documentation - usually before anyone has told the legal si…
How to read a patent claim
Break claim 1 into its features, treat every feature as a condition that must be met, and ignore everything else in the document until you have done that.
Reading a competitor patent without panicking
Check whether it is granted and in force, in your country, then map your product against the granted claims - not against the title, the abstract or the drawings.
Searching prior art the way an examiner does
Because examiners search by classification across jurisdictions and decades, in several languages, including documents that never became products - and engineers sea…
One concept, one word
Yes. Support for a claim term is judged by what the description says about that term, so a component with three names has its support split three ways.
What to record, and why it matters later
They matter for two things: proving who devised what, and preserving the technical detail that becomes disclosure and evidence. India is first-to-file, so a notebook…
Inventive step, explained for engineers
Because the test is not whether it was hard for you. It is whether a competent, unimaginative person in your field, holding all the prior art, would have got there -…
Not sure whether this applies to your invention?
The honest answer usually needs someone to look at your actual disclosure, your timeline and the prior art. That is a conversation, not an article.
Educational guidance, not legal advice. This material is published by Ragulika IP for general education and information. It is not legal advice, it does not create a professional-client relationship, and it is not a substitute for advice on your own facts. Patentability, infringement, prosecution strategy and every other IP outcome turn on the specific facts and on the law and Patent Office practice as they stand at the time you act. Please take professional advice before making a decision, and read the underlying provision or judgment before relying on any point stated here.