<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=691116991096043&amp;ev=PageView&amp;noscript=1">
Skip to content
  • There are no suggestions because the search field is empty.

πŸ›  Create Your Own - Internal Contract Request Workflow

This article explains how to configure the Internal Contract Request workflow in Gatekeeper, handling the data input, approvals and setup actions required to get a new contract live in your Gatekeeper repository. It covers mandatory configuration steps and optional enhancements to tailor the process to your organisation’s needs.

Take Control

  Estimated Read Time: 10 Minutes

  Estimated Configuration Time: 1-3 hours


Sections in this article:



Introduction

This Internal Contract Request workflow allows you to fully digitise your request intake, negotiation, approval, and signing processes for new contracts. It helps ensure that every contract added to Gatekeeper is reviewed and approved by the right people, contains complete metadata, and includes a full version history of both the form and the executed contract. See the demonstration video or follow the steps below to learn more:

 

Workflow Diagram: XML / PDF

 
 

 

πŸ›  Mandatory Configuration πŸ› 

The steps in this section outline the essential setup required to make your workflow fully functional.

The ⬇️ Additional Configuration ⬇️ section covers optional additions to expand the scope of your process or tailor the workflow to better align with your organisation’s unique policies, procedures, and Gatekeeper subscription features.

Add the Template

To get started, you'll need to add the template workflow:

  1. From the navigation menu, click Workflows.
  2. Click Add, then select Workflow Template.
  3. Click Create on the Internal Contract Requests template.
  4. Amend the title if needed, then click Create.

Configure AutoAction Values

Near the start of the workflow, an automatic action takes the contract metadata from the request form and converts it into a record in your contract repository. You can configure this action to define which metadata values are taken from the form, and which are set as default or placeholder values:

  1. Click the πŸ›  AutoCreate Contract πŸ›  phase to edit it.
  2. From Actions, click Edit AutoAction Values for the enabled AutoAction.
  3.  At the top, select the Take Value from Form checkbox.
  4. Where needed, select backup values from the dropdown lists for any fields that may be left blank, with particular attention to mandatory fields.
  5. Deselect the Take Value from Form checkbox for the Status and Approval fields. Select the values for these to be Pipeline and Awaiting Approval. This ensures that, if users view the contract in the repository, they will see that it is not yet approved or executed.

  6. Click Save.

ConfigureCreateAutoAction-gif-1

Configure Contract Templates

This workflow can use eNegotiate contract templates to create the first draft of a contract. Templates can also be generated automatically based on data provided by the requestor and initial approver(s).

Part 1 - Create the Templates
  1. From the navigation menu, expand the Settings option, then click Configuration.
  2. Click eNegotiate Contract Templates.
  3. Click Add MS Word Template.
  4. Use the Handlebar Instructions document to set up all dynamic or configurable sections in your Microsoft Word template. For detailed guidance, see πŸ“– Configure Contract Templates.
  5. Once finished, upload your MS Word template as the Document file.
  6. Complete the mandatory fields, then select Live from the Status dropdown list to make the template available for use in your workflow.
  7. Once finished, click Save.
  8. Repeat steps 3 - 7 until all required contract templates have been added.

Part 2 - Apply the Templates to the Workflow 
  1. Click the πŸ›  AutoCreate Draft πŸ›  phase to edit it.
  2. From Actions, click Edit AutoAction Values on AutoAction | Generate Draft from Contract.
  3. Select the relevant templates you want Gatekeeper to use for this action, then click Save.

SelectTemplates-gif-1

Note: Users can also manually select a template on the Draft Review πŸ“‘ phase if the AutoAction does not generate a draft.

Assign Contract Negotiation Owners

There are several steps in the contract setup and negotiation process within this workflow. Configure owners for the phases below to reflect how responsibility is normally assigned in your organisation:

Phase Description
Draft Review πŸ“‘

The initial draft is selected and marked up before being sent to the vendor for negotiation.

If Gatekeeper has generated the draft from a contract template, users may only need to make final tweaks.

If no Gatekeeper template was used, users should assign a Draft Version 1 (for example, a vendor-supplied draft), then make amendments before sending it for vendor review.

