HR & RECRUITING

Record the Committee Verdict and Route Candidate Next Steps

When the committee logs a decision, this writes the verdict into the candidate's record, archives a finalized decision packet to Coda.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCommittee verdict recordedAirtableAirtable
  • ActionRead verdict, rationale, and packetAirtableAirtable
  • ActionArchive finalized decision recordCodaCoda
  • LogicRoute on hire / reject / hold
  • OutputNotify recruiter with next stepMicrosoft Teams

What it does

Closes the loop after the committee decides. It captures the recorded verdict, locks a finalized decision packet for the audit trail, and branches the downstream action by outcome so the recruiter immediately knows whether to extend an offer, send a rejection, or schedule a follow-up, with no decision falling through the cracks.

When to use it

Use it the moment a committee verdict is entered and you want the candidate record, the documented rationale, and the recruiter's next step all updated in one consistent motion.

How it works

  1. 1A decision field on the candidate record changing to a final verdict triggers the run.
  2. 2The workflow reads the verdict, the rationale notes, and the compiled scorecard packet.
  3. 3It writes a finalized, timestamped decision record to a Coda archive page for compliance.
  4. 4A branch routes on the outcome: hire, reject, or hold.
  5. 5Each branch posts a tailored next-step message and owner to the recruiting Teams channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.