A cold emailing template should begin with a brief introduction, a verified reason this person is relevant, and one bounded informational request. Keep the native email subject and body separate from the evidence review.
The complete C01 model below is fictional. Riley, Jordan and the profile fragment are invented teaching inputs, not actual contacts or a sent message. Real sender/recipient facts must be supplied and confirmed before adapting it.
Verify the reason before polishing the sentence
The University of Chicago's networking-email resource presents brief introductions, context and requests for informational conversations. Adopt that structure without copying its sample identities, alumni relationships, phone number or wording. UChicago: Networking Email Templates
For original C01, the supplied fictional facts are:
| Evidence ID | Supplied fact | What the draft may say |
|---|---|---|
| S1 | Riley is a student | A brief student introduction |
| S2 | Riley is working on a volunteer sign-up project | The project context |
| P1 | Jordan's supplied profile fragment says coordinates weekend library volunteers | The relevant coordination role |
No supplied fact establishes a shared school, previous meeting, referral, award, hiring role or successful program outcome. Those claims do not become true because they make the opening warmer.
The connection to Riley's question is specific: someone coordinating volunteers may have a perspective on what first-time volunteers need before a shift. The question asks for that perspective; it does not assert that Jordan has solved Riley's project.
For a real draft, preserve the exact verified excerpt, source URL, retrieval date and why it connects to the sender's question. Those fields remain blank in the actual-person record until supplied. An absent P1 cannot be replaced by invented profile detail.
Copy the complete fictional model
C01 model subject: Question about volunteer coordination
C01 model body:
Hi Jordan,
I am Riley, a student working on a volunteer sign-up project. Your description of coordinating weekend library volunteers caught my attention.
I would like to understand how you decide what a first-time volunteer needs before their first shift. Would you be open to a 15-minute informational conversation in the next two weeks?
If a call is inconvenient, a short reply about that question would also help.
Thank you for considering it.
Riley
The introduction states the sender's role and project. The next sentence names the supplied recipient context. The question concerns one practical decision, then the request bounds the conversation.
The 15 minutes and two-week window are proposed limits in this fictional request, not a confirmed appointment or a universally optimal response strategy. No actual conversation, reply or meeting is recorded.
The short-reply alternative asks about the same question. It is not another request for a résumé review, referral, introduction or job. Keeping that alternative narrow gives the recipient a different way to answer the one topic.
Trace each claim to its input
| C01 wording | Evidence or role | Review result |
|---|---|---|
| Student working on a volunteer sign-up project | S1/S2 | Supported by fictional inputs |
| Coordinating weekend library volunteers | P1 | Supported by supplied fictional fragment |
| What a first-time volunteer needs before a shift | Sender's learning question | A request, not a fact about Jordan's results |
| Fifteen-minute conversation in the next two weeks | Proposed scope | No appointment implied |
| Short reply about that question | Same-topic alternative | No added task bundle |
Keep requests and observations distinct. Asking how someone makes a decision does not establish that you know their process; proposing a call does not establish availability or consent.
The evidence review belongs beside the maintained draft, not inside the email as a table the recipient must interpret. Native subject/body remain usable plain text.
Remove unsupported praise without adding new claims
Use C02 as a revision exercise. Its deliberately invented bad sentence is Your award-winning program transformed the city. That is an unsupported example, not a fact about the fictional recipient.
Replace it with the P1-based sentence in C01: Your description of coordinating weekend library volunteers caught my attention. Do not swap it for another unsupported compliment, a guessed result or an alleged shared connection.
The revision improves evidence discipline; it does not prove the recipient will respond. Keep the removed wording and why it was removed in the review record, so a later rewrite does not reintroduce it.
If the real role description changes or the source cannot be confirmed, revise the personalization and clear any Ready for adaptation label. The email can remain a draft while its factual basis is unresolved.
Preserve the native draft's status
Maintain two plain-text fields: subject and body. Keep the sender/recipient evidence record separately, with Draft only visible in the review packet. Actual email addresses, relationship facts, profile URL/date and responses remain blank unless supplied.
Before using a real draft, check the sender introduction, recipient relevance and single request against the source record. A refusal is a response to respect; no response establishes no appointment, referral or permission for automation. Do not label silence a proven personal rejection.
This review does not send anything, connect an inbox, scrape profiles, build mail merge or track opens. It makes no response, job, deliverability or legal-compliance guarantee. The output is a reviewed introduction, not an outreach campaign.
The local HTML review shows the native text and claim annotations using literal-text rendering. It is not an email renderer or sending service. Actual copying, line breaks in the email client, keyboard use and narrow layout require testing.
Copy this prompt to prepare your native draft
Write a complete original US-English informational cold-email subject/body in plain text, plus a separate personalization-evidence review and blank real-person record. Reference https://careeradvancement.uchicago.edu/career-toolkit/grow-your-network/templates-for-networking-emails/ for brief introduction/context/bounded conversation structure only. No copied samples/identities/phone/alumni wording, invented relationships/referrals/awards/hiring roles, response/job guarantee or sales campaign.
Fictional C01 only: Riley is a student (S1) working on a volunteer sign-up project (S2); Jordan's supplied fictional profile fragment (P1) says coordinates weekend library volunteers. These are invented teaching inputs, not actual contacts, source URL or achievements. Real personalization needs confirmed excerpt, source URL, retrieval date and relevance to the sender's question. Missing real P1 blocks readiness, not invention.
Use this complete original model as a labeled fictional draft:
Subject: Question about volunteer coordination
Body:
Hi Jordan,
I am Riley, a student working on a volunteer sign-up project. Your description of coordinating weekend library volunteers caught my attention.
I would like to understand how you decide what a first-time volunteer needs before their first shift. Would you be open to a 15-minute informational conversation in the next two weeks?
If a call is inconvenient, a short reply about that question would also help.
Thank you for considering it.
Riley
Annotate student/project to S1/S2 and coordination role to P1. Question is a learning request, not a claim of known recipient process/results. One bounded informational conversation plus same-question reply alternative; no job/referral/résumé review bundle. Proposed duration/window do not book a meeting. Actual response/call/referral/appointment remain blank.
C02 revision exercise: deliberately unsupported bad sentence “Your award-winning program transformed the city.” is invented bad wording, not recipient fact. Remove it and use P1 wording only; no new flattery/shared alumni/previous meeting/referral. Retain revision reason separately. Real role/source changes invalidate readiness until reviewed.
Native subject/body first; evidence and Draft only status separate. Real email addresses/profile URL/retrieval date/relationship/response remain blank until supplied. A decline is a declined request to respect; silence leaves the response unknown rather than proving personal rejection. Neither authorizes automation/tracking or establishes an appointment. No sending, inbox connection, scrape/mail merge, open tracking, deliverability or legal-compliance claim.
Optional later static HTML review shows text and evidence annotations literally, no Send/Track/Book controls or email-renderer promise. Actual copy/line breaks/email-client/keyboard/article width/360 px need tests; no email sent, HTML built or captures. End with separate optional NOS area: prepared HTML wording/evidence review can be saved/rendered while native email draft stays authoritative. No inbox integration, saved outreach records, sending, tracking, export or automatic source updates without proof.
Optional NOS use: a separate review of wording and evidence
Keep the confirmed subject/body in the user's native email draft and its source record alongside it. A prepared HTML review in NOS can show how the fictional model's statements trace to S1/S2/P1; NOS supports HTML saving and rendering.
Verify actual review layout, text copying and hosted behavior before presenting a working example. That review neither sends the draft nor supplies a missing relationship, recipient fact or reply.
Explore NOS with the evidence review. The useful draft gives the recipient a clear reason for the contact and one understandable choice about the requested conversation.