AI & IP workflows

EPO oppositions: clarify roles before assigning the work

Make the proposed roles and actual services clear enough for the responsible people to review before work begins.

Before work starts on an EPO opposition, the team needs a usable division of responsibilities. Who would act as the named party, who gives instructions, who prepares arguments and who provides administrative support? A shared record prevents different people from assuming that the same label covers different services.

A Microsoft 365 workspace can bring together approved instructions, an AI-assisted role chart and the decisions made about it. The result is a reviewable working brief. It does not itself decide whether a particular arrangement is legally permissible.

Start with the work that has actually been agreed

Collect the approved service description and expressly confirmed instructions. Identify questions still being discussed. A tentative proposal should not be given the same status as an accepted task. Silence in an email exchange should not quietly become an affirmative instruction in the chart.

The central working note does not need a confidential case history. For this purpose, record the role, intended activity, responsible person, information needed and decision status. Link the material the team has been authorised to use. Decide who may review the chart according to the engagement, rather than sharing every source with every participant.

Also identify which material each participant needs for the review. A useful role record works with the information required for the decision. It does not share the entire document set by default, but records which source should be available for each particular question.

Ask AI for a role draft and specific questions

Give AI a bounded task: associate described activities with the roles expressly mentioned and flag missing responsibilities. It might identify that document preparation is covered while nobody is named to review later substantive responses. Each proposed association should point to a particular instruction so a reviewer can verify it.

The responsible people check the draft against the originals. Turn unclear activities into questions: who decides the content, who signs, who is authorised to submit, and who deals with a possible hearing? The chart should support real decisions. It must not invent authority through confident wording or silently assign a professional task to administrative support.

A short matrix makes the differences visible

Fictional structure for clarifying the assignment
Work areaQuestion to resolveWorking evidence
Named partyWho would act in their own name?Confirmed description of the role
Substantive workWho prepares and reviews the arguments?Named owner and defined scope
Administrative supportWhich document, post and handover tasks are included?Bounded task list
Further proceedingsWho decides what happens at later stages?Decision route and open questions

Technical permissions do not give this matrix legal effect. Access to documents may be necessary for the agreed collaboration, but it does not establish who may represent a party or perform a procedural act.

Fictional example: find an unassigned task before starting

A fictional team describes the first document package in detail. AI flags that nobody has been assigned to later substantive questions or a possible hearing. The handling person confirms the gap and prepares a focused request for clarification, rather than treating the initial preparation instruction as a complete procedural engagement.

That part of the scope stays open until an answer is received. After the decision, the team retains an updated role chart. It shows what has been accepted and which work would need a separate instruction. The result is a useful briefing for further review without turning an incomplete request into a comprehensive promise.

Continue with a reviewed working brief

  • The named party, instructing role and support are distinguished.
  • Actual activities have clear proposed owners.
  • Unresolved representation questions have an appropriate reviewer.
  • Later responses and hearings are considered in the scope.
  • The confirmed version and its sources are findable.

IP Formalities can help prepare the administrative role record and the questions your team needs to resolve. Connect it with a defined engagement scope, a prepared conflict review and an explicit matter handover.

Sources and further reading

Frequently asked questions

Is an interested party staying in the background automatically impermissible?
No. G 3/97 says acting in a third party's interests alone is insufficient. The actual arrangement and any circumvention by abuse of process require separate assessment.
Must a German company always appoint a professional representative?
Article 133 EPC does not impose that general requirement. This does not automatically approve every service or actual allocation of activities.
Can AI legally approve the roles?
No. It can organise instructions, flag gaps and prepare questions. It does not replace assessment of the actual arrangement by the appropriate reviewer.
What is the practical deliverable?
A source-linked role and task chart showing accepted scope, unresolved questions and the people responsible for decisions.
All guides

Let’s talk about your workload.

Choose an introductory meeting with no obligation, or email me. It helps to know the tasks, dates, approximate volume and systems you use. General information is enough – please do not send confidential case files or access credentials yet.