POET is not designed to serve as the system of record for regulated processes, therefore not subject to GxP requirements. It is designed to enable cross-organizational collaboration and process orchestration, while the system of record for each process remains within the respective enterprise systems.
Type = Technical Guides,; Topic = OPUS Solution Environment, Process Orchestration for Empowered Teams (POET), OPUS,;Persona = Solution Designer, Solution Partner, Technology Partner,; Orchestration = Logistics,; Function = Regulatory Affairs, Quality,
Quality and Technical Agreement
Quality and Technical Agreement enables Owner and Partner organizations to create, manage, and collaborate on agreement records across internal teams and external partners to support regulatory, operational, and business readiness.
What is Quality and Technical Agreement
Quality and Technical Agreement supports collaboration on Quality Agreement, Technical Agreement, or combined Quality and Technical Agreement records. The agreement lifecycle captures the business need, agreement type, partner, initiation reason, scope, ownership, priority, due date, drafting, review, negotiation, and final agreement outcome.
Types of Quality and Technical Agreement
The Quality and Technical Agreement specification identifies the following agreement types:
-
Quality Agreement
-
Technical Agreement
-
Quality and Technical Agreement
Add a Quality and Technical Agreement
Add a Quality and Technical Agreement by entering the required details.
- .
- Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
-
In the General section fill in the following fields:
- field – Enter Provide the title for the Quality and Technical Agreement. This field is required.
- field – Enter Provide a description of the Quality and Technical Agreement.
- Select .
The Quality and Technical Agreement is created in the Draft state.
Modify a Quality and Technical Agreement
Modify an existing Quality and Technical Agreement by updating the applicable details.
- .
- Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select the Display Identifier of the Quality and Technical Agreement to edit.
- Select .
-
In the General section update the following fields:
- Update the field – System-generated unique identifier for the Quality and Technical Agreement; format QTA-000001 with a configurable prefix.
- field – Descriptive title of the Quality and Technical Agreement.
- field – Background for the collaboration request.
- field – Reason the agreement is initiated, such as Supplier Onboarding, Outsourced GMP Activity, Renewal, Revision, Amendment, Product Scope Expansion, Service Scope Expansion, Facility Scope Expansion, or Regulatory Requirement.
- field – Role of the external partner.
- field – Business priority: Critical, High, Medium, or Low.
- field – Target completion date by which the process should be completed.
-
In the Participants section update the following fields:
- field – Business name of the Initiator Company.
- field – Identifier type of the Initiating Company.
- field – Identifier value of the Initiating Company.
- field – Business name of the Assignee Company.
- field – Identifier type of the Assignee Company.
- field – Identifier value of the Assignee Company.
- field – Owner or Partner user accountable for agreement coordination.
- field – Name of the assigned user.
- field – Owner Quality representative responsible for the agreement.
- field – Name of the Owner Quality Coordinator.
- field – Partner Quality representative responsible for the agreement.
- field – Name of the Partner Quality Coordinator.
-
In the Agreement Overview section update the following fields:
- field – Agreement type: Quality Agreement, Technical Agreement, or Quality and Technical Agreement.
- field – Current agreement version, such as 1.0, 2.0, or Amendment 1.
- field – Previous agreement associated with this activity when the reason is Renewal, Revision, Amendment, or Replacement.
- field – Indicate whether a Master Services Agreement exists, does not exist, or is not applicable.
- field – Nature of outsourced services, specific products, facilities, laboratories, sites, or operational activities covered.
-
In the Operational Scope section update the following fields:
- field – Products covered by the agreement.
- field – Classification of the product or material covered by the agreement.
- field – Services covered by the agreement.
- field – Classification of the services covered by the agreement.
- field – Facilities or sites governed by the agreement.
-
In the Market Governance and Regulatory Scope section update the following fields:
- field – Markets where the covered product, service, or activity applies.
- field – Regulatory or quality frameworks applicable to the agreement.
- field – Confidentiality classification: Public, Internal, or Confidential.
- field – Indicate whether legal review is Required, Not Required, or To Be Determined.
- field – Scope summary notes.
-
In the Agreement Reference Documents section update the following fields:
- field – Name of the supporting document.
- field – Whether the document was provided by the Owner or Partner organization.
- field – Additional information about the purpose or relevance of the supporting document.
- field – Supporting document relevant to the agreement, such as procedures, specifications, reports, drawings, or appendices.
-
In the Quality Agreement Drafting section update the following fields:
- field – Quality topics addressed by the agreement. This section applies when Agreement Type is Quality Agreement or Quality and Technical Agreement.
- field – Draft Quality Agreement document.
- field – Drafting assumptions, open quality-content issues, reviewer instructions, or rationale for omitted expected content.
-
In the Technical Agreement Drafting section update the following fields:
- field – Technical topics addressed by the agreement. This section applies when Agreement Type is Technical Agreement or Quality and Technical Agreement.
- field – Draft Technical Agreement document.
- field – Technical drafting assumptions, open technical-content issues, reviewer instructions, dependencies, or rationale for omitted expected content.
-
In the Agreement Review by Owner section update the following fields:
- field – Summary of major review outcomes, unresolved issues, or negotiation points.
- field – Assigned Owner reviewer.
- field – Owner reviewer outcome: Review Accepted, Review Accepted with Comments, or Review Findings - Negotiation Required.
-
In the Agreement Review by Partner section update the following fields:
- field – Summary of major review outcomes, unresolved issues, or negotiation points.
- field – Assigned Partner reviewer.
- field – Partner reviewer outcome: Review Accepted, Review Accepted with Comments, or Review Findings - Negotiation Required.
-
In the Negotiation Log section update the following fields:
- field – Agreement document associated with the negotiation item: Quality Agreement or Technical Agreement.
- field – Section number, clause, appendix, schedule, or responsibility-matrix row being discussed.
- field – Comment, proposed wording, response, or decision.
- field – Person responsible for coordinating, tracking, and driving closure of the negotiation item.
- field – Redlined or revised draft, responsibility matrix, supporting evidence, or decision record.
- field – Agreed decision or reason the negotiation item was removed.
- field – Agreement draft agreed by both parties.
-
In the Closure Summary section update the following fields:
- field – Whether legal review is completed.
- field – Owner agreement status: Accepted or Not Accepted.
- field – Partner agreement status: Accepted or Not Accepted.
- field – Final clean Quality Agreement document when applicable.
- field – Final clean Technical Agreement document when applicable.
- field – Date by which the next periodic review should be completed.
- field – Date the executed agreement becomes active.
- field – Optional expiry date of the agreement.
- field – Final business outcome: Effective, Withdrawn, Canceled, or Replaced by New Agreement.
- field – Overall summary of the completed agreement lifecycle and final outcome.
- field – User closing the agreement lifecycle; auto-populated.
- field – Date and time the agreement lifecycle was closed; auto-populated.
-
In the Comments and Attachments section update the following fields:
- field – User who entered the comment; system generated.
- field – Date and time when the comment was last modified.
- field – Text of the comment.
- field – Visibility setting for the comment or attachment.
- field – Files attached to the Quality and Technical Agreement.
-
In the Followers section update the following fields:
- field – Users who follow the Quality and Technical Agreement.
- Select .
Monitor Quality and Technical Agreements
Monitor Quality and Technical Agreements using the Owner dashboard, Partner dashboard, and search.
- .
- Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
| Metric | Description |
|---|---|
| Current Trends | |
| Quality and Technical Agreements by Status – Open | Total number of open Quality and Technical Agreement records categorized by Status: Draft, To Do, Under Development, In Review, and In Negotiation. |
| Quality and Technical Agreements by Business Priority | Number of open agreement records categorized by Business Priority: Critical, High, Medium, Low. |
| Quality and Technical Agreements by Agreement Type | Total number of open agreements categorized by Agreement Type: Quality Agreement, Technical Agreement, Quality and Technical Agreement. |
| Quality and Technical Agreements by Agreement Initiation Reason | Number of open agreement records categorized by initiation reason such as Supplier Onboarding, Renewal, Revision, Amendment, Product Scope Expansion, Service Scope Expansion, or Regulatory Requirement. |
| Due Date Monitoring | |
| Quality and Technical Agreements Due in Next 24 Hours | Total Number of Quality and Technical Agreements with Due Date within the next 24 hours categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Due in Next 7 Days | Total Number of Quality and Technical Agreements with Due Date within the next 7 days from the current date categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Overdue | Total Number of Quality and Technical Agreements with Due Date less than the current date/time categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Due in Future | Total Number of Quality and Technical Agreements with Due Date greater than or equal to the current date/time categorized by Status (Draft, To Do, In Progress). |
| Network Performance | |
| Quality and Technical Agreements by Assignee Company | Total number of Quality and Technical Agreements of Status (Draft, To Do, In Progress) categorized by Assignee Company. |
| Quality and Technical Agreements by Assignee User | Total number of Quality and Technical Agreements of Status (Draft, To Do, In Progress) categorized by Assignee User. |
| Quality and Technical Agreements by Partner Type | Number of open agreement records categorized by Partner Type such as Supplier, Manufacturer, CDMO, Laboratory, Logistics Provider, Cloud Service Provider, etc. |
| Agreements Requiring Negotiation | Total number of agreements requiring formal negotiation. |
| Organizational Performance | |
| Quality and Technical Agreements by Final Outcome | Total number of closed agreements categorized by Final Outcome: Effective, Withdrawn, Canceled, Replaced by New Agreement. |
| Average Time to Close Quality and Technical Agreements by Final Outcome | Average closure duration categorized by Final Outcome. |
| Average Time to Close by Partner Type | Average closure duration categorized by Partner Type. |
- Select .
- Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
| Metric | Description |
|---|---|
| Current Trends | |
| Quality and Technical Agreements by Status – Open | Total number of open Quality and Technical Agreement records categorized by Status: Draft, To Do, Under Development, In Review, and In Negotiation. |
| Quality and Technical Agreements by Business Priority | Number of open agreement records categorized by Business Priority: Critical, High, Medium, Low. |
| Quality and Technical Agreements by Agreement Type | Total number of open agreements categorized by Agreement Type: Quality Agreement, Technical Agreement, Quality and Technical Agreement. |
| Quality and Technical Agreements by Agreement Initiation Reason | Number of open agreement records categorized by initiation reason such as Supplier Onboarding, Renewal, Revision, Amendment, Product Scope Expansion, Service Scope Expansion, or Regulatory Requirement. |
| Due Date Monitoring | |
| Quality and Technical Agreements Due in Next 24 Hours | Total Number of Quality and Technical Agreements with Due Date within the next 24 hours categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Due in Next 7 Days | Total Number of Quality and Technical Agreements with Due Date within the next 7 days from the current date categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Overdue | Total Number of Quality and Technical Agreements with Due Date less than the current date/time categorized by Status (Draft, To Do, In Progress). |
| Quality and Technical Agreements Due in Future | Total Number of Quality and Technical Agreements with Due Date greater than or equal to the current date/time categorized by Status (Draft, To Do, In Progress). |
| Network Performance | |
| Quality and Technical Agreements by Assignee User | Total number of Quality and Technical Agreements of Status (Draft, To Do, In Progress) categorized by Assignee User. |
| Agreements Requiring Negotiation | Total number of agreements requiring formal negotiation. |
| Organizational Performance | |
| Quality and Technical Agreements by Final Outcome | Total number of closed agreements categorized by Final Outcome: Effective, Withdrawn, Canceled, Replaced by New Agreement. |
| Average Time to Close Quality and Technical Agreements by Final Outcome | Average closure duration categorized by Final Outcome. |
- Select .
- Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
-
In the Filters panel, fill in one or more of the following fields to filter the results:
- field – Search using the complete or partial agreement identifier.
- field – Search using the complete or partial agreement title.
- field – Displays the current workflow state. Customized substates are included in the derived currentState field where configured.
- field – Search by the timestamp when the record was created.
- field – Search using the initiating company business name or identifier.
- field – Search using the partner company business name or identifier.
- field – Filter by the target completion date of the agreement activity.
- field – Filter by Quality Agreement, Technical Agreement, or Quality and Technical Agreement.
- field – Search by the current agreement version, such as 1.0, 2.0, or Amendment 1.
- field – Filter by the role of the external partner.
- field – Filter by the date the agreement became effective.
- field – Locate agreements approaching or past their required review date.
- field – Filter by Critical, High, Medium, or Low.
- field – Read-only date and time in the system-configured format.
-
Select .
All Quality and Technical Agreements matching the filter criteria are displayed.
Tag end


