OpenText Core Signature - Marq Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and Marq

OpenText Core Signature and Marq can work together to streamline document creation, approval, and signing workflows across marketing, sales, HR, legal, and operations teams. Marq is well suited for creating branded, editable business documents and templates, while OpenText Core Signature adds legally binding electronic signature capabilities and controlled approval routing.

1. Branded Contract and Proposal Creation to Signature Workflow

Data flow: Marq - OpenText Core Signature

Sales teams can use Marq to generate branded proposals, quotes, and customer agreements from approved templates, then send the finalized documents to OpenText Core Signature for secure signing. This reduces manual formatting, ensures brand consistency, and shortens the time from proposal creation to executed contract.

• Marq creates the customer-facing document using approved templates and dynamic fields
• OpenText Core Signature manages the signing sequence for customers, sales managers, and legal approvers
• Signed documents are stored in the ECM or CRM system for audit and retrieval

2. HR Offer Letter and Policy Acknowledgment Process

Data flow: Marq - OpenText Core Signature

HR teams can create offer letters, employment agreements, and policy acknowledgments in Marq, then route them through OpenText Core Signature for candidate or employee signature. This supports faster onboarding, reduces administrative effort, and creates a consistent document experience across regions and departments.

• Marq generates personalized HR documents from standardized templates
• OpenText Core Signature captures legally binding acceptance and timestamps
• Completed documents are automatically archived in the employee record system

3. Customer Onboarding Document Pack Assembly and Signing

Data flow: Marq - OpenText Core Signature

Customer success or operations teams can use Marq to assemble onboarding packs such as service agreements, welcome letters, and compliance forms. OpenText Core Signature then handles the signature workflow for customers and internal approvers, helping organizations accelerate onboarding while maintaining compliance.

• Marq builds a tailored onboarding packet based on customer segment or product type
• OpenText Core Signature routes documents to the correct signers in sequence
• Signed packets are returned to the customer record or case management system

4. Marketing Partnership and Co-Branded Agreement Approval

Data flow: Marq - OpenText Core Signature

Marketing and alliance teams can use Marq to create co-branded partnership agreements, event sponsorship forms, and campaign approvals. OpenText Core Signature ensures that internal stakeholders and external partners can review and sign documents securely, reducing delays in campaign launch and partner activation.

• Marq produces polished, brand-compliant partner documents
• OpenText Core Signature manages multi-party approval and signature routing
• Approved agreements are stored for governance and future reference

5. Legal Review and Signature of Standardized Business Documents

Data flow: Marq - OpenText Core Signature

Legal and business teams can standardize frequently used documents in Marq, such as NDAs, service addenda, and consent forms, then send them to OpenText Core Signature for execution. This improves control over document versions and reduces the risk of unauthorized edits before signature.

• Marq maintains approved document templates with controlled content
• OpenText Core Signature enforces signature order and captures audit evidence
• Final signed copies are retained in the document management repository

6. Internal Approval Packets for Procurement and Vendor Onboarding

Data flow: Marq - OpenText Core Signature

Procurement teams can use Marq to prepare vendor onboarding forms, purchase approvals, and supplier agreements. OpenText Core Signature then routes the packet to finance, legal, and procurement approvers, enabling faster vendor setup and reducing paper-based bottlenecks.

• Marq generates vendor packets from approved templates and master data
• OpenText Core Signature captures approvals and signatures from all required stakeholders
• Completed documents are linked to vendor master records and compliance files

7. Signed Document Distribution and Controlled Reuse of Templates

Data flow: OpenText Core Signature - Marq

After a document is signed in OpenText Core Signature, the signed version and key metadata can be sent back to Marq for reuse in future document generation or for updating template libraries. This supports continuous improvement of document templates and helps teams maintain consistency across recurring business processes.

• OpenText Core Signature returns signed document status and metadata
• Marq can use the completed document as a reference for template refinement
• Business teams maintain a library of approved, reusable document formats

8. Audit-Ready Document Lifecycle Management

Data flow: Bi-directional

Organizations can connect Marq and OpenText Core Signature to maintain a complete document lifecycle from creation to execution. Marq handles document assembly and version control, while OpenText Core Signature provides signature evidence, timestamps, and audit trails. This is valuable for regulated industries that need traceability across approvals, signatures, and final document storage.

• Marq creates and updates controlled document versions
• OpenText Core Signature records signer identity, timestamps, and completion status
• Final documents and audit data are synchronized to ECM, CRM, or ERP systems