Home/Blog/Ashby Debriefs: Setup, Feedback and AI Summaries
Recruiting AI

Ashby debriefs: schedule the meeting and review AI summaries

Set up Ashby debriefs, check feedback visibility and review AI summaries against interview evidence before your hiring team makes a decision.

Remqa · November 20, 2026 · 5 min read

Short answer

Set debrief defaults in Ashby, add the activity through an interview plan or candidate profile, then schedule and review the panel. Use AI feedback summaries as a discussion aid and check important claims against the original feedback before making a hiring decision.

  • Creating a debrief activity does not complete its scheduling
  • A debrief has no linked feedback form or feedback submission tab
  • Feedback visibility depends on access to the specific job
  • An AI summary needs evidence review, not automatic decision authority

A hiring team arrives at its debrief with an incomplete scorecard, an outdated summary and a calendar invite missing an interviewer. The meeting starts with record collection instead of candidate discussion. In Ashby, the debrief activity, its schedule, feedback access and AI summary are separate things to check. Treating one as proof that the others are ready creates avoidable confusion.

This guide explains the native debrief setup and a recommended review process around it. The preparation checklist, evidence checks and custom AI controls below are operating recommendations. They are not claims that Ashby automatically performs those checks or makes the hiring decision for your team.

1. Set debrief defaults before adding activities

Open Admin > Interviews & Scheduling > Debrief Defaults. On the Schedule page, configure the duration and attendees. Ashby lets you select attendees through their hiring team role on the job, choose whether to include past interviewers and add other attendees. Defaults apply to debriefs created moving forward and can be amended for an individual debrief.

Use the Communication tab for the scheduling calendar, location and interviewer invite templates. Use Reminders for the reminders sent to attendees. Review these settings with the recruiting coordinator and hiring manager. A default attendee rule should describe the intended discussion group, not everyone who has ever interacted with the candidate.

2. Add the activity, then schedule the meeting

In a Schedule Interview activity on the job interview plan, enable Include Schedule Debrief Activity. This creates a debrief activity once the interview has been scheduled. For an exception, open the candidate profile, choose + Add Activity and select Debrief. Neither path should be treated as proof that a calendar meeting is already ready.

Choose Schedule on the debrief activity and then Manual Schedule. Review attendees inherited from the defaults, adjust the panel, and check the title and timezone. Continue to Proposals to review generated schedule options. You can inspect a proposal with View Details and select Use Schedule, or choose Manually Schedule Instead to work from the Panel tab.

Before completing the invite, check the actual recipient list and location on the Calendar Invite tab. Ashby lets you edit these and amend reminders. Only the specified debrief panel receives the debrief notification and calendar invites. The candidate is not notified. Still review the panel for internal access and relevance rather than relying on the meeting title.

3. Know what the debrief does not collect

A scheduled debrief appears as an upcoming interview on each panel member's home page. Members can open it to review the candidate resume and feedback. But the debrief itself has no feedback submission tab and cannot have a feedback form linked to it. Do not build an operating process that waits for a nonexistent debrief scorecard.

Choose an outcome owner before the meeting. Decide who records the reviewed decision, unresolved questions and follow-up responsibilities in your approved hiring workflow. Keep that record separate from an AI-generated recap. A summary of interviews and a hiring decision have different owners and purposes.

4. Check feedback visibility with real user roles

Feedback controls live in Admin > Interviews & Scheduling > Feedback Visibility. Interview Feedback Visibility covers feedback from interviewers on the same panel or schedule. Other Feedback Visibility covers feedback outside that panel, including feedback requested without scheduling. The briefing setting determines whether other feedback appears there.

The applicable visibility setting depends on access to the specific job. Even an Organization Admin or Elevated Access user can fall under Limited Access visibility settings when they lack an applicable access role with Can See Feedback Forms. Those settings can reveal feedback before submission, after submission or never. Submitting one's own scorecard does not automatically grant broader access.

There is another important boundary. Ashby states that feedback visibility settings do not apply when interviewers are not required to give feedback in the interview setup. Test the configured workflow with representative accounts and required-feedback settings. A global role label or an administrator's successful preview is not enough evidence for every interviewer.

5. Review AI summaries against the evidence

