How to standardize team workflows with required fields and triggers

Documentation Index

Fetch the complete documentation index at: https://support.affinity.co/llms.txt

Use this file to discover all available pages before exploring further.

Last Updated: November 21, 2025 Object Tags: Team Management, Process Standardization, Onboarding, Data Quality, Automation

---

​

Overview

Implement consistent CRM workflows across your entire team using Required Fields and Triggers to enforce standard operating procedures. This workflow is especially valuable when onboarding new team members or scaling operations, ensuring everyone follows the same data standards regardless of experience level. What you’ll accomplish: Build automated enforcement of your team’s SOPs, reduce training time for new hires, maintain data quality at scale, and enable reliable reporting through consistent data capture. Who it’s for: Operations managers, CRM admins, team leads, and fund managers responsible for process consistency and data quality across growing teams. When to use this: When onboarding new analysts, scaling your team, implementing new processes, preparing for audits, or improving data quality for reporting.

---

​

Prerequisites

• List Owner or List Admin permissions
• Documented standard operating procedures (SOPs) for your team
• Buy-in from leadership on process standards
• Understanding of common data quality gaps in your current workflow

---

​

Workflow Steps

​

Step 1: Audit Current Process and Pain Points

Identify gaps in current workflow: Run data quality audit:

1. Filter your pipeline to last 90 days of entries
2. Check completion rates:

• What % of deals have Owners? Lead Source? Sector?
  • What % of Partner Review deals have investment memos?
  • What % of Passed deals have documented reasons?

1. Identify top 5 most common gaps Survey team:

• What information do you wish was always available?
• What fields do you constantly have to ask others about?
• Where do new team members make mistakes?
• What causes reporting headaches? Review onboarding challenges:
• How long does it take new analysts to learn data standards?
• What do they consistently forget?
• What questions do they ask repeatedly? Common findings:
• 30-40% of deals missing Sector assignment
• Pass reasons rarely documented
• New team members don’t know which fields are important

​

Step 2: Define Your SOPs with Trigger Map

Create comprehensive SOP document: Required at Entry (Add to List):

• Owner (who’s responsible?)
• Lead Source (how did we find them?)
• Sector/Industry (what space?)
• Geography (where based?) Required at Partner Review:
• Investment Memo Link
• Deal Champion
• Competitive Analysis Required at Due Diligence:
• DD Lead
• Target Close Date
• DD Checklist Link Required at Term Sheet:
• Investment Amount
• Ownership %
• Key Terms Summary Required at Pass:
• Pass Reason (specific explanation)
• Pass Category (Valuation, Team, Market, Timing, Thesis Fit)
• Key Learnings (what we learned for future) Map to triggers:

​

Step 3: Create Supporting Infrastructure

Before configuring triggers, set up: Fields with standardized dropdowns:

1. Lead Source dropdown:

• Inbound - Website Form
  • Inbound - Direct Email
  • Outbound - Cold Email
  • Outbound - LinkedIn
  • Referral - Portfolio Company
  • Referral - Investor Network
  • Referral - Personal Network
  • Conference/Event
  • Other

1. Pass Category dropdown:

• Thesis Misfit
  • Valuation Concerns
  • Team Concerns
  • Market/Competition
  • Too Early Stage
  • Timing (revisit later) Templates and examples:
• Investment Memo template in Google Drive
• Example Pass Reasons (good vs. bad)
• Due Diligence checklist template Documentation hub:
• Create wiki page: “CRM Data Standards & Triggers”
• Include: Why each field required, examples, templates
• Link in all trigger-related communications

​

Step 4: Implement Triggers in Phases

Don’t activate everything at once:

​

Phase 1 (Week 1): Required Fields on Add

1. Configure Required Fields: Owner, Lead Source, Sector
2. Announce to team with templates
3. Monitor for 1 week
4. Gather feedback

​

Phase 2 (Week 3): Pass Documentation

1. Configure Status Trigger on “Passed” status
2. Requires: Pass Reason, Pass Category
3. Announce with examples of good pass reasons
4. Monitor for 2 weeks

​

Phase 3 (Week 5): Partner Review Documentation

1. Configure Status Trigger on “Partner Review”
2. Requires: Investment Memo Link, Deal Champion
3. Share memo template
4. Monitor for 2 weeks

​

Phase 4 (Week 7): Opportunity Creation

1. Configure Opportunity Trigger on “Qualified”
2. Target: Active Deals list
3. Document workflow and linking behavior
4. Monitor for 1 month

​

Phase 5 (Week 11): Due Diligence Requirements

1. Configure Status Trigger on “Due Diligence”
2. Requires: DD Lead, Target Close Date
3. Final piece of comprehensive trigger coverage Why phased:

