EPO & digital workflows
Digital EPO 2027: organise access, AI assistance and team workflows
Connect personal access, responsibilities and cover with a checked team workflow and findable evidence.
Your team needs a clear picture of who can perform each EPO task and what remains to be set up. A Microsoft 365 workspace can hold confirmed access, owners and open points together. AI can propose an initial responsibility matrix from approved working instructions; the team checks it against actual tasks and official access.
Creating an EPO account is only the first step. Daily work raises more specific questions: who can see incoming communications, who prepares a draft, and who reviews, signs and sends it? A successful login does not yet establish an operational workflow.
From 1 April 2027, electronic filing and notification become the general approach in proceedings before the EPO. This guide connects the announced change with a practical setup plan for patent firms and in-house IP teams. Sources were checked on 8 November 2026.
What changes on 1 April 2027
The provisions published in September 2026 cover European patent proceedings, international proceedings before the EPO and Unitary Patent proceedings. Two tasks matter particularly for preparation: arranging submissions through the designated electronic filing service and receiving official post in the EPO company mailbox. Individual procedural actions are available only within the supported scope.
The change is not an absolute ban on every paper document. The new provisions contain exceptions and, for certain postal filings, provide for electronic resubmission following an invitation. PCT proceedings also involve specific routes, as provided for the relevant PCT procedure. The person responsible for the proceedings needs to check which provision applies to a particular task.
Five layers that need to work together
| Layer | Practical question | Evidence to keep |
|---|---|---|
| Personal EPO account and two-factor authentication | Can the authorised person sign in and use their second factor? | Login tested using the intended personal account |
| EPO company association and administration | Is the account linked to the correct company, and who manages members? | Company association and responsible administrator recorded |
| official mailbox and recipients | Which confirmed recipients should receive communications? | Recipient status and electronic communications settings checked |
| Portfolio and filing permissions | Which files and tasks can this person actually access? | Required views and actions checked in the relevant service |
| Work allocation and cover | Who controls the work, approves it and covers absences? | Responsibilities and escalation route recorded |
An administrator role does not automatically establish access to a particular filing task. Check the permissions needed for communications, submissions and fee work in the relevant EPO service.
Turn instructions into a checked responsibility matrix
Start with the work actually agreed. AI can draft a table covering the task, access needed, owner and absence cover. Missing owners or conflicting statements become questions rather than guessed answers. Keep the original instruction accessible beside the proposal.
Administration confirms the technical association; the responsible person confirms their task scope. In Microsoft 365, give each open setup step an owner and a checkable outcome. Keep passwords and authentication codes out of this table. Agree the document, task and AI capabilities needed for the actual working environment.
Prepare personal access
The EPO requires an EPO account with two-factor authentication for its secure services. Plan named user access for the people involved. A shared office email address can serve an organisational purpose; sharing a password makes it harder to attribute activity or withdraw one person’s access.
Before creating anything, check whether a suitable account and company association already exist. An additional organisation may create unnecessary duplication. Keep contact details current and maintain access to the account’s email address. The EPO recommends backup methods for two-factor authentication. Your IT team should know how access will be recovered if a device is lost.
- Identify existing personal EPO accounts and company administrators.
- Check login and the second factor with the intended user.
- Record an accessible contact address and the recovery arrangement.
- Agree who removes permissions and updates details when staff change.
Assign company membership and permissions to actual tasks
An EPO company groups users who work with a shared official mailbox and application portfolios. Its administrator manages members’ access. Check your existing structure and the responsible office administrator before creating a new company. The displayed company name does not itself establish a procedural role or an authorisation to act.
Build a short task matrix: read incoming communications, associate documents with files, prepare drafts, send approved submissions and perform fee tasks. Give each task a responsible person and identify the necessary permission. Then check what that user can actually see and do. Their working view is more useful evidence than the role label alone.
Procedural status also affects available functions. The current EPO guide distinguishes self-representing applicants from professional representatives when describing access to procedural actions. A missing area may therefore result from the available function, the procedural role or a permission. Granting additional technical rights does not create a right of representation.
Test the official mailbox and filing route separately
An existing official mailbox does not by itself prove that the intended communications are being delivered there. Check the requested recipients, their approval and the current electronic communications settings. A pending recipient request needs to be completed first. Email alerts about new documents are an additional notification layer.
For EPO electronic filing, check the company association, required forms and user permissions separately. Use the designated test environment for a trial submission. Do not send a real procedural document solely to see whether production access works. Substantive review, signature and authority to send remain distinct responsibilities.
For the daily process, see our EPO company mailbox guide. Before sending, use the filing package checklist; afterwards, keep an auditable filing confirmation with the case record.
Narrow down common setup problems
| Observation | First check | Useful next step |
|---|---|---|
| Login works, but the official mailbox is missing | Company association and personal official mailbox permission | Ask the administrator to check the specific membership |
| The official mailbox is visible, but expected post is missing | Recipient status, electronic communications and correct file | Clarify the routing with the responsible team |
| A form or action is unavailable | Service, form permissions and functions available for the procedural role | Define the task precisely; contact EPO support if needed |
| An email alert has not arrived | Alert settings and the normal email system | Check the official mailbox directly and investigate alerts separately |
| Only one person understands the setup | Cover permissions and internal instructions | Have an authorised colleague test access and the handover |
A useful support request identifies the service, time, visible status and exact task. Keep passwords, authentication codes and confidential case material out of general screenshots. A precise issue description reduces follow-up questions and can later become part of your internal instructions.
Make the setup usable through a short acceptance check
Fictional example: a small patent firm wants a shared incoming-post workflow. The administrator assigns memberships. One formalities colleague checks the official mailbox with their own account; the colleague covering absences repeats the check. The responsible representative checks the procedural actions available to them. The team records who associates documents with files, controls deadlines and handles questions. This review happens before the first time-critical task.
- The required people, company and recipients are associated.
- Reading, drafting, signing and sending have appropriate owners.
- Cover and escalation for access problems are agreed.
- Storage of communications and filing receipts is defined.
- Open issues have an owner and a next step.
IP Formalities can prepare an administrative access review, task matrix and handover under your instructions, working with your team and IT. We define the scope around your actual work. See external IP paralegal responsibilities. A possible later extension is described in our EPO API overview.
Connect the workflow to the next task
Related steps: organising official communications, planning data handovers, defining responsibility.
Sources and further reading
Frequently asked questions
- Is one EPO account enough for the whole firm?
- The personal account identifies the person signing in. Shared work is organised through an EPO company and appropriate user permissions. Plan personal access and a clear arrangement for cover.
- Does an EPO company administrator automatically have every filing permission?
- The administrator manages access rights. A particular task still needs to be checked in the relevant service and, where applicable, for the specific form. Technical access does not replace procedural authority.
- Should existing users check anything before April 2027?
- Yes. Existing company associations, recipients, electronic communications settings, personal permissions and cover arrangements should fit the planned workflow. An existing login alone does not establish this.
- Does technical setup transfer responsibility for deadlines?
- No. official mailbox monitoring, deadline determination and approvals need to be expressly allocated. A technical permission does not itself document that engagement.