Ashby's published AI debrief summary feature aggregates prior interview feedback into a briefing summary. Its setup instruction is to enable AI Generated Interview Feedback Summary under organizational settings. The feature description also supports regeneration and reviewing the source of generated text. Check the actual configuration available in your organization before designing the workflow around it.

Assign a recruiter to inspect the summary before the debrief. Confirm the right candidate and job, identify which interviews are represented and compare consequential statements with the original feedback. If one interviewer reports a concern and another reports contrary evidence, preserve the disagreement. Do not rewrite uncertainty into a confident consensus just to make the recap shorter.

Preparation checkEvidence to reviewRecommended response
Missing feedbackExpected interviews against submitted feedbackLabel the gap and assign a follow-up
Strong summary claimOriginal interviewer wording and contextCorrect unsupported interpretation
Conflicting assessmentsRelevant feedback from each interviewerBring the disagreement to discussion
Restricted materialJob access and intended summary audienceKeep distribution within approved access

6. Keep custom AI preparation inside the access boundary

If you add a custom assistant, give it a narrow preparation task. It can propose an agenda of unanswered questions or organize approved evidence for a reviewer. Do not give the assistant permission to advance, reject or contact candidates merely because it can read the feedback. Those actions need their own authorization and checks.

Carry the job and candidate identifiers with every preparation request. Record which approved feedback version was used, and recheck the packet if interviews or attendees change. A copied summary should not expose material its recipients could not otherwise access. For related access distinctions, see our guide to Ashby candidate notes visibility.

7. Test the workflow and handle exceptions

  1. Check a normal panel with all expected feedback submitted.
  2. Check a debrief where feedback is missing or contradictory.
  3. Test a participant with limited job access and a confidential role where applicable.
  4. Change an attendee and confirm the reviewed packet still has the intended audience.
  5. Document who reschedules or cancels the meeting and who records the outcome.

To cancel an upcoming native debrief, open the candidate profile and choose Actions on the debrief activity, then Cancel Interview. For custom calendar or ATS writes, keep a record of attempted actions and confirm the accepted state before retrying an uncertain response. This retry control is a recommended integration design, not a native debrief delivery guarantee.

Common mistakes to avoid

Do not confuse an activity with a scheduled invite, or a generated summary with completed interviewer feedback. Do not assume the hiring team roster grants permissions. Do not copy a restricted packet into a broad calendar description. Most importantly, keep missing evidence visible. A polished summary should not hide the reason the team still needs a conversation.

How Remqa helps recruiting teams

Remqa builds AI agents for recruiting teams around the actual ATS workflow. A debrief project can start with preparation checks, an evidence review queue and a clear human decision owner. For teams deciding which repetitive work to tackle first, our recruiting workflow review provides a starting point. Bring an example debrief and its access rules to a conversation with an engineer.

FAQ

Questions people ask.

How do you create an Ashby debrief?

Configure Debrief Defaults under Admin > Interviews & Scheduling. Include a Schedule Debrief Activity in an interview activity template, or add a one-off Debrief through + Add Activity on the candidate profile. Then schedule it.

Does the candidate receive the debrief invitation?

Ashby sends debrief notifications and calendar invites only to the users or interviewers specified on the debrief panel. The candidate is not notified.

Can an Ashby debrief have its own feedback form?

No. Ashby does not provide a feedback submission tab or a linked feedback form for a debrief. Agree separately where the hiring team will record its reviewed outcome.

How do Ashby AI debrief summaries work?

Ashby describes summaries that aggregate prior interview feedback on the debrief briefing. Its published setup instruction is to enable AI Generated Interview Feedback Summary in organizational settings. Review the generated text and its sources rather than treating it as a final decision.

Does submitting feedback always reveal other interviewers feedback?

No. Visibility depends on the applicable settings and access to the job. The Limited Access setting can show feedback before submission, after submission or never. Submitting feedback alone does not grant access.

Talk to an engineer

Want an engineer to look at your setup?

Book a free 30-minute call. We look at your tools and your team's week and tell you what we would do first.

Book a free 30-minute call
30 minutesFree, with an engineer
Your stackWe look at what you run today
Straight answerIncluding when we're not the fit