Start with the problem, not the patent jargon
A patent can be affected both by information disclosed before filing and by differences between language versions used later. These are separate problems with different evidence. A conference talk may make a technical feature accessible to an audience, while a translation may alter the apparent scope of a claim or omit a critical qualification. This directory connects users to two specific reviews and directs broader filing-route questions back to the existing procedural guides. The purpose is to preserve facts and avoid conclusions based only on the words “confidential” or “translated.”
Choose the guide that matches your situation
- Speaking at a conference? Check patent protection before you present. — Review My Conference Disclosure.
- Could a translation change what your patent actually protects? — Review My Patent Translation.
Research guide: choosing the correct filing decision
Are you about to disclose new information, or are you relying on a translated filing?
For a conference presentation, compare submitted abstracts, final slides, demonstrations, preprints and proceedings. Identify not only the event date but when any version first became publicly accessible. For a translation issue, map each critical technical term across the source document, target-language draft and claims. A change from “may include” to “must include,” for example, can be consequential in a technical description. However, the legal effect of discrepancies depends on the relevant filing route and local rules, not just a general linguistic preference.
What the official rules actually distinguish
Patent novelty and priority questions rely on the actual technical content and chronology of disclosures. The EPC provides narrow specified disclosure exceptions; it does not create a general safe period for scientific conferences. National-phase procedures can require translations and may impose rules on correction and the controlling text. WIPO’s PCT national-phase guidance is a starting point, but local office instructions govern the precise documents and consequences. A proofreading service does not replace legal interpretation or specialist technical translation.
A practical decision sequence
For disclosure review, collect every version of planned or completed public materials, access conditions, dates and participants. Make a claim-to-disclosure matrix identifying which inventive features were visible and which remained unpublished. For translation review, preserve the source-language filing, translator notes, target text, technical glossary and relevant office communication. Compare claims and key numerical or chemical terms line by line. Then identify the office whose rules determine whether corrections, declarations or other steps are available. Treat these tracks as separate review tasks.
Compare the possible paths
| Your situation | What to verify before acting |
|---|---|
| A presentation or research publication is upcoming | Review planned content and first public access dates |
| A disclosure already occurred | Preserve the actual materials and investigate applicable country rules |
| A foreign-language patent text is being prepared | Check the technical glossary, claims and source document |
| A translation was already submitted | Confirm the governing office’s correction and interpretation rules |
This comparison is a starting point, not an office-specific determination. Write down the evidence that makes each row relevant to your case and verify the governing rule for the office or territory involved. A similar-sounding issue may belong to another procedure if the application is at a different stage.
Documents that make a review more useful
| Record | Purpose |
|---|---|
| Draft and final conference materials | Identifies disclosed features and publication timing |
| Audience and distribution records | Helps establish who could access the information |
| Original-language patent specification | Provides the authoritative technical baseline |
| Translated claims and glossary | Supports consistent technical meaning |
| Filed documents and office notices | Determines the procedural posture and possible remedies |
An initial enquiry can describe the problem without attaching unpublished technical details. Preserve original files, dates and office correspondence securely. If an imminent statutory period may apply, treat an ordinary email as an enquiry rather than proof that an office has received a filing or that a professional has accepted an instruction.
Limits and mistakes to avoid
Do not infer that an informal “private” meeting was confidential without examining access conditions. Nor should a user assume an error in a translation can always be corrected without consequences. Translations of patent claims are legal-technical documents, and any correction path may depend on jurisdiction, date and original disclosure. If a user has already presented an invention or filed a problematic translation, immediate professional review may be appropriate. The page should not promise to reverse past disclosures or repair every filing defect.
Examples of why the facts change the answer
A researcher sends slides to conference organizers weeks before presenting and later posts them on a public repository. The relevant content may become accessible at more than one time. A manufacturer’s Japanese translation describes a component using a broader term than the original English application, raising a claim-interpretation issue. A biotech applicant discovers that an amino-acid symbol changed in a translated table; that may require technical and procedural examination. These scenarios need different evidence rather than a single generic “translation and confidentiality” checklist.
How to prepare a clear next-step brief
Begin with a one-sentence description of the problem. Add the first relevant filing or disclosure date, the country or patent office and the stage of the application. Record the exact question you need answered and list the official notices or dated originals that support it. If there are several alternative routes, state which outcomes matter to you and which destinations are merely being explored. Separate what you know from what requires confirmation. That creates a more useful enquiry than uploading an entire unpublished invention file without context.
For any decision that requires filing, legal opinion or formal office representation, confirm the engagement and the person's authority in the relevant jurisdiction before relying on the work. Information pages can explain possibilities and organize facts; they cannot guarantee that an office will accept a request or grant a right.
Why dates and language versions must be controlled independently
Disclosure review asks who received access to which technical content and when. Translation review asks which words accurately express the technical content and how the filing office treats the language versions. The two issues may arise in the same project, but they should be documented separately. A conference organizer might receive an abstract under restrictions while a public programme later publishes it without restrictions. Keep both versions and their dates. An engineer may translate a component name consistently while inadvertently changing a numerical condition in the claims; the latter can have a different technical consequence.
A useful translation audit compares the filed source language, proposed target text and a controlled technical glossary. Note terms for dimensions, ranges, optional features, chemical names and functional relationships. Record the provenance of any machine-translated material and whether it was professionally reviewed. Do not assume a later change in wording will be accepted by the office or restore the earlier priority support. For a disclosed invention, do not assume a later confidentiality agreement erases earlier public accessibility. Both problems require originals, not reconstructed versions prepared after a dispute arose.
Common follow-up questions
Is a research conference automatically confidential?
No. The actual audience, access restrictions and publication arrangements matter.
Can I use machine translation without any review?
A translated patent document should be checked for technical and legal meaning appropriate to the application.
Can an earlier translation error always be corrected?
No. The answer depends on the patent office, document and procedural stage.
Official references
- WIPO patent basics and novelty considerations
- EPC Article 55: disclosures
- WIPO PCT national-phase guidance
More patent guidance
Explore the Patent Help directory, the existing Filing Strategy guide and the related topic guide. These references serve different decisions; a general filing overview is not a substitute for a procedural deadline check.
This material provides general patent information and research guidance only. It is not legal advice, does not create an attorney–client relationship, and does not guarantee a filing, grant or other result. Current office requirements and the specific facts of the case must be checked with an appropriately qualified professional.
