> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/supplier-and-product-management/contractor-application/navigating-the-contractor-management-workflow.md). # Navigating the Contractor Workflow Perform the tasks assigned to your role to advance requests through the Contractor Management workflow. ### Workflow Overview The **Contractor** application operates through a single, standardized workflow: the **Contractor Management** workflow. This workflow governs the full lifecycle of a contractor request, from creation through final approval.
*** ### Workflow Stages The workflow is organized into **five key stages**, each with specific roles and responsibilities. {% hint style="success" %} For detailed instructions on any stage, click the corresponding button. {% endhint %} {% stepper %} {% step %} ### Create New Contractor Request > **Performed By:** Request Creator (e.g., Project Manager, Department Lead, Procurement Officer, Contractor) **Responsibilities**: * Identify the need for a contractor. * Provide the necessary details, including: * Legal and business information * Primary contact details * Scope of goods or services * Supporting documentation * Complete the assessment questionnaire, if applicable. * Submit the request to initiate the workflow.

Create a New Contractor Request

*** {% endstep %} {% step %} ### Prequalify / Screen Contractor > **Performed By:** Assigned Reviewer (e.g., Compliance Officer, Procurement Specialist, Risk Manager) **Responsibilities**: * Confirm that the contractor meets baseline eligibility and compliance requirements: * Business registration and legal status * Regulatory certifications and trade licenses * Insurance coverage and financial stability * Review section and total scores against organizational thresholds. * Add comments or flag discrepancies requiring follow-up. * Reject the contractor if they fail to meet minimum criteria, or submit the request for further evaluation.

Prequalify / Screen Contractor

*** {% endstep %} {% step %} ### Evaluate Contractor Response > **Performed By:** Assigned Evaluator (e.g., Subject Matter Expert, Technical Lead, Project Evaluator) **Responsibilities**: * Assess contractor qualifications, capabilities, and alignment with organizational standards. * Review questionnaire responses for completeness, accuracy, and relevance. * Score responses using the defined scale: **Very Low → Fully**. * Verify weighted scores and overall totals. * Record notes and provide rationale for each score. * Assign an approver and submit the evaluation for final review.

Evaluate Contractor Response

*** {% endstep %} {% step %} ### Conduct Final Contractor Review > **Performed By:** Assigned Approver (e.g., Department Manager, Procurement Manager, Executive Sponsor) **Responsibilities**: * Ensure contractor scores meet or exceed minimum thresholds. * Review comments and any flagged issues. * Confirm alignment of scoring with organizational standards. * Take appropriate action: * Approve the request to register the contractor. * Reject the request if criteria are not met. * Return the request to the evaluator for modification if revisions are needed.

Conduct Final Contractor Review

*** {% endstep %} {% step %} ### Modify Contractor Evaluation > **Performed By:** Assigned Evaluator (e.g., Subject Matter Expert, Technical Lead, Project Evaluator) **Responsibilities**: * Review feedback from the approver. * Make necessary revisions to the evaluation and scoring. * Resubmit the request for final review.

Modify Contractor Evaluation

{% hint style="warning" %} This stage is triggered only if the request is returned for modification after the final review. {% endhint %} *** {% endstep %} {% endstepper %} *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://interfacing.gitbook.io/interfacing-help-files/supplier-and-product-management/contractor-application/navigating-the-contractor-management-workflow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.