BAINTL Workflow Maps

Purpose

These diagrams visualize the complete workflow for both Hiring Partners (HPs) and Candidates. The HP workflow is a sales cycle to win Job Orders. The Candidate workflow is a delivery cycle to fill those Job Orders.

🏷️ Entity Types & Status Fields

Loxo has two different status systems that work together:

1. 👤 Person Global Status (Contact-level)

Field: Global Status on the Person/Contact record
Purpose: Tracks the relationship state with that individual
Applies to: Both Hiring Partners AND Candidates (universal field)

Current Global Statuses:

🔵 Sourcing: New Lead, Enrich, Prospect
🟡 Engagement: Outreach (auto), Contacted, Responded (auto), Nurture (auto), No Activity
🟢 Active Relationship: Active, Active Client, Shortlist
🔴 Outcomes: Placed, Previous Client, Rejected, Not Interested, Inactive, DNC, Delete Record

2. 📋 Pipeline Stage (Job Order-level)

Field: Stage on the Job Order record
Purpose: Tracks where a Job Order is in the recruiting process
Applies to: Only Job Orders (not individual people)

Pipeline Stages (in order):

Applied
Longlist
Shortlist
Outbound
Recruit Presentation
Client Submittal
First Time Interview
Offer
Placed (Success!)
Rejected (Outcome)

3. 📊 Job Order Status (Job-level)

Field: Status on the Job Order record
Purpose: Tracks the overall state of the Job Order itself
Applies to: Only Job Orders (not individual people)

Job Order Statuses:

Active (Default) - Job Order is open and actively being worked
Hold - Temporarily paused by client
Filled - Successfully filled by BAINTL (placement made)
Filled by Client - Client filled internally or with another firm
Did Not Hire - Client decided not to fill the position
Inactive - Job Order closed/archived

Status Triggers:

Active → Filled: When a candidate reaches “Placed” Pipeline Stage
Active → Hold: Client requests temporary pause
Active → Filled by Client: Client notifies they filled internally
Active → Did Not Hire: Client cancels the search
Hold → Active: Client resumes the search
Any → Inactive: Job Order is archived/closed

Key Distinction

A Person has a Global Status (their relationship with BAINTL). A Job Order has both Pipeline Stages (the recruiting process) AND a Job Order Status (the overall state of the job). One person can be associated with multiple Job Orders at different stages.

🏢 Hiring Partner (HP) Workflow - Sales Cycle

Goal: Find Hiring Partners, build relationships, and secure Job Orders.

graph LR
     System Automation Layer - Person Global Status
    C["🔧 Enrich<br/>Person Status<br/>AI data enrichment"]
    D["📤 Outreach (auto)<br/>Person Status<br/>Campaign active"]
    E["⚡ Responded (auto)<br/>Person Status<br/>Reply detected"]
    F["🌱 Nurture (auto)<br/>Person Status<br/>Long-term follow-up"]
    
     Outcomes - Person Global Status
    O["🚫 Not Interested<br/>Person Status<br/>No current need"]
    P["🚫 DNC<br/>Person Status<br/>Hard opt-out"]
    Q["😶 Inactive<br/>Person Status<br/>Stalled relationship"]
    R["🗑️ Delete Record<br/>Person Status<br/>Remove from system"]
    
     Outcome paths
    D --> O
    E --> O
    H --> O
    I --> O
    K --> O
    M --> O
    M --> P
    M --> Q
    M --> R
    
     Entry Points - Person Global Status
    A["📥 New Lead<br/>Person Status<br/>Candidate discovered"] 
    B["📦 Imported<br/>Person Status<br/>Bulk data entry"]
    
     Sourcing & Vetting - Person Global Status
    H["🎯 Active<br/>Person Status<br/>Engaged candidate"]
    I["📞 Contacted<br/>Person Status<br/>Human outreach made"]
    J["⭐ Prospect<br/>Person Status<br/>Pre-qualified"]
    K["📋 Shortlist<br/>Person Status<br/>Top candidate"]
    
     Final Outcomes - Mixed
    P["🎉 Placed<br/>Person Status + Pipeline<br/>✅ SUCCESS!"]
    S["❌ Rejected<br/>Person Status + Pipeline<br/>Not selected"]
    T["🚫 Not Interested<br/>Person Status<br/>Declined opportunity"]
    U["🚫 DNC<br/>Person Status<br/>Hard opt-out"]
    V["😶 Inactive<br/>Person Status<br/>Stalled process"]
    W["🗑️ Delete Record<br/>Person Status<br/>Remove from system"]
    
     Flow
    A --> C
    B --> C
    C --> D
    D --> E
    D --> F
    F -.->|Re-engage| D
    E --> H
    E --> I
    H --> J
    I --> J
    J --> K
    K --> L
    L --> M
    M --> N
    N --> O
    
     Job Order Status triggers
    P --> JO1
    S -.->|Client decision| JO2
    S -.->|Client decision| JO3
    S -.->|Client decision| JO4
    JO2 -.->|Archive| JO5
    JO3 -.->|Archive| JO5
    JO4 -.->|Archive| JO5
    
    %% Styling
    classDef entry fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef system fill:#fff3e0,stroke:#f57c00,stroke-width:2px
    classDef sourcing fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef pipeline fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef success fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
    classDef outcome fill:#ffebee,stroke:#d32f2f,stroke-width:2px
    classDef jobstatus fill:#e1bee7,stroke:#7b1fa2,stroke-width:2px
    
    class A,B entry
    class C,D,E,F system
    class H,I,J,K sourcing
    class L,M,N,O pipeline
    class P success
    class S,T,U,V,W outcome
    class JO1,JO2,JO3,JO4,JO5 jobstatus

