Turning AI Interview Notes Into an Onboarding Plan: From Evidence to the First 90 Days

The interview produces the most detailed assessment a company will ever write about an employee, and it is usually filed and forgotten the day the offer is accepted. The gaps the panel noted become surprises in month three, the strengths they praised go unused, and the new hire writes a 30-60-90 plan from the job posting rather than from what the team actually learned about them. This page shows how a hiring manager turns the report from Interviewer Mode, section scores, quotes and flags, into an onboarding plan that uses the strengths, closes the gaps and sets the first review's expectations, without the plan reading like a list of what was wrong with the candidate. The scorecard that produces the raw material is in interview scorecard template with AI scoring, the candidate's version of the plan is in 30-60-90 day plan for an interview, and the feedback that goes to those not hired is in how to give rejected candidates feedback from AI interview notes.

What the report gives you

None of this is shared with the new hire as a report; it shapes the plan the manager writes and the conversations they have.

Writing the plan

1. Days 1 to 30, learn: the people, the systems, the why. Build in the strengths immediately: a new hire who scored high on communication presents something small in week three. Pair on the gap the panel identified, framed as 'how we do it here' rather than remediation.
2. Days 31 to 60, contribute: a real deliverable in the area of strength, a supported one in the area of growth. Schedule the check-in that tests each flag, phrased as an open question about how things are going.
3. Days 61 to 90, own: something that is theirs, chosen against what they said they wanted. Set the expectations for the first review in writing, using the competencies the rubric scored, so the first review measures what the interview measured.
4. Keep the plan to one page; the report was for deciding, the plan is for doing.
5. Share the plan in the first week and ask what is wrong with it; the new hire knows things about themselves the interview did not capture.
6. Delete the flags from your own working notes once each has been tested; a disproved hypothesis should not follow someone into their first review.

What not to do with the notes

The report is an assessment made under interview conditions by people who had an hour; it is not a personnel file and it is not a verdict. Do not share the raw scores or flags with the new hire or with their peers; do not let a flag become a reputation before the person has worked a day; do not treat a strength as a permanent assignment. Keep the report where the hiring process keeps it, on the interviewer's machine for the period HR sets, and build the plan from it rather than attaching it. If the interview surfaced something that would be a real problem, such as a skills gap the role cannot carry, the time to address that was before the offer; after it, the plan's job is to make the hire succeed.

The first review

• Use the same competencies the rubric scored, so the new hire is measured against what they were hired for.
• Compare the panel's assessment with the first-review evidence; the gaps between them calibrate the interview process as much as the hire.
• Where the interview predicted well, note what question or round did it; where it predicted badly, change that round.
• Ask the new hire what in onboarding helped and what did not; feed that back into the plan template.
• Record the development goals for the next period against what they said they wanted in the interview.
• Close the loop with the panel: a short note on how the hire is doing teaches interviewers more than any calibration session.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant for candidates and, in Interviewer Mode, a copilot for interviewers that offers role-specific questions by category, live rubric scoring with evidence notes, follow-up question ideas, red and green flags as hypotheses, and a hire/no-hire report with section scores, flags and quotes, free in the desktop app for Windows and macOS with no signup; teams get volume licensing, centralised billing, SSO/SAML, custom templates per role, a centralised evaluation dashboard and priority onboarding, and audio is streamed for transcription in short segments and not stored on CoPilot Interview's servers, the transcript stays in the interviewer's Documents folder, and only the transcribed text goes to the model chosen. The report is built for the hiring decision, and the plan here is the manager's work with it. Interviewers hold the decision and the law; the copilot holds the notes. For candidates the product is built for practice, and if a candidate ever considers live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do I turn interview notes into an onboarding plan?

Use the report's section scores to decide where to lean and where to support, the quotes for how the person wants to work, the flags as hypotheses to test in check-ins, and the motivation answers as the first review's development goals. Write a one-page 30-60-90 plan from that and share it in week one.

Should I show the new hire their interview scores?

No. Share the plan, not the report. The report was for deciding; the plan is for doing.

What do I do with red flags from the interview?

Treat each as a hypothesis, test it with an open check-in in the first two months, and drop it once disproved. A flag must not become a reputation.

How does this improve interviewing?

Comparing the panel's assessment with first-review evidence shows which rounds and questions predicted and which did not; change the ones that did not.

Where do the notes come from?

Interviewer Mode in CoPilot Interview produces a report with section scores, quotes and flags after each interview, stored on the interviewer's machine.