These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Subcontractor Management
- Features
- Documents and Qualifications
Documents and Qualifications
Keep required submissions, insurance and license evidence connected to each subcontractor's qualification review.
OverviewDocument Review×
Subcontractor Management · Documents and Qualifications
New
Document Review
Approval conditions
| Subcontractor | Requirement | Submitted at | Effective date | Expiration date | Status | |
|---|---|---|---|---|---|---|
| SBC-1780 | DR-8958 | 20 Oct | 29 Oct | 04 Nov | Submitted | |
| SBC-7131 | DR-3099 | 27 Oct | 29 Oct | 07 Nov | Submitted | |
| SBC-6461 | DR-5044 | 12 Oct | 16 Oct | 22 Oct | Submitted | |
| SBC-2622 | DR-8984 | 18 Oct | 20 Oct | 26 Oct | Submitted | |
| SBC-8794 | DR-9714 | 03 Oct | 12 Oct | 16 Oct | Submitted |
6 of 6 records
SBC-1780Document submissions · DS-22936
SubmittedRequirementDR-8958
Submitted at20 Oct
Effective date29 Oct
Expiration date04 Nov
What you can do
Know which evidence needs attention
Compliance Officer defines the document requirements that support a subcontractor’s qualification. A requirement can apply across the vendor list or depend on a trade, state or named company. Its frequency and grace period give procurement a clear basis for follow-up. The related submission carries the file and review dates needed to decide whether the evidence is current.
Insurance certificates and licenses have their own records. A certificate retains its carrier, coverage type, amount and expiry. A license records its issuing authority, state and permitted scope. Procurement Manager can review these alongside the company before choosing it for project work or considering reinstatement after suspension.
How the work is organized
- Requirements and requests. Creating a requirement starts requests for matching subcontractors. Each submission links the company to the requirement, so an approved document can be checked against the obligation it fulfills.
- Review and expiry. Submissions move from Requested to Submitted and then to Approved or Rejected. Effective and expiration dates support renewal review. A rejection reason tells the submitter what must change before another review.
- Qualification records. Insurance distinguishes Pending review, Valid, Expired and Cancelled. Licenses distinguish Valid, Expired, Suspended and Revoked. Preserve those meanings when discussing a vendor’s eligibility with the project team.
What to agree during setup
Compliance Officer and Procurement Manager agree the applicable document set for each trade and project location. Decide which insurance coverage needs review and who verifies additional-insured wording. Record the source of a license verification and update the last verification date after the check.
Set the expiry follow-up cadence and confirm who receives each request. Connect the team’s email delivery service during setup. For W-9 review, agree how stored company information is checked and how a mismatch is resolved. External identity validation requires its own connection and operating procedure.
Check the handoff on an actual case
A roofing subcontractor has a replacement liability certificate ready, but its required license submission has expired. The replacement certificate is reviewed with its effective date and coverage amount. Procurement Manager still needs the license renewal before approving the company’s return to Active.
Use that case to rehearse the renewal decision. Approving a document for a suspended company starts a check of every applicable active required document. When the required evidence is current, the review routes clearance to Procurement Manager for the reinstatement decision. Keep the vendor under review while another required submission is expired or rejected.
Repeat the exercise with a document attached to the wrong company. The reviewer should identify the mismatch before approval and record a useful rejection reason. The follow-up should tell the sender which company and requirement need a corrected file, so the next submission can be assessed without guessing.
What your team sees
- Document Review — Submitted documents show the company, requirement and dates needed for review.
- Insurance Review — Certificates awaiting review or renewal stay visible with their coverage and expiry details.
- Active Subcontractors — Procurement can check qualification decisions alongside the company’s W-9 and TIN review status.
Follow the work through
Rehearse intake and qualification before starting payment review.
What it keeps track of
Data model- Document requirements
- The compliance catalog - what document types each subcontractor must keep on file.
- Document submissions
- Uploaded documents fulfilling a document requirement for a subcontractor.
- Insurance certificates
- Certificates of Insurance on file per subcontractor.
- Licenses
- State-issued contractor licenses held by a subcontractor.
- Subcontractors
- Vendor master - one row per outside-labor company on the qualified-vendor list.
- Users
- Users
Who uses it
Permissions- Compliance Officer
- Owns the qualification policy.
- Procurement Manager
- Coordinates vendor follow-up and makes the reinstatement decision.
- Subcontractor User
- Provides documents for the company.
Set up Subcontractor Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.