A former colleague has agreed to be a reference, and the employer has now asked for their details. You remember a shared project clearly; the colleague remembers a different part of it. Meanwhile, your application uses a newer job title and emphasizes responsibilities they never saw. Sending a large bundle of files does not resolve that mismatch. The useful next step is to brief your referees on this particular opportunity, while leaving their account of your work entirely their own.
This guide starts after you have identified someone suitable. It focuses on a short context packet: what the employer has actually requested, which application version matters, what the person observed and what remains outside their knowledge. Paper or a local document is enough. If you already use CVura, its connected role and chosen-document context can help you locate the application before assembling the packet yourself. The method does not depend on the app, and it does not promise a favourable reference or a hiring result.
Start with the request, not a generic reference template
Read the employer’s actual request before contacting anyone again. Are they asking for contact details, a completed form or a written recommendation? Which relationship must the person have had with you? Is there a stated deadline or a confirmed contact route? Record the answers you can verify, and leave unanswered questions visible. A general request for references does not tell you which questions will eventually be asked.
Keep this briefing separate from the reference list you provide to the employer. The list identifies a person and an agreed contact route. The briefing helps that person understand one application. Neither document replaces the employer’s form or a recommendation they have explicitly requested. For the earlier task of choosing and recording references, use the separate reference-list guide rather than rebuilding that work here.
If you cannot meet an instruction, ask the recruiting contact a focused question. Explain the particular difficulty and ask what alternative they would accept. Do not relabel a colleague as a manager to make the form appear complete. A clarification is more useful than a polished packet built around the wrong relationship.
Brief your referees using what they actually observed
Before assembling files, make two short private notes: what this person saw you do, and what they did not see. Describe the relationship as it existed then. A former project lead may now have a more senior title, but that new title does not change their original involvement. Similarly, working in the same organisation is not the same as reviewing each other’s work.
The University of Manchester’s careers guidance stresses that referees comment within their own experience of you. Use that boundary to select reminders, not to invent a stronger story. A meeting they attended, a handover they reviewed or a task they supervised can jog their memory. A later promotion, a separate qualification or a result achieved after they left belongs outside their direct observation unless they independently know it.
Choose concrete reminders that connect to the new role. Describe your own task, the setting and the part they witnessed. Mark shared work as shared. If a figure in your application is an estimate or comes from another team, do not turn it into something the referee supposedly confirmed. Leave room for them to correct your recollection or say that they do not remember enough.
Manchester Careers Service: contacting and briefing referees
Assemble a small packet with a clear reading order
Put the practical request first: the role, organisation, known process and any confirmed timing. Then add a short explanation of why the role interests you. Select two or three responsibilities from the advert that matter to the relationship you had with this referee. This is a reading aid, not a request to discuss every skill in the job description.
Include the relevant advert or an accessible copy and the resume version actually submitted. If that version has since been corrected, explain the correction instead of silently replacing history. Label each attachment clearly. A person should not have to guess whether a file marked “latest” is the one the employer received or an unfinished draft for a different job.
Finish with a few factual memory prompts and the contact route you have agreed to share. Remove unrelated application histories, private third-party details and internal work materials you are not entitled to distribute. Summarize the necessary context in your own words when that is sufficient. The packet should remain understandable when its recipient opens only the message first; the attachments provide supporting detail.
Distinguish submitted files from later drafts
Work through Anika’s initial message and context note
Anika Vale is applying for an operations coordinator role at Hearthline Services. The fictional employer asks for a former supervisor’s contact details. Tomas Reed led Anika’s team at Willow Quay Workshop between April 2023 and September 2024. He saw her maintain a handover log and explain unresolved service queries. He did not oversee purchasing budgets, although the new advert mentions budget monitoring.
Anika first checks whether Tomas is willing and which contact details he wants shared. Once he agrees, she sends the role information and submitted resume, with a short note below. She does not ask him to predict her performance in duties he has never seen. The note makes it easy to distinguish a remembered example from a requested endorsement.
Offer reminders without composing somebody else’s answer
A briefing can include an accurate reminder of a task without prescribing the conclusion the referee should draw. “You reviewed the handover log” identifies an observation. “Tell them I was the best coordinator you ever managed” requests a judgment and may also exaggerate the relationship. Read your note for that difference before sending it.
Ask whether the person needs further context or sees an error. They may remember a different division of responsibility, be unavailable during the expected contact period or have limits on what they can discuss. Those answers help you prepare accurately. They are not obstacles to negotiate away with more persuasive wording.
Keep the reference in the person’s own voice. Do not draft an unsolicited recommendation for them to sign, manufacture praise or ask them to conceal a material difference between your application and their recollection. If an application process explicitly requests a particular writing arrangement, clarify the instructions and attribution. A concise factual packet still has value because it separates your account from the independent assessment being requested.
Retrieve application context if you already use CVura
CVura’s current App Store description says it keeps opportunities and chosen documents connected. If you already use that feature, open the relevant opportunity and identify which document you selected for this application. Compare it with your actual sent copy before using it in the reference packet. Organised files make retrieval easier; they do not establish that a claim is correct.
Prepare the briefing and any permission record separately in a place that suits your own arrangements. This workflow assumes no dedicated referee-sharing feature, automatic message, employer contact or transfer from a ResumeField exercise. You choose what to send through the channel you have agreed with the person. A local file or paper note works as well.
ResumeField and CVura share the publisher Rocket Digital Limited. This is an optional first-party workflow, not an independent product recommendation. Check the app’s own privacy information before adding personal information; ResumeField’s browser-only exercises do not describe a separate app’s data handling.
Send a scoped update when something important changes
Anika later receives a confirmed contact window. She sends Tomas a brief update stating what changed and that the original role and submitted documents remain the same. She does not resend the whole archive or invent urgency because the process feels uncertain. If a deadline is given, she states the actual deadline and checks whether he is available.
Handle a correction just as explicitly. Identify the relevant sentence or attachment, state the accurate fact and explain which version it replaces. If the employer also needs the correction, deal with that separately through the appropriate recruiting contact. Asking a referee to use the corrected fact does not correct an already submitted application.
When the opportunity changes substantially, revisit the briefing. A new role may call for examples the person did not observe. Do not keep adding prompts until the packet implies broader knowledge than they have. Use a focused recruiting email when you need to clarify a process requirement; repeated messages to the referee cannot answer a question only the employer can resolve.
Ask a focused process question by email
Close the loop without requesting a rehearsed verdict
Thank the person for the time they have agreed to give. If the application ends or the reference is no longer needed, let them know so they are not waiting for a contact that will not arrive. Share the outcome you actually know. Silence from an employer is not proof that the reference went badly, and it is not evidence that someone failed to respond.
For your own record, keep the role, the briefing version, the agreed contact details and any confirmed next action together. Update inaccurate information rather than carrying it into the next application. Before reusing the packet, check the new request and ask the person again about the particular context. Your goal is a reliable handover of facts that supports an independent account, not a standard script circulated indefinitely.
Questions
Should I send the same briefing to every referee?
Keep shared role facts consistent, but tailor the memory prompts to what each person actually observed. Someone who supervised one project should not receive a note implying that they can confirm your entire career. Check the employer’s relationship requirements separately.
What if the person remembers the work differently?
Compare your account with reliable records and correct your own wording where needed. Do not ask the person to repeat your version merely for consistency. If the difference affects a submitted application, address that through the appropriate recruiting channel as well.
Do I need to know when the employer will call?
Share a confirmed window if one exists. If timing is unknown, say so and update the person when you receive useful information. Avoid guessing a date or presenting your own expectation as an employer’s commitment.
Can I prepare this without an app?
Yes. A concise message, the relevant documents and a private local note are enough. CVura is an optional way to retrieve existing application context if you already use it; the briefing does not require an app or automated sharing.