Published Updated

FormKiQ connects documents with the business context needed to act on them: metadata, schemas, relationships, and workflows. Teams can adopt a packaged Business Solution or use the platform’s APIs to embed document capabilities in their own application.
A file is one part of a record. Its attributes may identify the customer, case, classification, responsible team, and lifecycle state. Schemas make required metadata explicit; relationships connect supporting evidence to the business context.
Use stable identifiers for companies, cases, contracts, and other related entities. Keep display names separate from identity so a renamed customer or reorganised business unit does not break the relationship. Validate the supported entity and relationship features in the deployed release.
A packaged FormKiQ Business Solution provides a usable application for a defined workflow. Configure organisation-specific rules and integrate the required systems around that workflow.
For a custom product, the platform provides document capabilities through APIs and the console, while the product team owns its interface and specialised business logic. Commercial workflows and selected processing modules depend on the chosen edition and scope.
Define which events move a record from submitted to review, approved, or issued. A status attribute alone does not enforce an approval policy. Combine permitted transitions, access rules, review tasks, and audit evidence.
Design query patterns and indexes alongside the model. Avoid assuming that flexible attributes make every filter equally efficient or that platform adoption removes the need to test integration and operating behaviour.
Connect files to stable business entities and references.
Apply the classification schema and transition rules.
Review, generate, or integrate through the configured workflow.
A company has two business units and several supplier agreements. Each agreement keeps its own identity, relates to the company and responsible unit, and has supporting files. A change of unit name updates the displayed business context without renaming every document. Approval and later amendment events preserve the agreement’s history and the responsible reviewer.
A clear record model makes documents usable across an application. Prove its identities, rules, relationships, and handoffs with a representative business scenario.
Bring a representative document set, the intended users, and the acceptance criteria. Explore the relevant FormKiQ capabilities or discuss the workflow with our team.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.