Internal eNegotiate πŸ§‘β€πŸ’Ό

The latest draft version will be reviewed and redlined internally.
Draft Finalisations β˜‘οΈ β˜‘οΈ β˜‘οΈ

Final tidy-up of the draft, including accepting redlines, closing comments, and correcting typos, before sending the contract for final internal approval and signature.

eSign ✍️

The eSign process is initiated, including assigning signatories and configuring the document for signing. The contract can be signed using Gatekeeper eSign or via the DocuSign integration.

 

External Signature ✍️ Represents any contract signatures that occur outside of Gatekeeper (for example, when a vendor requires use of their own eSign tool).

To assign owners:

  1. Click on a phase where the owner needs configuring to edit it. 
  2. From Form Access, select the relevant radio button to determine how ownership is assigned.

Repeat these steps until owners have been assigned for all the phases outlined in the table. 

assign form access CRQ

Note: See πŸ“– Form Access Masterclass for more detail on assigning owners to phases.

 

Assign Approver/s

The Final Approvals βœ… phase is the last opportunity for internal stakeholders to review the agreement before signing. Consider who should be included here:

  • Which budget holder needs to review the commitment?
  • Which teams need to verify compliance and risk-mitigating clauses?
  • Which executives may want to approve, particularly for high-value contracts?

There are multiple options for approvals. Expand the relevant section to learn more, depending on your requirements.

Option 1: Simple Approval βœ…
Simple approvals can be used when only one user or group needs to approve new contracts. To configure this:
  1. Click on the approval phase to edit it.
  2. From Approval, ensure that the Enabled and Single radio buttons are selected.
Simple Approval Settings
  1. From Form Access, select the user/group who should provide the approval. If you select multiple users or groups, only one needs to approve the request for it to progress past this phase on the Kanban board.
Assign Approver

 

Option 2: Parallel Approvals βœ…βœ…βœ…
Parallel approvals can be used if multiple users/groups need to approve new contract requests. To configure this:
  1. Click on the approval phase to edit it.
  2. From Approval, select the Parallel radio button.
Parallel Approval Settings
  1. Select the required users/groups then click Save. All selected users/groups must approve for the contract to progress past this phase.
Parallel Approvals User Selection

 

Option 3: Conditional Parallel Approvals πŸ”€
Conditional parallel approvals can be used when multiple users or groups need to approve contract requests, and the required approvers may vary depending on the scope of the request. To configure this:
  1. Click on the approval phase to edit it.
  2. From Approval, select the Parallel radio button.
Parallel Approval Settings
  1. Select the required users/groups, then select the Conditional radio button and click Save.
  2. Click βž• ADD to assign conditions for the selected user/group to require approval.
  3. Click Add New Parallel Approval and repeat until all conditional approvers are set.

Gatekeeper will evaluate each rule and apply the relevant approvers when the workflow card meets the defined conditions.

 

Configure Vendor Selection Options 

You need to decide whether users can select new vendors when requesting contracts, or if they must choose from vendors already added and onboarded in Gatekeeper. This decision will likely depend on whether your organisation has a formal vendor onboarding process, and whether a Gatekeeper workflow is in place to support it.

Note: By default, users will have the option to select an existing vendor or enter the name of a new one. If they enter a new vendor, this will require manual input to create the vendor as the Create Contract AutoAction will fail if it cannot be linked to an existing vendor record.

Expand the relevant option to learn more:

Only Existing Vendors
If your organisation prioritises vendor management and due diligence, consider restricting the form so users can only select vendors already added and onboarded in Gatekeeper:
  1. Click the New Contract Request Form phase to edit it.
  2. From Form, expand the 3 dots on the Vendor Name field then click the pencil icon pencil icon.
  3. Select the Select Existing Dropdown Values Only radio button, then click Save.
Existing Vendors Only GIF
See πŸ“– Only Onboarded Vendors for further context about this scenario.

 

