The First 90 Days After Switching COI Tools: What Actually Changes

TL;DR: In the first 90 days after switching COI tools, expect Week 1 configuration and data mess, Week 2 migration of active subs only (not historical), Weeks 3-6 document collection and pushback from subs, and Days 60-90 retirement of the old spreadsheet. Keep the old system running in parallel until every active sub on every live project has a complete record and a named compliance owner is handling exceptions daily.

The decision to switch subcontractor compliance tools is one thing. Actually experiencing the switch is another. If you're considering a move from a spreadsheet, a legacy COI tracking platform, or an enterprise tool that isn't serving your needs, this post walks through what the first 90 days realistically looks like so you know what to expect and where to focus.

Week 1: Setup and Initial Panic

In the first week after signing up for a new tool, two things happen simultaneously: you start learning the new system, and you realize how messy your existing data is.

What you'll feel

• Mild overwhelm: even simple systems have configuration choices you didn't anticipate
• Awareness of data quality issues: old spreadsheets surface duplicate entries, outdated emails, and missing files
• Uncertainty about what to migrate: should you bring old records forward, or start fresh?

What to do

• Keep the old system running in parallel. Don't retire it until the new system is fully populated and tested.
• Focus the first week on configuration and training, not data migration.
• Define what "done" looks like for migration. Usually: every active sub on every active project has a complete record in the new system.

Week 2: Active Sub Migration

In the second week, start moving active subs into the new system. The key word is "active."

What to migrate

• Every sub currently working on a live project
• Every sub with a contract signed but not yet started
• Every sub you expect to rehire within the next 60 days

What not to migrate (yet)

• Historical subs you haven't worked with in a year
• Subs from completed projects where the statute of limitations has passed
• One-time vendors from years ago

A clean cutoff focuses the migration on what matters. You can always add historical subs later if a claim surfaces.

What you'll feel

• Progress visible for the first time: seeing active subs populate the new dashboard feels like momentum
• Some frustration with data entry: if the new tool requires manual re-entry, this part is tedious
• Discovery of compliance gaps: subs whose documentation is stale or missing become visible in the new system

Week 3 to 4: Document Requests

By the end of the first month, you should have every active sub in the system. Now start collecting current documentation for any sub whose records are incomplete.

The process

• Send document requests through the new tool's upload workflow
• Give subs a 7 to 14 day window to respond
• Escalate non-responders to the PM or ops leadership
• Work through exceptions with documented decisions

What you'll feel

• Gratitude for automated reminders: the system handles follow-up so you don't have to manually chase every sub
• Some pushback from subs: some subs will resist the new upload workflow initially. Most adapt within a week.

What to do

• Frame the change positively with subs: "our new compliance system is faster and more secure. Here's a link to upload your current COI."
• Escalate quickly on non-responders. The first exception sets the tone.

Day 30 Checkpoint

By day 30, you should be able to answer these questions:

1. Is every active sub in the new system?
2. What percentage of active subs have complete compliance documentation?
3. What exceptions are open, and when will they resolve?
4. Who on the team is responsible for the new workflow?
5. Is the team using the new system for new subs going forward?

If the answer to any of these is unclear, you're behind schedule but still on a recoverable path.

Month 2: Building the Rhythm

The second month is about making the new system routine.

Week 5 to 6: Weekly Compliance Reviews

Establish a 15-minute weekly meeting where the compliance owner walks through the dashboard with ops leadership. Review:

• Expiring documents in the next 60 days
• Open exceptions
• Any new subs added this week
• Any compliance incidents or concerns

This meeting doesn't need to be formal. It just needs to happen consistently.

Week 7 to 8: Retiring the Old System

By week 7 or 8, the new system should be the only source of truth. Archive the old spreadsheet. Stop maintaining it. If a project manager still sends COIs via email to be manually filed, redirect them to use the new workflow.

What you'll feel

• Momentum: the new workflow starts feeling natural
• Visibility: you know where every sub stands on every project
• Relief: catching an expiring document 60 days out instead of after the fact

Day 60 Checkpoint

By day 60, the new system should be fully operational. Questions to ask:

1. Is the old system archived and no longer being updated?
2. Are all new subs flowing through the new workflow without PM intervention?
3. Are weekly compliance reviews happening?
4. Have you caught at least one expiration through the automated alerts that would have slipped past you before?
5. Is leadership visible on the compliance status?

Month 3: Optimization

The third month is where habits solidify and small improvements compound.

Week 9 to 10: Process Refinement

Now that the workflow is routine, refine it:

• Are there required document types you didn't configure initially but should have?
• Are there exception categories you see repeatedly? Build a standard decision path.
• Are there subs consistently missing the same items? Update the onboarding template.

Week 11 to 12: Reporting and Insights

Start pulling reports to understand your compliance patterns:

• Which sub categories have the most gaps?
• Which project managers have the best compliance discipline?
• Which exceptions take longest to resolve?
• What's the average time from document request to upload?

Use the data to make small improvements.

Day 90 Checkpoint

By day 90, the transition is complete. Questions to ask:

1. Is compliance running in the background without requiring active management?
2. Would switching back to the old system feel like a step backward?
3. Have you caught compliance issues that would have been missed before?
4. Is the team using the new tool naturally?

If yes to all four, the transition is successful.

Common Problems in the First 90 Days

Problem: The Old System Stays Alive

The old spreadsheet keeps getting updated "just in case." Result: two systems of truth, and the new tool loses credibility.

Fix: formally archive the old system at day 60. No more updates.

Problem: Leadership Stops Paying Attention

After the initial excitement, leadership stops asking about compliance. Without visibility, the discipline fades.

Fix: include compliance status in regular ops meetings. Keep it on the leadership radar.

Problem: PM Bypass

Project managers still collect COIs directly via email and forget to upload them to the new system.

Fix: require the upload as a condition of PO issuance. No compliance, no PO.

Problem: Data Quality Issues From Migration

Incorrect sub names, duplicate entries, missing fields carried over from the old system create ongoing friction.

Fix: run a cleanup pass in month 2, catching and correcting migration errors systematically.

How PaperBoss Supports the Transition

PaperBoss is designed for self-serve transitions. The sign-up flow, CSV import, and document request workflow are all built to work without a customer success manager walking you through them. For GCs switching from a spreadsheet or a legacy tool, the whole 90-day transition is realistic because the tool doesn't require an army of implementers.

If you get stuck during the transition, email support and a real person responds. No sales calls required.

Start a 14-day free trial, no credit card required.

Frequently Asked Questions

How do I know if a switch is working before day 90?

Check the leading indicators: percentage of active subs in the new system, percentage compliant, response time for document requests, and whether leadership is using the dashboard.

What if I'm switching from an enterprise tool to save money?

The transition is similar but may involve untangling integrations and contract exit terms. Give yourself 30 to 60 extra days for administrative work with the outgoing vendor.

Can I keep using both systems in parallel?

For up to 60 days during transition, yes. After that, running parallel systems creates data drift and conflict. Commit to one system.

What happens to historical records in the old system?

Export them to CSV or PDF archives. Retain per your retention policy. Don't lose them just because you switched tools.

Is it worth switching mid-project?

Yes. Don't wait for an arbitrary milestone. The longer you delay, the more legacy mess you bring forward.

---

This article is for educational purposes only. Transition timelines vary by organization size and data complexity.