Jigani

Process – Vendor Contract Repository Intake

Bommasandra.com

Vendor Contract Repository Intake

Store vendor contracts with metadata, documents, renewal terms, owner, and compliance classification.

Requester

Requester Name * Enter the accountable person who owns this workflow request. Requester Email * Use a monitored business email for approvals and audit communication. Organization * Company, customer, vendor, partner, or internal business unit name. Business Unit * Select the owning function so routing and reports stay clean. Region * Used for regional manager assignment and location-wise reporting.

Control

Priority * Select urgency based on business impact and committed customer dates. Workflow Category * Controls domain reporting and default dashboard grouping. Target Completion Date * Date by which the workflow outcome is expected.

Commercial

Estimated Value Estimated revenue, cost, refund, claim, order, or budget amount. Currency * Currency used for reporting and approval limits.

Repository

Vendor Category *

Evidence

Contract Document *

Supporting Attachments

Upload approvals, invoices, screenshots, identity documents, contracts, or evidence. Reference Images

Add visual proof or supporting screenshots where useful.

Approval

Approval Required * Select the highest approval gate required before completion. Approver Email Optional approver mailbox for workflow notifications.

Details

Business Justification * Explain why this workflow is needed, expected outcome, risk, and dependencies. Operational Notes Add special instructions, exceptions, dependencies, or handover details.