A person who knows your work is not automatically someone you may name as a reference. Virginia Tech’s career guidance advises asking permission before listing references, supplying relevant materials and keeping them updated and thanked. The fictional exchange below turns that preparation into a complete small workflow. No message has been sent, no permission obtained and no hiring outcome established.
Make the initial request answerable
Imagine Jordan applying for a project coordinator role and considering a former supervisor, Casey. Jordan should first check the actual application’s instructions and the relationship being invoked. A reference request should not invent a job requirement or imply that Casey has already agreed to discuss every part of Jordan’s career.
An original draft can read: “Subject: Permission to name you as a reference. Hello Casey, I am applying for a project coordinator role and wondered whether you would be comfortable serving as a reference about our work together on the community events project. I can send the role description and a current resume through a route you prefer. Please feel free to decline. I will not list your contact details unless you agree. Thank you, Jordan.”
Leave the status genuinely open
That message has asked a question. It has not created consent. In an actual private application note, Jordan can record “permission requested, no answer yet” and keep Casey off the submitted reference list while the question remains unresolved. A deadline does not transform silence into an agreement.
If a real answer says no, acknowledge it without asking the person to justify the decision. If there is no answer, follow the actual application process and consider another suitable person rather than repeatedly escalating the same request. This article prescribes no universal waiting interval and no required number of references. Those details belong to the particular application and relationship.
Confirm the scope after an actual yes
For a second fictional branch, suppose Casey agrees but asks to receive only the role description and current resume. Jordan’s reply can read: “Thank you for agreeing. I will send those two documents through the route you requested. Please confirm the professional contact details you want used and whether there are any limits I should pass on about contact arrangements. I will keep you updated about the application.”
Before a real submission, check the correct person, role and agreed contact information. Do not add private phone numbers found elsewhere or forward unrelated documents simply because the reference has said yes. Permission to serve in this application is a bounded agreement, not general authority to distribute someone’s information. This is practical correspondence guidance, not legal privacy clearance.
Finish the loop without inventing endorsement
Keep the reference document separate where the actual application asks for it, and send the agreed supporting material rather than a large archive of work. An update can identify a real change in status or expected contact. A thank-you can be complete even if the application does not produce an offer.
If Jordan later applies for a substantially different role, revisit what Casey is willing to discuss instead of treating the earlier agreement as permanent. A plain private note can track the request, actual reply, agreed details and update. Paid contact-management software is optional; it cannot replace the permission that makes the list usable.
Sources & further reading
Published sources for the details and examples discussed in this story.