• Reduces change fatigue
• Allows iteration between phases
• Team learns one trigger at a time
• You can refine approach based on earlier feedback

​

Step 5: Train New Team Members

Onboarding flow: Day 1:

• Walk through trigger system and why it exists
• Show example: Add company → Required Fields → Quality data
• Explain each required field and dropdown options
• Share templates and documentation hub Week 1:
• New hire adds first 5 companies with supervision
• Review their Required Fields entries for quality
• Correct any misunderstandings early Week 2:
• Introduce Status Triggers as they move first deals forward
• Walk through Partner Review trigger requirements
• Share investment memo examples

​

Result

• New team members immediately follow standards
• Less variation in data quality between junior and senior team members
• Training time reduced (triggers teach the process)

​

Step 6: Monitor Compliance and Quality

Monthly audit:

1. Run compliance report:

• % of entries with Owner: Should be 100%
  • % of Passed deals with documented reasons: Should be 100%
  • % of Partner Review deals with memos: Should be 100%

1. Sample data quality:

• Are Pass Reasons specific and useful?
  • Are Lead Sources using correct dropdown values?
  • Are Investment Memos substantive?

1. Identify outliers or gaps Quarterly review:
2. Survey team: Are triggers still helpful or burdensome?
3. Review dropdown usage: Are options sufficient?
4. Assess whether new required fields needed
5. Consider retiring fields that aren’t being used

---

​

Expected Outcome

• Consistent data capture across all team members regardless of seniority
• New hires follow process standards from day one
• 100% compliance on critical fields (Owner, Lead Source, Pass Reasons)
• Reliable reporting possible (no missing data causing inaccurate metrics)
• Institutional knowledge captured systematically
• Reduced time spent on data cleanup and “who owns this?” questions
• Faster onboarding (triggers teach the process)
• Better decision-making enabled by complete context

---

​

Tips & Best Practices

Change Management:

• Start with wins: Begin with fields everyone agrees should be required
• Explain the why: “We need Lead Source to analyze which channels work best”
• Show benefits: Report on data quality improvements monthly
• Listen to feedback: Triggers should help, not hinder For Small Teams (2-10 people):
• Fewer triggers needed (easier to enforce through culture)
• Focus on Required Fields for data consistency
• Use Status Triggers only at critical milestones (Partner Review, Passed) For Large Teams (15+ people):
• More triggers needed (can’t rely on informal enforcement)
• Required Fields critical for consistency across geographies/practices Measuring Success:
• Data completeness: % of entries with all required fields
• Consistency: Standard deviation in dropdown usage
• User satisfaction: Survey scores on trigger usefulness
• Time savings: Onboarding time for new hires
• Decision quality: Fewer “incomplete context” complaints from partners

​

Common Mistakes

• Implementing all triggers at once (overwhelming)
• Not providing templates or examples (unclear expectations)
• Never iterating based on feedback (rigidity breeds workarounds)
• Requiring fields that aren’t actually used (creates resentment)
• Not celebrating improvements (miss opportunity to reinforce value)

---

​

Example Use Case

Velocity Ventures scaled from 4 to 12 investment professionals in 6 months: The Challenge:

• New analysts didn’t know data standards
• Senior team members had different conventions
• Partners complained about incomplete deal context
• Reporting was manual nightmare due to inconsistent data Month 1 - Baseline:
• Audited 200 recent deals:
• 60% missing lead source
  • 10% of passes had documented reasons
  • Sector tags inconsistent (“AI”, “Artificial Intelligence”, “Machine Learning” all used) Month 2 - Phase 1 (Required Fields):

1. Created standardized Sector dropdown (12 options)
2. Configured Required Fields: Owner, Lead Source, Sector
3. Announced to team with option definitions
4. Result: 100% of 43 new adds that month had all three fields Month 3 - Phase 2 (Pass Documentation):
5. Created Pass Reason (text), Pass Category (dropdown)
6. Configured Status Trigger on “Passed”
7. Shared examples of good pass reasons
8. Result: 100% of 18 pass decisions documented (vs. 10% before) Month 4 - Phase 3 (Partner Review Prep):
9. Created Investment Memo Link (URL field)
10. Created Deal Champion (Person field)
11. Configured Status Trigger on “Partner Review”
12. Shared memo template
13. Result: 95% of 12 partner reviews had memos ready (vs. 40%) Month 5 - Phase 4 (Opportunity Automation):
14. Configured Opportunity Trigger on “Qualified” status
15. Target: “Active Deals” opportunity list
16. Result: 23 qualified leads automatically created opportunities with linking

---