New or Existing Vendors
If you want to make the contract request process simpler for users, you can opt to allow both cases. However, for a valid contract record to be created with a new vendor, this vendor record must be created on the workflow. This step can be automated:
  1. Navigate to the right hand side of the workflow board.
  2. Next to New Phase, click ADD.
  3. Enter πŸ› οΈ AutoCreate Vendor πŸ› οΈ as the title, then click Save & Next.
  4. Click Reorder Icon Reorder to move the phase to before AutoCreate Contract in your workflow, and select the Minimise checkbox.
  5. From Actions, select the AutoAction | Create Vendor checkbox.
  6. Select the Update Form on Action and Submit Card on Action checkboxes, then click Edit AutoActon Values to set how Gatekeeper will populate new records.
  7. From Transitions, select the πŸ› οΈ AutoCreate Contract πŸ› οΈ radio button.
  8. Click the Initial Review βœ… phase to edit it, and from Transitions, select the new πŸ› οΈ AutoCreate Vendor πŸ› οΈ radio button within IF APPROVED.
Note: Duplicate vendor records will not be created. If the AutoAction detects that the vendor already exists, it will skip this step and move to the next stage of the workflow.

 

New or Existing Vendors with Automated Onboarding
To reduce friction, you can allow users to request contracts with new vendors while triggering the onboarding process at the same time.
  • This minimises delays and frustrations when requesting contracts.
  • It also shortens the turnaround time by running contract negotiations and approvals alongside vendor due diligence checks.

To learn more about setting this up, see πŸ“– Parallel Workflows - Contract Request x Vendor Onboarding.

 

πŸ›  Additional Configuration πŸ› 

This section covers optional steps to adjust the workflow’s scope or default settings, helping you tailor it to your organisation’s needs.

Leverage LuminIQ in Workflow Forms

With LuminIQ, data can be automatically extracted from uploaded contract documents and used to populate the core details of the form. This can be used for contract requests submitted via the Submit Requests dashboard. To enable this:

  1. Click to edit the start phase.
  2. From Form Access, select the Create Card from Contract checkbox under Lumin Intake.

create card from contract

 

Add Custom Data

By default, this workflow includes the contract and vendor core data fields. If you have created custom metadata, you can add the fields to the workflow form so that:

  • The values are saved to the finalised record in the repository, and can be used for filtering, saved views, and reporting.
  • The values can be pulled into a contract document when generating a draft from a contract template.

To do this:

  1. Click on the start phase of the workflow to edit it. 
  2. Navigate to Form, then click ADD SECTION and enter a section name.
  3. Select the following from the dropdown lists:
    1. Predefined: Contract
    2. Custom Data Group: The custom group you want to add.
  4. Click Save.
  5. Click REORDER to move the new section to your preferred position in the form.

AddContractCustomDataForm-gif-1

Set Visibility Rules

Once you add a form section, it will be Editable by default in the current phase, and Read Only in all other phases. You can adjust this for specific phases of the workflow if needed:

  1. Click the settings icon to access the Configuration View.
    configure workflow
  2. To set the section visibility, hover over the relevant section box and select from the dropdown list.
    section visibility-1
  3. To set the field visibility:
    1. Hover over the section box and select the appropriate checkbox to apply the visibility to all fields within the section.
    2. Hover over an individual field box and select from the dropdown list to apply the visibility to fields one-by-one.
  4. To copy a section/field visibility settings to other phases, click the copy icon. Then, select the checkboxes to determine which phases you want to copy the settings to, and click Copy.
    copy icon-1
Set AutoAction Values

For any additional custom metadata sections, you need to ensure the contract record is updated with the values from these fields in any AutoAction phases. In the template, you may configure these values on the following phases:

  • πŸ›  AutoCreate Contract πŸ› 
    This phase exists near the start of the workflow to create the contract record before the draft document is created and eNegotiate begins.
  • βœ… Contract Executed βœ…
    This is the Done phase of the workflow. It captures any updates made after the previous AutoAction and publishes them to your finalised contract records, as well as updating it to Live and Approved.

To configure this:

  1. Click a phase of the workflow where vendors are created/updated.
  2. From Actions, click Edit AutoAction Values for the enabled AutoAction.
  3. For any new fields, select the corresponding Take Value from Form checkbox.
  4. If required, select an optional backup value in case the field is left blank.
  5. Click Save.

