Track Employee and Subcontractor Documents in Sidecar

This pattern is useful when a document list needs one more piece of context:

Whose document is this?

Sidecar uses tracked parties to identify the employee, subcontractor, company, crew, or other subject that a document or requested item belongs to.

You can combine tracked parties with a simple internal expiration program, customer-specific document packages, or request and follow-up workflows. Tracked parties add ownership context; they do not create a separate subcontractor-management or employee-compliance system.

This is one of Sidecar’s Common Setup Patterns.

When this setup makes sense

Use this pattern when your team tracks records such as:

• employee licenses or certifications
• First Aid, CPR, OSHA, operator, or trade cards
• subcontractor COIs and W-9s
• vendor licenses
• company registrations
• crew training rosters
• equipment or inspection records associated with a managed crew or company
• customer-requested documents that belong to a specific person or subcontractor

Without tracked-party context, a list can show that a COI is missing while hiding the operationally important detail: missing for whom?

Customer, contact, and tracked party are different

These three records answer different questions.

A customer answers:

Which outside organization or internal program is this work grouped under?

A contact answers:

Who should receive communication?

A tracked party answers:

Whose document or requested item is being managed?

For example:

Role	Example
Customer	Red Mesa Utilities
Contact	Morgan Hill — insurance coordinator
Tracked party	Apex Trenching LLC — subcontractor
Document	Apex Trenching General Liability COI

The same real person or company can appear in more than one role, but the records still serve different workflow purposes.

1. Choose the customer structure

There are two common ways to group tracked-party documents.

Internal document program

Create one internal customer for your organization when you are primarily tracking employee, subcontractor, company, crew, or vendor records for your own review.

Examples:

• Summit Field Services — Internal Documents
• Employee and Subcontractor Records
• Internal Credential Tracking

This works well with Simple Document Expiration Tracking.

Customer-specific package

Create the actual outside customer when the document exists because that customer requires it.

For example, the same subcontractor may need a COI tracked in the context of Red Mesa Utilities and a different requested item or submission state for Chevron.

Do not combine unrelated customer-specific packages under one internal record merely because the tracked party is the same. Customer requirements, contacts, portals, submissions, and acceptance states may differ.

2. Create tracked parties

Owners and admins can manage tracked parties from Settings.

Use a clear name and the most useful available type, such as:

• Internal Company
• Company
• Subcontractor
• Employee
• Other

Use Other for a crew, equipment group, or managed subject that does not fit the more specific types.

Avoid duplicate names that differ only by punctuation or abbreviation. A list containing Apex Trenching, Apex Trenching LLC, and Apex Trenching, L.L.C. may accurately reflect spreadsheet history while still making the current workspace unnecessarily exciting.

3. Assign the document to the tracked party

When adding or editing a document, use Belongs to to select the tracked party.

Leave the document assigned to Workspace / primary company when it belongs to your own organization rather than a separate managed party.

Examples:

Document	Customer	Belongs to
Company business license	Internal Documents	Workspace / primary company
First Aid / CPR card	Internal Documents	Jordan Lee — Employee
General Liability COI	Internal Documents or outside customer	Apex Trenching LLC — Subcontractor
Crew training roster	Internal Documents	North Yard Crane Crew — Other
Vendor license	Outside customer package	Reyes Electrical Services — Company

The tracked party appears as subject context on the document and in connected customer workflow views.

4. Use tracked parties on requested items when needed

A customer may request an item for a specific employee, subcontractor, crew, or company.

Add the tracked party to the requested item so Customer Detail can show both:

• what the customer expects
• whose record is involved

For example:

• Requested item: Provide current OSHA 10 card
• Customer: Red Mesa Utilities
• Tracked party: Jordan Lee — Employee
• Linked document: Jordan Lee OSHA 10 Card

The requested item can remain Missing or Submitted while the document has its own status and expiration date. Those records describe related but different states.

5. Track dates only when the record has a real date

Use effective and expiration dates when they support the real review process.

Do not invent dates for records that do not expire. W-9s and some company or policy records may remain useful without an expiration date.

For dated credentials, review the workspace expiration attention window and use Reports for the next 30, 60, and 90 days. The current attention window applies across the workspace; Sidecar does not assign a separate warning window to every tracked-party or document category.

6. Add requests and waiting states when someone owes the next move

Tracked-party context becomes especially useful during document chasing.

For example:

• Customer: Red Mesa Utilities
• Requested item: Revised COI
• Tracked party: Apex Trenching LLC
• Contact: Apex’s broker
• Waiting on: Broker
• Follow-up: August 12

The tracked party shows whose record is affected. The contact shows who receives the message. Waiting On shows who has the next move.

See Document Requests and Follow-Ups when the workflow grows beyond dates and ownership.

7. Review the right level of context

Use:

• Documents for the complete record list and current document state
• Customer Detail for the customer package and its tracked-party context
• Today for customer-level attention when dates, missing work, waiting, or tasks become important
• Reports for expiration review and customer package status
• Waiting On when a response or replacement depends on someone else

Tracked parties improve context inside these workflows. They are not currently a full employee directory, subcontractor qualification engine, or project-readiness system.

Importing tracked parties

A spreadsheet can identify tracked parties on their own worksheet or through document and requested-item columns such as subject, document owner, subcontractor, employee, company, crew, or related names.

During import preview, Sidecar distinguishes tracked parties that match existing tenant records from those proposed for creation. Blank subject information continues to mean Workspace / primary company.

Review names and types carefully before approval so inconsistent spreadsheet labels do not create duplicates.

See Importing Data for the reviewed import process.

What this pattern does not determine

Sidecar can show whose document is missing, current, expiring, expired, submitted, or waiting according to the state your team records.

It does not determine whether an employee is legally qualified, whether a subcontractor is approved, whether a credential satisfies a regulation, whether insurance coverage is adequate, or whether a customer will accept the record.

Tracked parties provide operational context and traceability. The responsible people and customer systems still perform the actual review.

Next steps

Return to Common Setup Patterns to compare smaller workflows. Use Simple Document Expiration Tracking for an internal date-focused program, or Customer Document Package Checklist when tracked-party documents belong to specific customer requirements.