Phase 2: The Contractor Management System That Actually Learns
What happens when you let Phase 1 teach you what to automate
Hey everyone,
Three months ago, I told you about Phase 1 of our contractor management system.
The one that gave managers training wheels. Automated alerts. Hand-holding from HR when things went wrong.
Results? Manager compliance went from 40% to 78%.
But here’s what I didn’t tell you: Phase 1 was always the learning phase.
We built it to teach us what Phase 2 should actually look like.
And Phase 2 just went live.
What We Learned From Phase 1
After 18 test cases, hundreds of notifications, and countless manager interactions, here’s what the data told us:
Pattern #1: Managers Need Earlier Warnings
The 14-day notification? Not enough for some.
So Phase 2 adds:
2-week notification (action required)
3-day notification (urgent reminder)
Day-of notification (final warning)
Not because managers are forgetful. Because they’re busy.
And our job is to make compliance effortless, not add to their cognitive load.
Pattern #2: The 90-Day Rule Works
We set a hard limit: managers can extend contracts up to 90 days without approval.
Beyond that? Manager sees Error message.
Result? 85% of extensions stayed within the 90-day window.
The validation isn’t punishing managers. It’s protecting the company.
Pattern #3: Auto-Termination Needed Clear Messaging
Phase 1 reassigned incomplete tasks to HR.
Phase 2? If managers don’t act by the contract end date, the system auto-terminates the contract at midnight.
Reason: “Involuntary - Contract Expired”
Worker: Disabled
Access: Revoked
It sounds harsh. But here’s why it works:
The message is crystal clear from day one.
When HR hires a contractor, they see: “Please note that you need to add contract end date.”
When managers get the 2-week alert: “If no action is taken, the worker(s) will be automatically terminated on the contract end date.”
No surprises. No gray areas. Just clarity.
The Phase 2 Build (What Actually Changed)
Let me walk you through what we built:
Change #1: Three-Tier Alert System
Alert 1 - Two Weeks Prior:
Who gets it: Manager only (not manager’s manager)
What it says: “Action Required - Worker Contract Ends in 2 Weeks”
What it includes: Link to Change Contingent Worker Details task
Alert 2 - Three Days Prior:
Who gets it: Manager
What it says:“Urgent: Action Required - Worker Contract Ends in 3 Days”
What it includes: “The contract for the worker(s) listed below ends in 3 days. Please review and take action if needed.”
Alert 3 - Day Of:
Who gets it: Manager
What it says:“Final Reminder: Worker Contract Ends Today”
What it includes: “The contract for the worker(s) listed below ends today. If the contract needs to be extended, click the link below to update the end date immediately.”
Warning: “If no action is taken, the worker(s) will be automatically terminated today, and their access disabled.”
Change #2: Smart Validations That Actually Enforce
Validation #1: Contract End Date is Mandatory
Try to hire a contractor without an end date?
Error: “No contract end date was added. Please populate.”
Validation #2: 90-Day Extension Limit (For Managers)
Manager tries to extend beyond 90 days?
Error: “You can only extend a contract up to 90 days at a time.”
But here’s the smart part: HR Ops can override this.
Because sometimes there are legitimate reasons for longer extensions. And we trust HR to handle those exceptions.
Validation #3: New End Date Required
Manager opens the Change Contingent Worker Details task but doesn’t update the end date?
Error: “The field Contract End Date is required and must have a value.”
Can’t submit. No workarounds.
Change #3: The Automated Integration
This is where it gets interesting.
Every night at midnight, a scheduled process runs:
Scans all active contingent workers
Identifies contracts ending that day
Checks if manager completed the renewal task
If not? Auto-terminates the contract
What happens on auto-termination:
Effective Date: Contract End Date
Reason: “Involuntary - Contract Expired”
Worker Status: Disabled
Access: Revoked
Position: Closed (if applicable)
Test case validation:
We tested this with multiple contractor scenarios.
All terminated cleanly. All on the correct date. All with the right reason code.
Zero manual intervention required.
Change #4: The Exception Handling
Not all contractors should auto-terminate.
Example: Certain specialized roles managed differently by specific teams.
How we handle it:
They still get alerts
They still require end dates
But they don’t auto-terminate
Only specific HR team members can process their contracts
Why? Because automation without exceptions is just rigid bureaucracy.
Smart automation recognizes that some situations need human judgment.
Change #5: No More Manager Approval on Terminations
Phase 1: Manager ends contract → Requires manager approval → Creates task
Phase 2: Manager ends contract → No approval required → Straight to offboarding
Also: The offboarding task no longer has a due date.
Why? Because when a contract ends, offboarding happens immediately. A due date implies flexibility that doesn’t exist.
The Testing That Proved It Works
We ran 18 test scenarios. All passed.
Here are the critical ones:
Test 1: Hire contractor with end date within 90 days → No warning message
Test 2: Hire contractor with end date beyond 90 days → Warning displays, but submission allowed
Test 3: 2-week notification goes to manager → Validated name, date format, link included
Test 6: Manager extends contract up to 90 days → No error
Test 7: Manager tries to extend beyond 90 days → Critical error blocks submission
Test 9: HR Ops extends beyond 90 days → Allowed (override capability)
Test 15: Auto-termination runs at midnight → Contract ended, worker disabled, reason = “Contract Expired”
Test 17: Specialized roles exempted from auto-termination → Confirmed
What This Actually Means for the Business
Before Phase 2:
Managers missed contract end dates
HR chased everyone manually
Contractors worked without valid contracts (compliance risk)
400+ hours per quarter spent on cleanup
After Phase 2:
Automated daily process handles terminations
Zero contractors work without valid contracts
Compliance risk eliminated
HR focuses on exceptions, not routine admin
The ROI:
Phase 1: 60% reduction in HR operational time
Phase 2: Additional 30% reduction (projected)
Total savings: ~1,040 hours per year
At a blended rate of $75/hour, that’s $78,000 annually.
And we didn’t buy new software. We just built smarter workflows.
The Lessons from Building This
Lesson #1: Phase 1 Data is Gold
We didn’t guess what Phase 2 should look like.
We let Phase 1 users teach us:
Which notifications actually got read
Where managers struggled
What errors happened most
Which validations were too strict (none) or too loose (some)
If we’d built “perfect” automation on day one, we would’ve built the wrong thing.
Lesson #2: Clarity Beats Flexibility
The auto-termination sounds harsh.
But every single notification tells managers exactly what will happen if they don’t act.
No ambiguity. No “maybe.” Just: “This will happen. Here’s how to prevent it.”
And guess what? Managers appreciate it.
Because clarity removes anxiety. Ambiguity creates it.
Lesson #3: Exceptions Prove the Rule
We excluded certain specialized roles from automation.
Not because the automation failed. Because their workflow genuinely requires different handling.
Smart systems recognize when the rule doesn’t apply.
Dumb systems enforce rules everywhere and call it “consistency.”
Lesson #4: Test Everything
18 test cases. Every validation. Every notification. Every edge case.
Positive testing (does it work when it should?).
Negative testing (does it fail when it should?).
We found issues:
Date format inconsistencies
Notification routing errors
Manager’s manager getting alerts (they shouldn’t)
And we fixed them before go-live.
That’s the difference between “it works in dev” and “it works in production.”
What’s Next (Phase 3?)
Honestly? We’re not sure there needs to be a Phase 3.
Phase 2 accomplishes what we set out to do:
Managers have visibility and control
Automation handles the routine
Exceptions get human attention
Compliance is enforced automatically
But here’s what we’re watching:
Manager compliance rate: If it drops below 70%, we’ll add more nudges
Auto-termination volume: If it’s high, managers need better training
HR override frequency: If HR is constantly overriding the 90-day rule, we may need to adjust it
User feedback: Are managers finding this helpful or annoying?
The data will tell us if Phase 3 is needed.
Most companies build automation in one shot.
“Here’s the system. Use it. Good luck.”
Then they wonder why adoption fails.
We did it differently:
Phase 1: Learn what works (with training wheels)
Phase 2: Automate what works (based on actual data)
Phase 3: Maybe? (if the data says we need it)
That’s not slower. It’s smarter.
Because you only get one chance to build trust with users.
If your “perfect” system fails on day one, you’ve lost them.
But if your “good enough” system works and improves over time? They’ll champion it.
The Bottom Line
Phase 2 is live.
Auto-terminations running nightly. Managers getting three levels of alerts. Validations enforcing the 90-day rule. HR handling exceptions.
And it’s working.
Not because we built perfect technology.
Because we built technology that respects humans.
Technology that’s clear, predictable, and fair.
Technology that automates the routine so humans can handle the exceptions.
That’s the formula.
Want to see the technical details? The full test results, configuration steps, and validation logic are available. Subscribe and reply to this email, I’ll send them over.
Building something similar? Let’s talk. I’m happy to share what worked (and what didn’t).
— Rohini Tirumalaraju
P.S. — Phase 1 saved 400 hours per quarter. Phase 2 is projected to save another 200. That’s 600 hours per quarter, or 2,400 hours per year. All without buying new software. Just by thinking through the process first, then automating second.