Placement Counselor Co-pilot

A placement counselor co-pilot is only as good as its cites. Every sentence in a draft must trace to two records: the student's profile and a job that already exists on the office's allowed list. If either record lacks a fact the draft would need, that part of the draft stays empty. The counselor still sends the message.

The model is not a job board and not an employer directory. It does not create postings, invent recruiter names, or fill in student experience. It retrieves a listed job, shows which fields it used, and drafts language a human can check. Quality here means a counselor can point at a line in the email or the interview packet and name the source field.

This writing step comes after you have already decided that a role is a reasonable path for the student. career pathway matching is the fit question. The co-pilot only writes after the allowed list has already constrained which jobs may be named in outreach.

Start from the list the office already maintains: employer partnerships, screened postings in the career portal, and roles staff have approved for student contact. Retrieve the job by the identifier on that list. Do not retrieve by a title the student remembered from a feed.

Student context usually already lives in systems you run for other reasons. Student and advising records may sit in Ellucian or Anthology. Employer relationships and prior outreach may sit in Salesforce. Course and credential history may sit in Canvas. Treat those platforms as the system of record for people and history. Treat the allowed job list as the system of record for openings you are willing to mention.

Do not paste a link from a student's text thread and treat it as a posting. If the role is not on the list, retrieve nothing and tell the counselor the job is out of scope. Adding it to the list is a staff decision, not a model decision.

When a sector is moving, job market signal monitoring can explain demand. It still does not authorize a specific employer, a contact, or a posting that never entered the list.

One walkthrough: Priya is a December graduate in accounting. Her profile includes work-authorization status, a tax internship with the software named, a location constraint (commutable to the city campus), and a note that she wants staff accountant work rather than unpaid "experience" roles. The allowed list includes posting J-4418, Staff Accountant at a local CPA firm, with an office email from the partnership record, a start window, and a software requirement that matches her internship. The co-pilot may retrieve J-4418 for this draft. A similar title at a firm that never entered the list is not a substitute, even if the model could write a fluent paragraph about it.

Once the job record is in hand, generate two artifacts. Both must carry cites the counselor can see without hunting through source systems.

Outreach: a message in the office's usual pattern (counselor to employer, or student to employer with counselor review) that names the posting as it appears on the list, uses only profile fields that exist, and addresses only the contact on the job record. Show cites next to the claims, for example profile.internship_tax, job.J-4418.title, and job.J-4418.contact. If the job record has no contact, leave the recipient field empty. Do not invent a first name or a generic inbox.

Interview prep: a short packet tied to the same two records. Talking points and likely questions should map to duties and requirements on J-4418 and to evidence on Priya's profile. If the posting does not list a competency, do not coach it as if the employer asked. If her profile does not include a tool, do not write that she used it.

Keep the counselor's voice and the office's privacy habits. The draft is a starting point for an office that already has templates. It is not a new channel that speaks for the institution on its own.

Three failure modes show up once drafts get easy. Build the workflow so each one is visible before anything leaves the office.

Emailing a job not on the list. A student forwards a social post. The model extracts a title and writes a warm introduction. You have now implied an employer relationship you do not have, and you cannot later attach the outcome in employment outcome tracking to an official posting. Block retrieve unless the job ID is on the allowed list.

Inventing an employer contact. The posting is real and the partnership may be real, but the record has a careers portal, a phone note, or a blank email. Completing the gap with a plausible address is a data incident. An empty recipient field is the correct draft. Staff look up the contact in Salesforce or the partnership file and write it back to the job record before anyone sends.

Sending without review. Auto-send, or a counselor who never opens the cite panel, turns a draft into official speech. The student may be described inaccurately. The employer may be approached for a role that was never approved. Review is not a courtesy pass. It is the send step.

Open the draft beside the two source records. Check three things in order. The job ID matches the allowed list. Every claim about the student has a profile cite. The recipient is exactly the contact on the job record, or the field is blank.

Edit for tone, timing, and office policy. Then send from the counselor's account, or from the student's account under the process you already use. The model does not send.

If a live conversation with a recruiter is next, recruiter call coaching can reuse the same cited prep. Do not let coaching introduce a new employer or a new posting that was not retrieved from the list.

If Priya's profile had only major and graduation term, the co-pilot should not draft a body that implies internship software, authorization, or a commute. Leave those sentences out. Give the counselor a list of missing fields instead of a polished email.

A thin profile is a counseling task: get the resume facts, authorization status, and location constraint into the record. Until then you can still retrieve J-4418 and walk Priya through the posting in a meeting. You cannot honestly claim fit in writing.

Empty drafts are a quality signal. A fluent paragraph with no cites is the failure the office should refuse to send.