📊 Candidate Workflow: Person Status vs Pipeline Stages

Type	Status/Stage	Activity	Business Context
Person	New Lead	Manual entry	Initial candidate discovery
Person	Imported	Bulk import	Kelsey’s offshore data entry
Person	Enrich	AI enrichment	Data validation
Person	Outreach (auto)	Campaign active	Job-specific outreach
Person	Responded (auto)	Reply detected	High Priority: Candidate engaged
Person	Active	Phone call/meeting	Active engagement
Person	Contacted	Email/InMail sent	Manual outreach
Person	Prospect	Pre-qualified	Initial vetting complete
Person	Shortlist	Top candidate	Human vetted
Pipeline	Applied	Candidate applied	Inbound application
Pipeline	Longlist	Initial pool	Preliminary interest
Pipeline	Shortlist	Top tier	Narrowed selection
Pipeline	Outbound	Outreach phase	Active sourcing
Pipeline	Recruit Presentation	Internal pitch	Team review
Pipeline	Client Submittal	Submittal	Sent to hiring manager
Pipeline	First Time Interview	Interview scheduled	Evaluation phase
Pipeline	Offer	Offer extended	Terms discussion
Pipeline	Placed	Success!	Revenue generated!
Person	Rejected	Not selected	Wrong fit

🔗 How the Workflows Connect

graph TB
    subgraph HP_Workflow [Hiring Partner Sales - Person Status]
        HP1["📥 New Lead"] --> HP2["📤 Outreach (auto)"]
        HP2 --> HP3["🎯 Active Client<br/>Job Order Secured!"]
    end
    
    subgraph Bridge [The Bridge - Job Order Created]
        HP3 -->|"Creates Job Order"| JO1["📋 Job Order<br/>Pipeline: Applied/Longlist"]
    end
    
    subgraph Candidate_Workflow [Candidate Delivery - Mixed]
        C1["📥 New Lead<br/>Person"] --> C2["🔧 Enrich<br/>Person"]
        C2 --> C3["📤 Outreach (auto)<br/>Person"]
        C3 --> C4["📋 Shortlist<br/>Person"]
        C4 -->|"Submitted to Job Order"| JO2["📋 Client Submittal<br/>Pipeline"]
        JO2 --> JO3["🎤 First Time Interview<br/>Pipeline"]
        JO3 --> JO4["💼 Offer<br/>Pipeline"]
        JO4 --> C5["🎉 Placed<br/>Person + Pipeline"]
    end
    
    subgraph Success [Success Loop - Person Status]
        C5 -->|"Feedback"| HP4["👥 Previous Client<br/>Person Status"]
    end
    
    classDef hp fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef bridge fill:#fff3e0,stroke:#f57c00,stroke-width:3px
    classDef person fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef pipeline fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef success fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
    
    class HP1,HP2,HP3,HP4,C1,C2,C3,C4,C5 person
    class JO1,JO2,JO3,JO4 pipeline

The Process Flow

HP Workflow (Sales): Find Hiring Partners → Build relationships → Win Job Orders
The Bridge: Each Job Order becomes a search mandate with its own Pipeline Stages
Candidate Workflow (Delivery): Source talent → Vet candidates → Submit to Job Order → Interview → Place
Success Loop: A successful placement converts the HP to a “Previous Client” for future business

🧠 Strategic Overview

The “Two-Track” Model:

MPC (Most Placeable Candidate) Shortcut:
- Start with a great candidate (Person Status: Shortlist)
- Run HP workflow to find a Job Order for that specific candidate
- Fast-track to placement
Search Business (Traditional):
- Win Job Order first via HP workflow (Person Status: Active Client)
- Run full Candidate workflow to fill the position
- Systematic sourcing through Pipeline Stages

Key Distinction:

Person Global Status: Tracks the relationship with an individual (applies to both HPs and Candidates)
Pipeline Stages: Track the recruiting process for a specific Job Order (only on Job Orders)

The Win-Win

When both workflows execute successfully, BAINTL wins the Job Order AND places the candidate, creating revenue and a long-term client relationship.

Everyday Workflows Client Portal

Explorer

Workflow-Maps

BAINTL Workflow Maps

🏷️ Entity Types & Status Fields

1. 👤 Person Global Status (Contact-level)

2. 📋 Pipeline Stage (Job Order-level)

3. 📊 Job Order Status (Job-level)

🏢 Hiring Partner (HP) Workflow - Sales Cycle

📊 Candidate Workflow: Person Status vs Pipeline Stages

🔗 How the Workflows Connect

The Process Flow

🧠 Strategic Overview

Graph View

Table of Contents