Identify the kind of archive and the work requested

An archivist cover letter should respond to the actual posting. A position centered on arranging and describing collections calls for different evidence from one focused on reference requests, digitization support, or records intake. Mark the two or three responsibilities you can substantiate, then choose one example that joins them. Do not assume every archive uses the same procedures or access rules.

Read the organization description for its collections and audiences, but do not claim a personal connection you cannot explain. If the posting calls for a particular system or standard, mention it only if you have used it in the relevant way. The letter is a place to connect your experience to their work, not to copy their requirements back to them.

  • Processing: what material did you arrange, describe, or prepare for use?
  • Access: who needed to find or consult it, and what part of that workflow did you handle?
  • Care: which handling, privacy, or review procedures shaped your work?

Open with the role and one defensible connection

In the opening, name the position and your closest relevant task. For example, if accurate: “I am applying for the archivist position. In my recent collections role, I drafted folder descriptions and checked them against existing inventories so staff could locate materials for reference requests.” Replace the task with your own work and the organization with the correct one; never present the sample as a completed project of yours.

If you worked on a team, make the boundary clear from the beginning. Drafting descriptions is not the same as approving a finding aid, and preparing a request is not the same as deciding whether restricted material can be released. Precise verbs make the letter more credible than an expansive claim about managing an entire archive.

Build the middle around a collection-to-access example

Choose one real piece of work and explain its sequence: what arrived or needed review, what you did, what you checked, and what became easier for an authorized user or colleague. For instance, a candidate who actually did the work might describe comparing folder labels with an inventory, flagging discrepancies for review, and updating approved descriptions. This shows how description supports discovery without promising a result you cannot verify.

Keep the level of detail appropriate for a letter. Your resume can list the collection, dates, tools, and scope; the letter can explain a judgment call, such as why you paused an unclear description and asked a supervisor before publishing it. If you know the size of the project, use a verified figure with its unit. Otherwise, a specific workflow is stronger than a fabricated number.

  • Weak: “I organized archives and improved access for everyone.”
  • Stronger, if true: “I reconciled folder titles against the inventory and flagged uncertain descriptions before the finding aid was reviewed.”
  • Ask: what did I personally do, and who made the final access or description decision?

Address sensitive material without revealing it

Collections can include private correspondence, donor conditions, or records with access limits. Show that you understand the boundary without identifying people or disclosing contents. You might describe following a documented review process, recording an unresolved restriction question, or referring a researcher request to the person authorized to decide. Avoid claiming independent authority over access if you did not have it.

Do not attach a sample inventory or finding aid from a workplace unless you have permission to share it. If the posting asks for a writing sample, choose a public, approved example or create a clearly labeled practice sample from nonconfidential material. A thoughtful sentence about handling choices is more useful than a vague claim that you always protect everything.

Translate adjacent experience accurately

If you are moving from a library, museum, records office, or graduate project, connect a transferable task to the posting without relabeling it as professional archival work. For example, a project that involved describing a small teaching collection can demonstrate careful naming and documentation, but it does not make you the custodian of an institution-wide archive. State the context and your role plainly.

Select one bridge, not an inventory of every class or tool. A researcher-facing role might benefit from an example of answering a source question and recording the handoff; a processing role might benefit from a description or quality-check example. Explain how you would apply that habit to the advertised task while remaining open to the archive’s procedures.

Close with the specific contribution and check the files

End with a concise sentence linking your example to the posted work and expressing interest in discussing it. Before sending, compare the letter with your resume: institution name, job title, collection terminology, dates, and your level of responsibility should agree. Remove an extra paragraph if it merely recites resume bullets rather than explaining how you worked.

CreateResume can help you edit a role-specific cover-letter draft, preview it, and prepare PDF-ready output. Open the exported letter and resume to inspect spacing, filenames, and contact details; then confirm that the correct version and any permitted sample are attached to this application.

  • Does the opening name the real position and a matching archival task?
  • Can you describe your contribution without exposing restricted material?
  • Do the letter, resume, and attachments agree on titles and permissions?