For engineering organizations developing communications, display, imaging or input-device technologies, understanding how patent applications are examined can help teams prepare for the application process. The USPTO TC 2600 Customer Partnership Meeting, held January 17, 2018, set out a program focused on examiner training, Office Action review, interviews and discussion with Technology Center leadership.
The published agenda does not describe specific examination decisions or policy changes. It does, however, identify several parts of the examination process that applicants and their technical representatives may need to navigate, as well as the breadth of technologies and workgroups represented within TC 2600.
What the USPTO TC 2600 meeting covered
The day began with introductions to contacts for procedural issues, followed by a presentation on general and Technology Center-specific training. Later sessions addressed how Supervisory Patent Examiners (SPEs) and primary examiners are trained to review Office Actions, and how examiner interviews are trained and conducted. Workshops and a director panel Q&A were also scheduled.
These agenda topics reflect different points of contact between applicants and the examination process. Training on Office Action review concerns the examination record and the communication of an examiner’s position. Interview training concerns another channel for discussion between an applicant and an examiner. The agenda identifies these subjects as meeting sessions; it does not provide detailed guidance on interview procedure or how particular applications should be argued.
Why Office Action review matters to technical teams
An Office Action is a formal communication issued during patent examination. For a company’s engineering and intellectual-property teams, responding to one typically requires connecting the examiner’s stated concerns to the application’s claims and technical disclosure. The meeting’s planned session on how SPEs and primary examiners are trained to review Office Actions placed this examination activity on the program.
That subject is relevant to cross-functional teams because patent applications describe technical subject matter in a legal framework. Engineers may be asked to clarify how a system operates, how components interact or what distinguishes a proposed implementation. Keeping technical explanations consistent with the application’s written disclosure can help the team communicate efficiently with its patent counsel as it evaluates a response.
The source agenda does not set out a response method or promise a particular examination outcome. Its practical significance is narrower: Office Action review was explicitly included as a topic for discussion between the Technology Center and its customers.
Examiner interviews as a communication topic
The scheduled presentation on examiner interview training and practices highlights interviews as another part of the applicant-examiner interaction. For technical decision-makers, an interview can provide an opportunity to discuss an application’s issues directly, with patent counsel coordinating the substance and process. The agenda confirms that TC 2600 planned to address examiner interview practices, but it does not specify the rules, timing or expected results of an interview.
Teams preparing for any examination discussion can benefit from clear internal coordination. Engineering staff can help ensure that explanations of the technology are accurate, while patent professionals manage how those explanations relate to the claims and the examination record. This division of responsibilities is particularly important for complex systems involving hardware, software, communications or image processing.
TC 2600 spans a range of technical workgroups
The meeting materials identify directors responsible for workgroups 2610, 2620, 2630, 2640, 2650, 2660, 2670, 2680 and 2690. The listed areas include communications, display systems, image analysis, input devices, digital cameras, semiconductor testing and measuring, telecommunications, printing and related subject matter.
The biographies also describe experience across other technical fields, including electrical and mechanical engineering, biotechnology, semiconductor fabrication, measurement and testing. These backgrounds provide context for the leadership and presenters named in the program. They should not be read as a complete map of application assignments or as a substitute for checking the current USPTO resources relevant to a particular filing.
For industrial automation companies, the range of subject areas is a reminder that a product’s patent portfolio may touch multiple technical domains. A connected device, for example, could involve communications, display or sensing elements. The meeting materials do not assign any specific automation technology to a particular workgroup, so applicants should confirm the appropriate classification and routing through official USPTO channels.
Using the meeting agenda as process context
The January 2018 program is best understood as a snapshot of topics selected for a customer partnership meeting, not as a current procedural manual. Its agenda highlights three useful areas for applicants to understand:
- Procedural contacts: The meeting opened with introductions to contacts for procedural issues.
- Examination and review: Training for examiners and review of Office Actions were scheduled for discussion.
- Applicant communication: Examiner interviews and practices were included, alongside workshops and a director Q&A.
Because the event took place in 2018, its listed personnel, workgroup responsibilities and program details should not be assumed to reflect current arrangements. Patent applicants should consult up-to-date USPTO information when seeking contacts or procedural requirements.
Practical implications for automation organizations
For plant technology suppliers, system integrators and automation businesses pursuing patents, the meeting’s themes reinforce the value of treating prosecution as a coordinated technical and legal process. Maintain a clear account of the invention, involve engineers when technical questions arise, and work with patent counsel to connect those explanations to the application and any Office Action. Where an examiner interview is considered, clarify the goals and preparation with counsel rather than assuming the meeting format or outcome.
The TC 2600 customer meeting brought examiner training, Office Action review, interviews and leadership discussion into one program. For technical organizations, those topics offer useful context for understanding how communication takes place during patent examination—while the agenda itself remains a historical record, not a source of current filing instructions.