Module quick menu
FormKiQ document management modules extend the platform with higher-value capabilities while keeping one architecture, one governance model, and one deployment approach.
Modules help teams scale from foundational document operations to advanced automation, intelligent processing, and AI-powered discovery — without replacing core systems or introducing separate infrastructure to manage.
Modules are available as add-ons to FormKiQ Advanced and FormKiQ Enterprise.
Document Generation
Produce structured, repeatable documents from templates and data — contracts, notices, reports, correspondence, and other governed outputs — without manual assembly or downstream formatting work. Document Generation supports both PDF and Word document formats, allowing organizations to generate output that matches existing document standards and downstream workflow requirements.
Document Generation is designed for workflows where document output is a defined business process: the same template, applied consistently, with controlled inputs and an auditable result. It integrates with FormKiQ's metadata and workflow layers, so generated documents are stored, classified, and governed the same way as any other document in the platform.
When to use it
High-volume contracts, notices, certificates, and decision letters where consistency, auditability, and workflow integration matter. Programs that require PDF manipulation as part of intake or output workflows.
Common fit
Advanced and Enterprise; frequently used in Contract Management, Grants Management, Case Management, Claims Management, and Policy and Procedure Management programs.
Capabilities
1. Document Generation from Templates and Data
Generate structured documents by combining predefined templates with data sourced from FormKiQ metadata, external system inputs, or structured JSON payloads — producing consistent, correctly formatted document output without manual assembly. Templates define the structure, layout, and fixed content of the document while the data input populates the variable elements: names, dates, amounts, identifiers, decision outcomes, and any other content that changes between instances of the same document type.
Integration with FormKiQ's metadata layer means that data already captured on a document record can be used directly as generation inputs. Integration with external systems through the FormKiQ API and Integration Framework modules allows generation to be triggered by events in ERP, CRM, case management, and other connected systems. Generated documents are routed into downstream workflows — for review, approval, or eSignature — immediately on generation.
Common fits: contract drafting from counterparty and term data, grant award and rejection letters from application review outcomes, case correspondence from case record attributes, regulatory notices from compliance assessment results, HR correspondence from employee record data.
2. PDF File Splitting and Joining
Split multi-page PDF documents into individual component documents, or combine multiple PDF documents into a single consolidated file — as part of an automated workflow or on demand through the FormKiQ API.
PDF splitting is valuable for intake workflows where documents arrive as multi-page PDFs containing multiple distinct document types — allowing each component to be extracted, classified, and governed as an independent document record. PDF joining is valuable for output workflows where multiple document components need to be assembled into a single deliverable. Both operations are available as Document Actions within a workflow, and each resulting document is stored in FormKiQ with full provenance metadata recording its origin.
Common fits: multi-document submission intake in grants, insurance, and regulatory programs; contract assembly with schedules and annexes; case file compilation; correspondence assembly for multi-recipient programs.
3. PDF Certificates and Attestation Documents
Generate signed PDF certificates — documents that carry a verifiable record of a specific event, outcome, decision, or attestation — as governed, tamper-evident records that can be issued, distributed, and verified within FormKiQ's document management framework.
PDF certificates include a verifiable record of their generation — the timestamp of issuance, the data inputs used, the template applied, and the FormKiQ record from which they were produced. Certificate generation integrates with FormKiQ's workflow and metadata layers — certificates can be generated automatically when a workflow reaches a defined milestone, issued in response to a review outcome, or produced on demand through the API.
Common fits: training and course completion certificates, professional development and continuing education records, compliance attestation documents, grant award certificates, inspection and audit completion records, identity and credential verification certificates.
Module configuration and workflow integration
All three Document Generation capabilities integrate with FormKiQ's workflow, metadata, and event architecture — generation, splitting, joining, and certificate issuance can all be triggered as Document Actions within a defined workflow, with Document Events published on completion to notify connected systems and trigger downstream processes. For programs that combine Document Generation with eSignature Integration, generated documents can be routed directly to a signature workflow on creation, with the signed result returned to FormKiQ completing the generation-to-execution lifecycle within a single automated process.
eSignature Integration
Add controlled signature workflows to document processes without routing documents outside your governed environment. FormKiQ's eSignature Integration supports DocuSign natively and extends to other providers — including Adobe Sign and comparable platforms — through a bring-your-own-license (BYOL) model, allowing organizations to connect FormKiQ to an existing eSignature relationship rather than adopting a new one.
Signature workflows can be triggered from existing document processes, linked to approval and routing steps, and configured to meet the audit and evidentiary requirements of your specific use case. Signed documents are returned, stored, and classified within your FormKiQ deployment, with a complete chain of custody.
Common fits: contract execution, policy acknowledgment, consent and authorization workflows, and any process where a signed document is the required output before a workflow can proceed.
When to use it
Approval-intensive processes requiring secure signature checkpoints with a full audit trail.
Common fit
Advanced and Enterprise; typically paired with Contract and Case Management.
AI Processing and Analysis
Intelligent document processing powered by Amazon Bedrock and running entirely within your AWS account. Because all AI processing happens through Bedrock within your own deployment, your documents never leave your cloud environment. Inference region controls allow you to define which geographic areas are used for model processing, ensuring that document content stays within the boundaries required by your data residency and sovereignty obligations.
The module covers the full spectrum of intelligent document processing — from classification and extraction through summarization, analysis, generation, and vision processing — using the large language models available through Amazon Bedrock, including Anthropic Claude, Amazon Nova, and other supported models. Individual capabilities can be enabled selectively for specific document types, workflows, or intake pipelines without applying AI processing uniformly across the entire document collection. All processing runs within your AWS account under your access control model, and every AI action is logged in FormKiQ's audit trail.
When to use it
Complex intake and review workflows that require faster processing and better consistency across unstructured document types.
Common fit
Advanced and Enterprise; widely used in Case and Grants Management.
Capabilities
1. Document Type Classification
Automatically identify and classify the type of each document as it enters FormKiQ — determining whether an incoming document is a contract, invoice, application, correspondence, report, identification document, or any other category relevant to your document program — and applying the appropriate classification schema, metadata attributes, and workflow routing based on that determination.
Classification models can be configured to the specific document types relevant to your program, with confidence scoring that routes low-confidence classifications to a human review queue rather than applying them directly.
Common fits: high-volume mixed document intake, mailroom digitization, insurance and financial services intake, grants and applications processing, and any workflow where incoming documents need to be classified before routing.
2. Content Sensitivity Classification
Automatically identify and classify the sensitivity level of document content — detecting the presence of PII, PHI, financial data, legally privileged content, confidential business information, and other sensitive content categories — and applying appropriate access controls, handling requirements, and metadata attributes based on the sensitivity determination.
Sensitivity classifications can trigger downstream actions — escalating access restrictions, routing to a restricted review queue, flagging for data protection impact assessment, or initiating a privacy officer notification. Sensitivity models can be configured to the specific data categories relevant to your regulatory obligations.
Common fits: regulated document intake programs with data protection obligations, healthcare document processing requiring PHI detection, legal document review for privilege detection, HR and financial services document intake.
3. Metadata Extraction
Automatically extract structured metadata from document content at the point of ingestion — identifying and populating key attributes such as dates, names, organization identifiers, reference numbers, amounts, addresses, and other structured data elements — and applying those extracted values as FormKiQ metadata attributes without manual data entry.
Extraction models are configured to the specific fields relevant to each document type. Extraction confidence scoring allows low-confidence extractions to be flagged for human review rather than applied directly, maintaining metadata quality without requiring manual review of every document.
Common fits: contract and legal document processing, accounts payable and invoice processing, grants and applications intake, insurance claims, HR document processing, records digitization programs.
4. Document Summarization
Automatically generate concise, accurate summaries of document content — capturing key points, decisions, obligations, and context — and storing those summaries as searchable metadata attributes alongside the original document record.
Summaries are searchable through FormKiQ's search layer and available to the KnowledgeBase module's retrieval model. Summarization can be configured to produce different formats for different document types — structured summaries of parties and obligations for contracts, decision and action item summaries for meeting minutes.
Common fits: contract and legal document review, board and committee documentation, policy management, research programs, case file review, regulatory document processing, and any environment where document volume exceeds the practical capacity for full manual reading.
5. Document Analysis
Apply structured analytical reasoning to document content — evaluating documents against defined criteria, identifying obligations and commitments, assessing compliance with requirements, comparing document content against reference standards, and producing structured analytical outputs that support downstream review, decision-making, and governance.
Analytical use cases vary by domain: contract analysis identifies obligations, termination conditions, and non-standard terms; compliance document analysis assesses whether submitted documents meet defined requirements; application analysis evaluates submissions against eligibility criteria. Analytical outputs are stored as structured metadata attributes and can trigger workflow routing decisions.
Common fits: contract lifecycle management, regulatory submission review, grants eligibility assessment, vendor qualification documentation review, policy governance, compliance monitoring.
6. Document and Content Generation
Automatically generate structured document content — drafts, responses, summaries, notices, and reports — using document content, metadata attributes, and defined templates as inputs. This capability is complementary to the Document Generation module: AI content generation produces free-form or semi-structured text based on reasoning over existing document content, while Document Generation formats and outputs that content as a governed PDF or Word document.
Generated content is stored in FormKiQ as a document record with full metadata, version history, and audit trail — including the generation inputs, model used, and generation timestamp — so the provenance of AI-generated content is always traceable.
Common fits: correspondence and response management, claims and adjudication communication, freedom of information response drafting, grants and regulatory communication, case management correspondence, compliance reporting.
7. Vision and Multi-Modal Document Processing
Process documents that contain visual content — images, diagrams, photographs, mixed-content pages, handwritten forms, and other non-textual or partially textual document types — using Amazon Bedrock's vision-capable models to extract meaning, classify content, and generate structured outputs from visual document elements that text-based OCR cannot fully address.
Vision processing use cases include handwritten document and form processing, image and photograph classification and analysis, mixed-content document analysis, form and document layout understanding, and identity and credential document processing. Vision processing outputs are stored as FormKiQ metadata attributes alongside outputs from text-based processing.
Common fits: insurance claims image processing, property inspection documentation, grants programs accepting handwritten submissions, healthcare document processing with clinical images, identity and credential verification, construction and engineering document programs with mixed technical and visual content.
Module configuration and inference region controls
All seven capabilities run on Amazon Bedrock within your AWS account using supported large language models — including Anthropic Claude, Amazon Nova, and other available models. Each capability can be enabled independently and applied selectively to specific document types, intake workflows, or sites within a multi-tenant deployment, allowing AI processing to be introduced incrementally and validated against specific document categories before being expanded.
Enhanced Full-Text Search
Full-text search across large document repositories, with relevance tuning, faceted filtering, and metadata-aware query construction. FormKiQ's Enhanced Full-Text Search module extends the platform's baseline search capability for organizations where search performance, result quality, and query flexibility are operational requirements rather than conveniences.
Search operates across document content and metadata simultaneously, supporting complex queries, multi-field filtering, and result ranking based on document attributes and relevance signals. For organizations with large archives, records programs, or high-frequency retrieval workflows, Enhanced Full-Text Search provides the discovery layer that makes those collections operationally useful.
Common fits: archives and special collections, grants and records programs, legal document repositories, knowledge management programs, and any deployment where the document collection is large enough that baseline search creates retrieval bottlenecks.
When to use it
High-volume environments that require fast retrieval and defensible response workflows across large document collections.
Common fit
Advanced and Enterprise; especially important for Records, Archives, and Legal use cases.
KnowledgeBase — powered by Amazon Bedrock
AI-powered document intelligence for natural language query, synthesis, and knowledge retrieval — built on Amazon Bedrock and operating entirely within your AWS deployment.
FormKiQ's KnowledgeBase module connects your document repository to large language model capabilities, allowing users to ask natural language questions and receive answers synthesized from the actual content of your documents — with source attribution, so every response can be traced back to the underlying records. This is not a generic AI assistant: it is a retrieval-augmented generation (RAG) system scoped to your document collection, operating under your governance and access control model.
Because KnowledgeBase runs on Amazon Bedrock within your AWS account, your documents are never sent to a third-party AI service. Inference region controls allow you to define which geographic areas are used for model processing, keeping document content within the boundaries required by your data residency and sovereignty program. Access policies, audit trails, and deployment boundaries are the same as the rest of your FormKiQ environment. Users only receive answers drawn from documents they are authorized to access.
Common fits: internal knowledge management, policy and procedure retrieval, research and archives programs, legal and compliance reference, case preparation, and any environment where staff need to find and synthesize information from large document collections quickly and accurately.
When to use it
Large document collections where staff need to find and synthesize information through natural language queries rather than keyword search.
Common fit
Advanced and Enterprise; widely used in Knowledge Management, Research, Case Management, and Policy programs.
Key capabilities
- Natural language query against your document repository
- Retrieval-augmented generation scoped to your collection and access model
- Source attribution — every answer linked to the originating document
- Runs on Amazon Bedrock within your AWS account — no data leaves your environment
- Inference region controls for data residency and sovereignty compliance
- Respects existing FormKiQ access controls — users see only what they are authorized to access
- Audit trails for queries and retrievals consistent with the rest of the platform
How modules map to editions and use cases
Modules are available as add-ons to FormKiQ Advanced and FormKiQ Enterprise, and can be adopted individually or in combination depending on your operational requirements.
| Module | Primary use case | Common solution fit |
|---|---|---|
| Document Generation | Repeatable, governed document output — PDF and Word | Contracts, cases, grants, regulatory correspondence |
| eSignature Integration | Controlled signature workflows — DocuSign, Adobe Sign, BYOL | Contract execution, consent, policy acknowledgment |
| AI Processing and Analysis | Intake, document classification, content sensitivity classification, extraction, multi-modal | High-volume intake, records digitization, mixed-content workflows |
| Enhanced Full-Text Search | Large repository discovery and retrieval | Archives, records programs, legal repositories |
| KnowledgeBase | Natural language document intelligence with inference region controls | Knowledge management, research, policy retrieval, case preparation |
Modules operate within the same governance and deployment boundaries as the core platform. Adding a module does not change your deployment model, your access control architecture, or your compliance posture.
For architecture-level planning, pair modules with FormKiQ's Document Gateways to define how documents enter the platform and Integration Frameworks to connect document workflows to your existing enterprise systems.
How modules map to FormKiQ editions
| Module | FormKiQ Advanced | FormKiQ Enterprise |
|---|---|---|
| Document Generation | Available | Available |
| eSignature Integration | Available | Available |
| AI Processing and Analysis | Available | Available |
| Enhanced Full-Text Search | Available | Available |
| KnowledgeBase | Available | Available |
FAQ: Document management modules
Do modules require replacing our existing FormKiQ deployment?
No. Modules are designed as additive capability expansions. They extend your existing deployment without requiring architectural changes or replatforming.
Which module is best first for operational automation?
Many teams start with Document Generation or AI Processing and Analysis depending on whether output automation or intake automation is the immediate need. For organizations with large existing collections, Enhanced Full-Text Search or KnowledgeBase are often the highest-impact starting points.
Can modules support compliance and governance goals?
Yes. Modules operate within the same governance and deployment boundaries as the core platform — the same access controls, audit trails, retention policies, and regional deployment constraints apply.
Does the AI processing stay within our cloud environment?
Yes. Both AI Processing and Analysis and KnowledgeBase run on Amazon Bedrock within your own AWS account. Your documents are processed and queried entirely within your deployment boundary. Inference region controls give you additional specificity over which geographic areas are used for model processing, supporting data residency and sovereignty requirements.
We already have a DocuSign or Adobe Sign contract. Can we use it with FormKiQ?
Yes. eSignature Integration supports a bring-your-own-license model, so organizations with existing DocuSign or Adobe Sign agreements can connect their current eSignature provider to FormKiQ without adopting a new licensing relationship.
Can multiple modules be combined in a single deployment?
Yes. Modules are designed to work together. A common combination for regulated document programs is AI Processing and Analysis for intake, Enhanced Full-Text Search for retrieval, Document Generation for output, eSignature Integration for execution, and KnowledgeBase for knowledge access — all running within a single FormKiQ deployment under one governance model.
Talk to FormKiQ About Modules
Learn About FormKiQ Advanced · Learn About FormKiQ Enterprise · Review Document Gateways · Review Integration Frameworks