Consonance - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Core Signature

Consonance and OpenText Core Signature complement each other well in publishing operations where editorial, legal, rights, and production approvals require secure, auditable signatures. Consonance manages the publishing workflow and title metadata, while OpenText Core Signature adds legally binding electronic signature capabilities for approvals, contracts, and release documents.

1. Rights Agreement and Contract Signature Workflow

When a title is acquired or a rights deal is negotiated in Consonance, the system can trigger a signature request in OpenText Core Signature for author contracts, licensing agreements, translation rights, or subsidiary rights deals.

• Data flow: Consonance to OpenText Core Signature
• Business value: Speeds up deal closure and reduces manual emailing of contracts
• Operational benefit: Signed documents are returned to Consonance and attached to the title or rights record for a complete audit trail

2. Editorial Approval of Manuscript Release Documents

Before a manuscript moves from editorial development to production, Consonance can route approval forms, author sign-off sheets, or final content release documents to OpenText Core Signature for formal approval.

• Data flow: Consonance to OpenText Core Signature, then back to Consonance
• Business value: Ensures no title advances without documented approval
• Operational benefit: Reduces production delays caused by missing signatures or unclear approval status

3. Production and Print Release Authorization

For print-ready files, cover approvals, or final proof sign-off, Consonance can initiate a signature workflow so production managers, editors, and stakeholders can approve release to print through OpenText Core Signature.

• Data flow: Consonance to OpenText Core Signature
• Business value: Prevents costly reprints and last-minute production errors
• Operational benefit: Signed release documents are stored against the title record and can be used as evidence of approval

4. Author and Contributor Approval for Metadata and Marketing Copy

Consonance can send final metadata sheets, jacket copy, author bios, or marketing claims to OpenText Core Signature when author approval is required before publication or campaign launch.

• Data flow: Consonance to OpenText Core Signature
• Business value: Improves accuracy of published metadata and reduces post-publication corrections
• Operational benefit: Approved content is linked back to the title record for downstream distribution and retailer feeds

5. Royalty Statement Acceptance and Acknowledgment

When royalty statements are generated in Consonance, the platform can send acknowledgment or acceptance forms to OpenText Core Signature for author confirmation, especially where contractual acceptance is required.

• Data flow: Consonance to OpenText Core Signature, with signed acknowledgment returned to Consonance
• Business value: Creates a formal record of statement receipt and acceptance
• Operational benefit: Helps finance and rights teams resolve disputes faster with signed evidence

6. Rights Renewal and Expiration Notice Sign-Off

For time-sensitive rights renewals, Consonance can generate renewal agreements or extension notices and send them to OpenText Core Signature for signature by authors, agents, or licensors.

• Data flow: Consonance to OpenText Core Signature
• Business value: Protects valuable rights by accelerating renewal turnaround
• Operational benefit: Signed renewals are captured in the rights workflow, reducing the risk of missed deadlines

7. Cross-Functional Approval for Multi-Format Publishing

For titles released in print, ebook, and audio formats, Consonance can coordinate a single approval package that includes format-specific release documents, which are then signed in OpenText Core Signature by the relevant stakeholders.

• Data flow: Consonance to OpenText Core Signature
• Business value: Supports coordinated approvals across editorial, production, and digital teams
• Operational benefit: Ensures each format is approved before distribution, reducing launch inconsistencies

Overall, integrating Consonance with OpenText Core Signature creates a controlled approval layer across publishing workflows. It improves compliance, shortens cycle times, and gives publishers a single operational record that connects workflow status, signed approvals, and title metadata.