Docoply pilot intake

Contractor Engagement Route Assistant

Capture the request before contract drafting, identify the likely engagement route, and create an evidence checklist for reviewer sign-off.

1. RequestDescribe the business need and proposed route.
2. RouteDocoply applies the route rules and flags conflicts.
3. EvidenceThe case gets a route-specific evidence checklist.
4. ReviewA reviewer confirms, changes, or asks for clarification.

Before you start: company, department, requestor name, requestor email, business need, and need type are required. Placeholder answers such as “N/A”, “test”, “TBD”, or very short descriptions are rejected because they do not create a reliable route record. Enter the reviewer name and reviewer email so the case goes directly to that reviewer’s Docoply panel.

Step 1

Request details

Record who is asking and the business reason for the work. These identity fields are required so the case can be reviewed and evidenced properly.

Reviewer routing

Reviewer information

Enter the reviewer who should receive this case. The reviewer email must match an active Docoply reviewer account so the request is sent directly to that reviewer’s panel.

Optional, but helpful for pilots with several companies.
Use the reviewer email connected to their Docoply Intake access. That email sends the case to their Docoply panel.
This should be the plain-English request before route, contract, or supplier decisions are fixed.
Step 2

Engagement facts

Answer the working-practices questions as they are expected to operate in reality, not just as they may be written in a contract.

Step 3

Constraints and approvals

Add context that may affect review, evidence collection, or handoff to HR, procurement, legal, or IR35/SDS review.