Automation Philosophy
Vendor management automation enables proactive governance rather than reactive firefighting. Automated contract expiry alerts prevent missed renewal deadlines. SLA breach notifications ensure accountability. Risk review scheduling maintains assessment currency.
- Proactive alerts - notify stakeholders before deadlines, not after
- Escalation paths - route to appropriate levels based on urgency
- Audit trail - document all automated actions for compliance
- Integration ready - connect with existing workflows and tools
Contract Expiry Automation
Contract lifecycle automation ensures timely renewal decisions and prevents costly auto-renewals or service gaps.
CE-01: Contract Expiry Early Warning (120 Days)
Notify contract owners and vendor managers when contracts enter the renewal planning window.
AQL Query:
objectType = "Contract" AND Status = "Active"
AND "End Date" >= now() AND "End Date" <= now(120d)
Email Template:
Escalation Schedule:
| Days to Expiry | Action |
|---|---|
| 120 days | Initial notification; Status = "Expiring Soon" |
| 90 days | Reminder to Contract Owner |
| 60 days | Escalate to Vendor Manager |
| 45 days | Escalate to Contract Manager |
| 30 days | Escalate to CPO |
| Notice Period | Final warning; risk of auto-renewal or gap |
CE-02: Auto-Renewal Alert
Flag contracts with auto-renewal clauses requiring proactive non-renewal notice if not renewing.
AQL Query:
objectType = "Contract" AND Status = "Active" AND "Auto-Renew" = "Yes"
AND "End Date" >= now() AND "End Date" <= now(90d)
Email Template:
CE-03: Contract Expiration Processing
Update contract status when contracts reach their end date without renewal.
AQL Query:
objectType = "Contract" AND Status IN ("Active", "Expiring Soon") AND "End Date" < now()
Actions:
- Update Status to "Expired"
- Query related SLAs and update Status to "Expired"
- Send expiration notification
- Create post-expiration review task
SLA Breach Automation
SLA automation ensures vendor performance accountability and enables timely credit claims.
SB-01: SLA Performance Due Reminder
Remind service delivery teams to record SLA performance data at the end of each measurement period.
AQL Query (Monthly SLAs):
objectType = "SLA" AND Status = "Active" AND "Measurement Period" = "Monthly"
Logic:
Run on first 5 business days of each month. Check if SLA Performance exists for previous month. If missing, send reminder.
Email Template:
SB-02: SLA Breach Notification
Alert stakeholders when SLA targets are missed to enable credit claims and vendor accountability.
Trigger:
Object created (SLA Performance object type) with condition: Target Met = "No"
Email Template:
SB-03: SLA Breach Trending Alert
Identify vendors with repeated SLA breaches indicating systemic issues.
AQL Query:
objectType = "SLA Performance" AND "Target Met" = "No" AND Created > now(-90d)
Logic:
- Group breaches by Vendor
- Count breaches per vendor
- Alert if vendor has 3+ breaches in 90 days
Actions:
- Schedule vendor performance review meeting
- Request formal root cause analysis
- Add to Vendor Governance Committee agenda
Risk Assessment Automation
Risk assessment automation ensures vendor risk reviews remain current and findings are tracked to resolution.
RA-01: Risk Assessment Due Scheduling
Schedule and notify TPRM analysts when vendor risk assessments are approaching their review date.
AQL Query:
objectType = "Risk Assessment" AND Status = "Approved"
AND "Next Review Date" >= now() AND "Next Review Date" <= now(30d)
AND Vendor.Status = "Active"
Assessment Frequency by Risk Level:
| Risk Level | Review Frequency | Notification Lead Time |
|---|---|---|
| Critical | 6 months | 45 days |
| High | Annual | 30 days |
| Medium | 18 months | 30 days |
| Low/Minimal | 24 months | 30 days |
RA-02: Risk Assessment Overdue Escalation
Escalate when risk assessments become overdue, indicating compliance gap.
AQL Query:
objectType = "Risk Assessment" AND Status = "Approved"
AND "Next Review Date" < now()
AND Vendor.Status = "Active"
Escalation Matrix:
| Days Overdue | Escalation Action |
|---|---|
| 1-14 days | Remind TPRM Analyst |
| 15-30 days | Notify TPRM Manager |
| 31-60 days | Notify CPO; block new engagements |
| 60+ days | Vendor Governance Committee escalation |
RA-03: Risk Factor Mitigation Tracking
Track open risk factors and ensure mitigations are completed on time.
AQL Query:
objectType = "Risk Factor" AND Status = "Open"
AND "Target Mitigation Date" <= now(14d)
Escalation for Past-Due Mitigations:
- 7 days past due: Notify TPRM Manager
- 14 days past due: Escalate to Business Owner
- 30 days past due: Vendor Governance Committee review
RA-04: New Vendor Risk Assessment Trigger
Automatically initiate risk assessment workflow when new vendors are registered.
Trigger:
Object created (Vendor object type) with condition: Status = "Under Review"
Assessment Tier Logic:
| Tier | Criteria | Assessment Type |
|---|---|---|
| Tier 1 | Strategic Importance IN (Critical, High) OR Spend > $250,000 | Comprehensive |
| Tier 2 | Strategic Importance = Medium OR Spend $50,000-$250,000 | Standard |
| Tier 3 | Strategic Importance = Low OR Spend < $50,000 | Streamlined |
Performance Review Automation
Performance review automation ensures systematic vendor evaluation and stakeholder input.
PR-01: Quarterly Performance Review Scheduling
Schedule quarterly performance reviews for Critical and High importance vendors.
AQL Query:
objectType = "Vendor" AND Status = "Active"
AND "Strategic Importance" IN ("Critical", "High")
Email Template:
PR-02: Stakeholder Feedback Collection
Gather performance feedback from multiple stakeholders before finalizing vendor reviews.
Trigger:
Object created (Performance Review) with Status = "Draft"
Stakeholders to Survey:
- Contract Owner
- Business Owner
- Technical Lead (from Product/Service records)
- Recent Issue reporters
Feedback Dimensions:
- Quality Score (1-5): Quality of products/services
- Responsiveness Score (1-5): Response to requests and issues
- Value Score (1-5): Value delivered vs. cost
PR-03: Poor Performance Escalation
Escalate when vendors receive poor performance ratings requiring intervention.
Trigger:
Object updated (Performance Review) with Status = "Final" AND Overall Score IN ("Needs Improvement", "Unacceptable")
Actions by Score:
| Score | Required Actions |
|---|---|
| Needs Improvement | Schedule vendor discussion within 2 weeks; Develop improvement plan; Increase monitoring; Follow-up in 90 days |
| Unacceptable | Emergency meeting within 5 days; Formal corrective action; Evaluate alternatives; Assess termination; Executive notification |
Spend Management Automation
Spend automation enables budget monitoring and cost optimization visibility.
SM-01: Budget Variance Alert
Alert when vendor spend exceeds budgeted amounts or contract values.
Logic:
- For each Active vendor: Sum Spend records for current year
- Compare to Contract Total Value (annualized)
- Calculate variance and alert based on threshold
Variance Thresholds:
| Over Budget By | Alert Level |
|---|---|
| > 10% | Warning |
| > 20% | Alert |
| > 50% | Critical |
SM-02: Spend Categorization Reminder
Ensure spend records are properly categorized for accurate reporting.
AQL Query:
objectType = "Spend" AND Category is EMPTY AND Created > now(-14d)
Available Categories:
Software, Hardware, Services, Support, Training, Other
SM-03: Annual Spend Summary
Generate annual vendor spend summary for planning and consolidation analysis.
Report Contents:
- Total Vendor Spend and Year-over-Year Change
- Top 10 Vendors by Spend
- Spend by Category breakdown
- Consolidation opportunities (multiple vendors in same category)
- Recommendations for contract optimization
Issue Management Automation
Issue automation ensures vendor problems are tracked, escalated, and included in performance assessments.
IM-01: Critical Issue Escalation
Immediately escalate critical vendor issues to appropriate stakeholders.
Trigger:
Object created (Issue object type) with condition: Priority = "Critical"
Notification Recipients:
- Vendor Manager
- Contract Owner
- Business Owner
- If Security Incident: CISO
Immediate Actions:
- Contact vendor via emergency escalation path
- Document all communications
- Assess business continuity impact
- Activate workarounds if available
- Update status every 2 hours until resolved
IM-02: Issue Resolution SLA Tracking
Monitor issue resolution times and escalate when targets are exceeded.
AQL Query:
objectType = "Issue" AND Status IN ("Open", "In Progress")
Expected Resolution by Priority:
| Priority | Expected Resolution |
|---|---|
| Critical | 4 hours |
| High | 24 hours |
| Medium | 72 hours |
| Low | 5 business days |
Vendor Lifecycle Automation
Vendor lifecycle automation ensures systematic onboarding, monitoring, and offboarding.
VL-01: New Vendor Onboarding Checklist
Create and track onboarding checklist when new vendors are approved.
Trigger:
Object updated (Vendor) with Status changed from "Under Review" to "Active"
Onboarding Checklist:
- Risk Assessment approved and documented
- Contract executed and registered
- Primary and backup contacts recorded
- Products/Services registered
- SLAs documented (if applicable)
- Monitoring configured
- Initial spend forecast entered
- Business owner assigned
- Stakeholders notified
- First performance review scheduled
VL-02: Inactive Vendor Identification
Identify vendors with no recent activity for potential cleanup or re-engagement.
AQL Query:
objectType = "Vendor" AND Status = "Active"
Activity Checks (12 months):
- Any Spend records
- Any Issues logged
- Any active Contracts
- Any SLA Performance records
Actions:
- Vendor relationship ended - update Status to Inactive
- Vendor relationship continues - update records
- Vendor relationship paused - document reason and review date
VL-03: Vendor Offboarding Trigger
Initiate offboarding workflow when vendor is marked for deactivation.
Trigger:
Object updated (Vendor) with Status changed to "Inactive" OR "Blocked"
Offboarding Checklist:
- Terminate or expire all contracts
- Retire all products/services
- Resolve or transfer open issues
- Process final invoices
- Revoke vendor system access
- Retrieve company data from vendor
- Archive vendor documentation
- Update contacts to Inactive
Automation Schedule Summary
Daily Automations
| Automation | Time | Priority |
|---|---|---|
| Contract Expiry Early Warning | 07:00 | Critical |
| Contract Expiration Processing | 00:01 | High |
| SLA Performance Due Reminder | 08:00 | Medium |
| Risk Assessment Overdue Escalation | 09:00 | Critical |
| Issue Resolution SLA Tracking | Every 4 hours | Medium |
Weekly Automations
| Automation | Day/Time | Priority |
|---|---|---|
| Auto-Renewal Alert | Monday 08:00 | Critical |
| Risk Assessment Due Scheduling | Monday 09:00 | High |
| Risk Factor Mitigation Tracking | Wednesday 10:00 | High |
| Spend Categorization Reminder | Friday 14:00 | Low |
| SLA Breach Trending Alert | Friday 16:00 | High |
Real-Time Automations
| Automation | Trigger | Priority |
|---|---|---|
| SLA Breach Notification | SLA Performance created with Target Met = No | Critical |
| New Vendor Risk Assessment | Vendor created with Status = Under Review | High |
| Stakeholder Feedback Collection | Performance Review created with Status = Draft | Medium |
| Poor Performance Escalation | Performance Review updated to Final + Poor Score | Critical |
| Critical Issue Escalation | Issue created with Priority = Critical | Critical |
| New Vendor Onboarding | Vendor Status changed to Active | High |
| Vendor Offboarding | Vendor Status changed to Inactive/Blocked | High |
Troubleshooting
Contract Automation Issues
| Issue | Root Cause | Solution |
|---|---|---|
| Contracts not triggering expiry notifications | End Date format or Status filter | Ensure End Date is Date field (not Text); Verify Status = "Active" |
| Auto-renewal alerts missing contracts | Auto-Renew or Notice Period not populated | Require Auto-Renew field during contract creation |
SLA Automation Issues
| Issue | Root Cause | Solution |
|---|---|---|
| SLA breach notifications not sending | Target Met field value mismatch | Ensure "Target Met" = "No" (exact match, case-sensitive) |
| Duplicate breach notifications | Multiple automation rules | Consolidate into single rule; Add notification sent check |
Risk Assessment Issues
| Issue | Root Cause | Solution |
|---|---|---|
| Assessment reminders not matching frequency | Next Review Date not calculated | Verify date is set during assessment approval |
| Wrong assessments appearing | Vendor Status filter missing | Include only Active vendors in query |
FAQ
Q1: How do I handle contract renewals that span multiple years?
For multi-year renewals: Update End Date to new expiration date, update Total Value to reflect new term total, create amendment documentation, verify SLA records continue, and refresh risk assessment for extended term. Automation will recalculate notification dates based on new End Date.
Q2: Can automations update vendor status based on risk assessment results?
Yes, but implement with caution. Recommend notification and task creation rather than automatic status change. Human decision required for blocking vendors due to business impact. Automatic updates are acceptable for non-blocking changes like updating review schedule.
Q3: How do I handle vendors with multiple contracts having different SLAs?
The schema supports multiple SLAs per vendor. Each Contract can have multiple SLA objects, SLA Performance records link to specific SLAs, breach notifications identify specific SLA and Contract, and performance reviews aggregate across all vendor SLAs.
Q4: How do I prevent notification fatigue from too many alerts?
Implement notification management: Consolidate into weekly digests instead of individual notifications, alert only above significance thresholds, route to appropriate roles only, start with owner and escalate only if needed, and allow suppression of acknowledged items.
Q5: Can automation calculate SLA penalties automatically?
Partial automation is possible. Store penalty formula in SLA.Penalty (text description). For simple formulas (X% per Y%), automation can calculate. Complex formulas may require external calculation. Recommend calculating estimated credit with human verification before claiming.
Schema Forge