Skip to main content

Use Contract Management

This walkthrough uses a fictional Service Agreement in a configured FormKiQ Web v4.3.8 workspace. An administrator must first configure the solution. The labels and actions you see depend on workspace configuration, permissions, and enabled services.

1. Find your work​

Open Contract Management from the workspace's modules. The agreement register lists accessible agreements. My Agreements limits that view to accessible agreements whose primary document was created by you; it is not a separate storage location or an authorization boundary.

Open Tasks for assigned reviews, responses to requested changes, signature requests, and renewal reviews. My Tasks matches your signed-in email; Team Tasks remains limited to agreements you may access. A suggested reviewer does not receive an assigned task until the assignment is recorded.

2. Capture an agreement​

Upload the draft document using the available intake action, or start the configured template-generation flow. Select the agreement type and complete Step 2: Complete agreement details. Check the parties, owners, department, currency/value, relevant dates, risk, and sensitivity.

With ingestion disabled, complete details manually. PDF text-layer suggestions can help fill empty fields, but do not perform OCR or establish that the extracted facts are correct. Where AI ingestion is enabled, review its output against the actual document before requesting review. AI-ingested and later-stage metadata may require administrator correction.

Check the Documents and Revisions views. Use the normal revision process for changed content; replacing a signed or reviewed file through a recovery action is not a revision workflow.

3. Request review​

Choose the configured review process, confirm the document package and reviewer assignments, and start review. The package identifies the revisions being reviewed. Configured reviewer pools, backend approval groups, and delegation rules determine who can act.

The assigned reviewer opens the task's Review tab and reads the pinned document package. Depending on the process, they can approve, request changes, or record another configured decision. Post Comment records a note without resolving the task or advancing the process when the backend identifies comments as non-counting decisions.

If an action is unavailable, check the named assignment, identity-group membership, workspace permissions, review state, and whether the document package can be read. Being a platform administrator is not a bypass for a required reviewer approval group.

4. Respond to requested changes​

The response task belongs to the agreement owner and review requester, with business-owner fallback where those are absent. Explain how the request was addressed and add the required document revision or supplemental documents.

Resubmission restarts the entire review process from its first step. Earlier approvals and not-required decisions do not carry forward. If the main document is unchanged, the available Addressed without main revision — restart review action still creates a new first-step review and records the explanation and package. It does not approve or rewrite the old rejected review.

An authorized assigned reviewer can cancel an entire open review where configuration permits. Read the confirmation and provide a reason; cancellation closes pending review work and restores the saved pre-review agreement state. It differs from requesting changes.

5. Prepare signing​

After the required reviews, open eSignature if the workspace has the signing integration enabled. Check recipients, documents, routing order, and the sending environment before sending.

The released integration uses DocuSign. Ready signers and signers waiting for an earlier recipient have different task states. Completed recipients and copy recipients are not actionable signing tasks. DocuSign enforces recipient order and supplies the signing evidence.

Built-in FormKiQ eSignature is not implied by a visible signing action. Do not mark a document signed solely because a request was sent.

6. Activate and maintain the agreement​

Use the configured lifecycle transition after signing or other required checks. Review the transition preview, including affected work, and confirm. Lifecycle coordination records completed operations for retry; changes across multiple records are not a single atomic backend transaction.

Check the effective expiry date, owners, milestones, obligations, and any scheduled reminders. Activation uses the saved expiry reminder policy and snapshots its recipients; later metadata edits do not automatically reschedule reminders. Handle amendments and linked instruments through their own selected record and document/review history.

Use native retention and legal hold controls for governance. A custom business retention field or a lifecycle status alone does not apply a backend legal hold.

7. Use tasks and reports​

Return to Tasks for ongoing assigned work. Review tasks open Review; signature tasks open eSignature. Resolve incomplete-list or permission warnings before concluding that no tasks exist.

Reports → Operational Reports summarizes the agreement data available to the current user. Use the offered filters and report/export controls to inspect lifecycle, review, signing, and expiry work. Reports do not grant access to additional agreements. An incomplete data warning means the result is partial, not a complete inventory. Reconcile audit-sensitive exports with backend records and retain the filters and time of extraction.

Troubleshooting​

SymptomCheck
Agreement type or template is missingEnabled state, department mappings, selected workspace, template registration, and your permissions.
Assigned reviewer cannot decideExact backend approval-group claims, named assignment, open review, and document-package access. Reassign legacy reviews after fixing pool configuration if necessary.
A task is missingRecorded assignment, signed-in email, agreement visibility, completed/terminal state, and any incomplete-list warning.
A reminder did not arriveSaved opt-in policy at activation, valid expiry/recipients, provider setup, scheduler operation, and notification status.
Saving a lifecycle transition partially failsKeep the recorded state and use the offered retry. Do not repeat unrelated destructive operations or assume the whole transition rolled back.

See the configuration guide and document reviews for the underlying distinctions.