> ## Documentation Index > Fetch the complete documentation index at: https://seal-d2ca5bea.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Custom software change control > Managing change control for your existing software systems through Seal. If your organisation develops custom software—whether internal tools, lab systems, or production applications—you need a robust change control process to maintain compliance. Seal can serve as your single source of truth for managing software changes alongside all other GxP-controlled documentation. ## Why manage software changes in Seal? Custom software in regulated environments requires the same rigor as any other controlled document: formal change requests, impact assessments, review and approval workflows, and complete audit trails. By managing software change control through Seal, you get: * **Unified change control** — Software changes follow the same approval workflows as SOPs, batch records, and other controlled documents * **Traceability** — Link software changes to related documentation, validation protocols, and training requirements * **Audit-ready records** — Complete history of who requested, reviewed, approved, and implemented each change * **Risk-based workflows** — Configure review requirements based on the impact and risk level of changes ## How it works You can manage software change control in Seal by creating entity types for change requests, linking them to your development workflow, and configuring appropriate review requirements. Changes flow through your defined approval process before implementation, with full audit trail capture. For teams using GitHub, we offer a direct integration that connects your pull requests to Seal's change control workflow. Automate change control for GitHub repositories with built-in compliance workflows. The GitHub integration automatically creates change records in Seal when pull requests are opened, routes them through your configured review process, and ensures code changes are only merged after proper approval. This provides end-to-end traceability from change request through deployment.