AI & IP workflows
Public patent files: review visibility before filing
Link a deliberate disclosure decision to identifiable outgoing files and the source material used to review them.
A document may be prepared privately inside the team. Once it enters official patent proceedings, a different question arises: which information may form part of a file that others can inspect? A deliberate outgoing-document check helps separate internal working material from the intended filing package.
A Microsoft 365 workspace can connect originals, AI suggestions and the package proposed for external use. The practical result is a recorded decision about particular files. That decision depends on the proceedings and required information, rather than an internal confidential label alone.
Separate internal confidentiality from official file inspection
Article 128 EPC distinguishes the periods before and after publication of a European patent application. After publication, file inspection is generally available subject to the applicable restrictions. Rule 144 EPC identifies excluded parts of the file. The responsible person needs to check how those provisions apply to a particular document.
Using different sign-in accounts does not establish a general anonymity guarantee. Nor does an internal agreement automatically make an official file confidential. Review the outgoing content itself, rather than drawing conclusions about future visibility from the technical account used to transmit it.
Build the outgoing package from an organised record
Distinguish three sets in the workspace: original sources, internal working material and proposed outgoing files. A comparison draft should not enter the package merely because it sits in the same folder. Links can preserve the relationship without sending every working note to an external recipient.
The package list identifies the purpose, specific version and intended recipient. Also record which information must be included under the approved instruction. A shorter file is not automatically the correct file. Do not remove necessary or procedurally required information simply because the team has a general concern about visibility.
Check the actual outgoing file again after conversion or final editing. Approval of a working draft does not automatically cover every file subsequently generated from it. The package list should therefore identify the exact version proposed for external use.
Use AI to raise questions for the reviewer
A bounded AI task might compare the selected files with the approved package list and flag unclear attachments, personal details or internal comments for review. Each suggestion needs a reference to the relevant passage. The absence of an AI flag does not establish that every issue has been identified.
The handling person opens the originals and decides which suggestions are valid. Questions about required information or an available exclusion from inspection go to the appropriate reviewer. Keep a record of the exact file checked and the decision that followed, rather than retaining an unexplained general approval label.
Keep a short decision record
| Check | Record | Outcome |
|---|---|---|
| File version | The particular version presented for review | Confirmed or revision needed |
| Package membership | Purpose and approved document list | Outgoing or internal |
| Required information | Instruction and procedural requirement | Confirmed or awaiting review |
| External use | Owner and exact outgoing files | Approval or question |
This note records the internal review. It is not an office decision on file inspection and does not replace a prescribed request. If a further official step is needed, give it a separate owner and a visible status so a colleague can see whether it has actually been taken.
Fictional example: find a working comment before release
A fictional team prepares documents for patent proceedings. The proposed outgoing version still contains an internal working comment. AI flags the passage and identifies the file. The handling person confirms the finding and asks the responsible person which version should actually be transmitted.
The revised outgoing file is identified and presented for a fresh decision. The earlier version remains recognisable as internal material. No mandatory information is concealed, and nobody claims that later file inspection has thereby been excluded. The useful result is a deliberate selection of documents with a record of what was checked and why the version changed.
Hand over an identifiable package
- Internal notes are separate from outgoing documents.
- AI suggestions have been checked against original files.
- Required information is preserved or expressly awaiting review.
- Approval relates to identifiable files.
- Any further professional question has an owner.
IP Formalities can help prepare the administrative outgoing-document check and the questions needed for release. Connect it with package preparation, the agreed information scope and the resulting filing evidence.
Sources and further reading
Frequently asked questions
- Do different accounts make a relationship invisible?
- No general guarantee follows from that. Actual documents, information and procedural rules matter, rather than the sign-in accounts alone.
- Is an internal confidential label enough?
- It records an internal intention. It does not automatically decide which parts of an official file are open to inspection.
- Can AI identify every disclosure issue?
- No. It can prepare suggestions and highlight passages for review. The originals and the appropriate person's assessment remain essential.
- What is retained in the workspace?
- The sources, checked suggestions, identifiable outgoing files and the decision about their release. Access is agreed according to the engagement.