Reviewed: 9 October 2026. The candidate, organisation, role and upload instructions below are fictional. The letter is an original example, not a university template, a real application or evidence of selection. Follow the actual employer's current instructions.
Format the letter around the application brief
A cover letter's format should make its purpose and evidence easy to follow. Start with the employer's actual submission instructions, then decide how to present the role, relevant experience and close. A readable document does not independently prove that a particular application system parsed it or that a recruiter accepted it.
Harvard's cover-letter guidance recommends concise, factual, tailored letters with evidence connecting experience to role requirements, and checking formatting after conversion. These are narrow preparation principles. They do not establish a universal font, word count, file type or ATS guarantee for employers in India. The complete letter below uses independently invented facts and wording.
If an application asks for a text field, prepare for that field. If it requests an uploaded document, check its accepted types and size. A default preference for PDF should not override an employer's explicit request for a different format.
Original candidate and role record
The fictional organisation is Open Shelf Community Services. Its supplied brief advertises a Programme Records Assistant role, reference OS-17. The role involves maintaining event records and preparing a weekly status note from approved inputs. The brief names no individual contact and requests a separate cover-letter PDF of no more than one page and 1 MB, alongside a résumé in its own upload field.
The candidate is Kavya Rao, based in Mysuru. In a fictional college volunteering activity, Kavya maintained a list of twelve event sessions. She checked session dates and named facilitators against the coordinator's supplied schedule and flagged two missing facilitator names. The coordinator provided those names, and Kavya updated the list. She also drafted a weekly note that the coordinator reviewed. No employment experience, certified software qualification or measured efficiency improvement is supplied.
The application account is stipulated to contain Kavya's current contact details. The exercise supplies no email address or phone number, so the public example does not invent either. In a real document, include the actual contact details requested by the employer and check them against your account and résumé.
Complete original cover letter
Kavya Rao
Mysuru
9 October 2026
Hiring Team
Open Shelf Community Services
Dear Hiring Team,
I am applying for the Programme Records Assistant role, reference OS-17. The advertised responsibility for maintaining event records and preparing weekly notes interests me because I have practised both tasks in a college volunteering activity. I would like to contribute careful record handling while learning your organisation's actual procedures.
For twelve event sessions, I maintained a list of dates and facilitators using the schedule supplied by our coordinator. I compared the entries with that schedule and flagged two sessions whose facilitator names were missing. The coordinator supplied those names, and I updated the list. My contribution was the comparison, flagging and authorised update; I did not decide the facilitators or independently verify the entire event programme.
I also drafted a weekly status note from the supplied session information and submitted it for the coordinator's review. That experience gave me practice in keeping a draft separate from a reviewed record. Your role's stated record and weekly-note responsibilities are the basis for my interest. I would not present this volunteering activity as paid employment or as proof that I already know your internal systems.
Thank you for considering my application. I would welcome a discussion about how this experience relates to the role and what additional training your procedures require. My current contact details are in the accompanying application account and résumé.
Sincerely,
Kavya Rao
This is a drafted letter within the fictional exercise. No PDF has been exported, no application submitted and no reply received. The stated one-page limit still needs to be checked in the actual exported document; a Markdown example cannot prove its page count.
Inspect the structure against the record
The opening identifies the exact role and reference. It connects interest to two responsibilities actually supplied in the brief, rather than inventing a company product, award or mission. The body describes Kavya's owned actions and identifies who supplied and reviewed the information.
The closing offers a discussion without inventing availability, a contact address or a promise that Kavya already meets every qualification. It does not claim an invitation or selection decision. The generic hiring-team greeting reflects the absence of a named contact in this fictional brief.
The count of twelve sessions and two missing names comes from the supplied exercise record. It is not a result borrowed from a university sample. A real applicant should use only figures they can support and are entitled to discuss. If a figure is uncertain, omit false precision rather than adding an impressive number.
Choose layout decisions you can actually check
For the requested document, a proposed layout would keep the name, role reference and paragraphs readable, use consistent spacing and avoid unnecessary visual elements. The brief does not prescribe a font or margin measurement, so those choices are editorial presentation decisions, not employer rules.
After export, inspect the actual page rather than assuming that the editor view survived conversion. Check paragraph breaks, missing text, characters, page count and whether the contact and role reference remain legible. If the document exceeds one page, edit the content or layout without making it too small to read.
The requested 1 MB limit applies to the actual saved file. A filename or an editor's preview does not establish file size. Check the exported file's size before attaching it. No file-size measurement has been performed in this example.
Keep résumé and letter claims consistent
The résumé should describe the same activity as volunteering, with the same scope of contribution. A letter that says “I managed all programme operations” would go beyond maintaining the supplied list and drafting the note. A résumé that labels the activity as paid employment would also contradict this record.
Likewise, no certificate is supplied. Do not add a course title, completion status or software credential to make the application appear stronger. If the vacancy has an eligibility requirement, check the actual published requirement and your actual evidence separately. This format exercise does not establish Kavya's eligibility for a real role.
Consistency is about the underlying facts, not merely repeating keywords. You can phrase the same truthful experience differently in a narrative letter and a résumé bullet while preserving who acted, what was checked and what remained outside your authority.
Adapt to a text-field variant
Consider a separate fictional application that asks for a plain-text cover letter rather than a file. In that variant, the PDF upload instructions do not apply. Preserve the role reference, paragraphs and truthful content in the field, then inspect the actual field's preview and character limit.
If the field cannot retain line breaks or has a shorter limit, edit the wording deliberately. Do not assume that a successful paste means the complete text was saved. The exercise supplies no actual text-field submission or receipt, so the variant remains a proposed adaptation.
For a real portal, use the actual accepted channel. Do not attach an extra file or send a separate email merely because that was convenient in another application. Submission rules can differ across vacancies and across stages within the same organisation.
Distinguish preparation, upload and receipt
The prepared letter, exported document, selected attachment, completed upload and final submission are separate states. An attachment appearing in a local file picker does not confirm that it reached the employer. A portal acknowledgement can confirm the state it explicitly reports; it does not establish that the letter was evaluated favourably.
Before final submission, compare the actual requested fields and filenames with the application brief. Open the final file once more to check that it belongs to the intended employer and role. For a real account, use your verified contact information and inspect whatever receipt the system actually supplies.
For discussing truthful experience, see the STAR method guide. For recipient and attachment choices in a message, use digital communication etiquette. Those guides complement formatting without proving that a document has been submitted.
Frequently asked questions
Must a cover letter always be a PDF?
Follow the actual employer's instructions. The fictional brief here requests PDF; a text-field or different file-type brief would require a different submission.
Should I include a full street address?
Check the actual requested information. This brief does not request one, and the example does not invent an address.
Does a one-page letter guarantee ATS compatibility?
No. Page count and readability do not independently verify a system's parsing, acceptance or assessment outcome.