Submission chase and escalation when a client gives no feedback

Outcome. A candidate sent to a client is chased on a schedule instead of on memory, and after two silent rounds the account owner is told, so a submission either moves or is closed on purpose.

Workflow map Enrollment, branches and actions at a glance recruiting-002

flowchart TD
    A[Deal stage Submitted and pipeline type placement] --> B[Stamp submission date, chases = 0]
    B --> C[Delay 3 business days]
    C --> D{Still in Submitted?}
    D -->|No| E[End, client answered]
    D -->|Yes| F[Chase task to recruiter, chases = 1]
    F --> G[Delay 2 business days]
    G --> H{Still in Submitted?}
    H -->|No| E
    H -->|Yes| I[chases = 2, notify recruiter and account owner]
    I --> J[Call task to account owner]
    J --> K[Delay 3 business days]
    K --> L{Still in Submitted?}
    L -->|No| E
    L -->|Yes| M[Notify manager, decision task, chases = 3]

When to use it, when not to

• UseUse it on the placement pipeline once a Submitted or Shortlist sent stage exists and a deal is created per candidate per vacancy.
• UseUse it when the feedback window is written into the terms of business, or when you are ready to pick a default of five working days.
• SkipDo not use it on the business development pipeline. A deal there is a mandate, not a candidate, and the enrollment filter on Pipeline type is what keeps the two apart.
• SkipDo not use it when one deal carries the whole vacancy and several candidates. The chase text and the counter both assume one candidate per deal, otherwise a single reply closes chases for people the client never saw.