SetContractAutoActionValues-gif-1

 

Enable Office for the Web

If you have a Microsoft business account and use Office for the Web (instead of the desktop version of Microsoft Word) to review and edit Word documents, you can embed this in your workflow to streamline the draft revision cycle:

  1. Click an internal phase (i.e. Draft Review πŸ“‘, Internal eNegotiate πŸ§‘β€πŸ’Ό, or Draft Finalisations β˜‘οΈ β˜‘οΈ β˜‘οΈ) where you want to enable OFTW.
  2. From Actions, select the Office for the web checkbox alongside the Submit Draft action. 

Note: As this feature requires users to log in to Gatekeeper and have Microsoft accounts, it should not be enabled for vendor users during draft review phases.

EnableOFTW-gif-1-1

 

Amend SLAs

Workflow SLA Timers are used to set deadlines, automate escalations (via conditional transitions), and identify bottlenecks.

These have already been set for certain phases of the workflow:

Phase Default SLA Timer Transition After Expiry
Review Rejection 7 Days ❌ Contract Rejected ❌ [Done]
Initial Review βœ… 7 Days -
Draft Review πŸ“‘ 7 Days -
Vendor eNegotiate πŸ‘· 8 Days Draft Finalisations β˜‘οΈ β˜‘οΈ β˜‘οΈ
Internal eNegotiate πŸ§‘β€πŸ’Ό 7 Days -
Draft Finalisations β˜‘οΈ β˜‘οΈ β˜‘οΈ 7 Days  -
Final Approvals βœ… 7 Days -
eSign ✍️ 7 Days -
External Signature ✍️ 7 Days -
To edit SLAs to match your organisation's timelines:
  1. Click the phase where you want to edit the SLA.
  2. From SLA, enter a value, then select the unit (hours or days) from the dropdown list.

SLA timer

 

Add Extra Phases

This template is designed to be succinct, with flexibility to expand within the pre-configured phases. For example, the single Final Approval phase can accommodate multiple reviews and approvals, depending on your team structure. However, you can also add steps to your workflow to support additional processes, such as:

  • Finance e.g Raise PO
    If your finance team uses Gatekeeper for information on new vendors or contracts, you can include them in the process so they are aware of agreements requiring payment and can confirm when payments are completed.
  • Additional Approval e.g. CEO Approval
    Although the template workflow can run multiple approvals in parallel through the Final Approvals phase, if you need a specific user or team to complete a standalone review, you can add a dedicated phase to the workflow. This can be configured with conditional transitions, e.g. If contract value is greater than Β£100,000, transition to CEO Approval.
  • Fast Track e.g. Fast Track Completed [Done]
    This workflow is primarily for contract requests that require setup, negotiation, approval, and signing in Gatekeeper. However, you may receive requests that do not follow this standard process, such as small, simple, or low-risk contracts that do not require approval, negotiation, or signing. Adding this phase would allow these forms to be completed with no further tasks after the Initial Approval phase.

To do this:

  1. Navigate to the right hand side of the workflow board.
  2. Next to New Phase, click ADD.
    Internal Contract Request - add new phase
  3. Enter a phase title and description if needed, then click Save & Next.
  4. Click  Reorder to move the phase to the appropriate point in your workflow.
  5. Complete the configuration for the phase depending on its purpose, and reconfigure transitions from other phases to ensure your new phase is included in the end-to-end form workflow.

See πŸ“– Add Phases to a Workflow for more guidance.

⚑️ Getting Started βš‘️

Once your workflow is fully configured, follow the guidance below to start using it:

If using the Employee Portal

Once your workflow is configured, users can initiate a new contract request via the Submit Requests dashboard. To share the form URL, right-click the Request button to copy the link. 

If using a Public Form

You will need to copy and distribute the form URL. To do this:

  1. Click the start phase of the workflow to edit it.
  2. From Form Access, copy the URL to share with users.
    Internal Contract Request - public url

Additional Reading πŸ“š