Job search
Interfolio Dossier Recommendations: Request, Reuse, and Attach the Right Confidential Letter
Choose the right confidential recommendation, distinguish Dossier and application requests, and verify receipt, attachment and application submission separately.
An Interfolio letter can be safely stored in Dossier without being attached to the application you intend to submit. First identify where the request began, then match the received letter to the correct application requirement. For a confidential recommendation, use its available metadata and status; you cannot read the contents yourself to check which version it is.
This guide uses Interfolio's public request-management, email-correction and delivery documentation, checked October 14, 2026. We inspected public help pages and the plan comparison, without signing into an applicant account, requesting a letter or making a delivery. The worked records below are fictional examples, not reports of a real applicant's results.
LandOffer.ai publishes this guide. If you are organizing several opportunities, browse jobs posted in the last 24 hours, then keep each application's letter requirements with its own deadline and submission record. Before reusing a recommendation, check that its intended purpose fits the destination's instructions.

Check whether the request began in Dossier or in the application
Interfolio's request-management guide distinguishes two routes. A letter requested within an application is attached there and stored in Dossier after the writer uploads it. A letter requested from personal Dossier is stored in Materials; you must attach it to the intended application separately.
Before requesting another letter, check whether the existing request belongs to this application or only to personal Dossier. Your personal note can say “requested for application R52” or “requested for general Dossier storage.” Keep that description separate from whether the writer has responded.
A request email is evidence of a request, not the finished letter. A document in your materials is evidence of storage, not proof that every application needing it has the right attachment. Work through the particular destination rather than assuming that a single action updated all opportunities in your account.
Start inside the application whose requirement you are trying to satisfy. Read its requested number, letter type, any named subject matter and the relevant deadline. If the posting asks only for referee details at this stage, follow that instruction instead of assuming that collecting a completed letter is immediately required.
Choose an existing letter by purpose, writer and available details
A general letter may be reusable, while a letter prepared for one opportunity may need reconsideration before reuse. Interfolio's Dossier best-practices article recommends discussing that distinction and the actual letter requirements with the writer. Do this before the deadline becomes a reason to select an uncertain document.
Consider Nora, a fictional applicant preparing R52, a fictional university software-research position. In this example, the application requires two confidential recommendations. Nora has two older documents available, but their titles describe different purposes. She has not read either confidential letter.
Her completed selection record is:
| Available item | What Nora can establish in this example | Selection decision |
|---|---|---|
| Desai — general recommendation — 2026 | Writer identity, document title and receipt date; Desai separately confirms general reuse is appropriate | Select this existing letter for the R52 requirement and check the resulting attachment |
| Huang — fellowship recommendation — 2025 | Title identifies a different purpose; suitability for R52 is unresolved | Ask Huang about an updated R52 recommendation instead of assuming the stored version fits |
| R52 instructions | Two confidential letters required in this fictional application | Track two individual requirements; do not turn this count into a rule for other positions |

The writer's confirmation in the first row is an assumption within the teaching example. It is not something we obtained from a real recommender. Nor does the title establish the letter's strength, tone, detailed contents or whether an employer will value it.
The unresolved item is Huang's letter choice. “I have a letter from Huang” answers a different question from “this is the recommendation Huang intended for R52.” If the distinction cannot be resolved from permitted details and a conversation with the writer, keep the selection pending rather than guessing from the newest filename.
Prepare a new request without asking to inspect confidential content
For Huang's new request, Nora prepares a short brief: the opportunity reference, relevant work they did together, the requested emphasis, the institution's instructions and the actual deadline. Her message can explain why a general or position-specific recommendation would be useful without drafting praise on the writer's behalf.
An original title convention such as “Huang — R52 research role — 2026” makes the intended purpose easier for Nora to recognize later. It is a personal organizational choice, not a required Interfolio naming format. If a proxy is uploading for a writer, follow the platform's instructions for identifying the recipient and the actual recommender rather than substituting one name indiscriminately.
Princeton's confidential-letter guidance describes applicant access to status, rather than letter content. Interfolio's own request guide likewise separates attachment access from access to confidential contents. Do not treat an unavailable preview as a reason to ask the writer to send you the confidential file for manual uploading.
A suitable draft request could read:
I am preparing application R52 for a software-research role. Would you be comfortable providing a confidential recommendation based on our research collaboration? The posting asks for discussion of research contributions and teamwork. I can provide my current CV and the opportunity instructions. Please let me know whether the earlier fellowship letter is suitable or whether you would prefer a new request for this role.
This fictional message asks about suitability before assuming it. Replace its facts with your own and agree on the request with the writer. Sharing the relevant background is useful; inventing a project, contribution or relationship to make the request more persuasive is not.
Keep the letter status separate from the application requirement
Interfolio describes Requested, Pending and Completed as request sent, accepted but not uploaded, and uploaded, respectively. Read the label beside the specific request and its details; similar words elsewhere may describe the application instead. None of those labels alone establishes that the entire application has been submitted or that a selection committee has accepted the packet.
Nora's second completed record combines route and status. Every entry below is a hypothetical snapshot, not an authenticated screen observation:
| Item and route | Assumed state in this example | Next action |
|---|---|---|
| Desai's general letter, requested from personal Dossier | Received and available in Materials, but not yet attached to R52 | Add the selected existing letter to the R52 requirement and verify that specific item |
| Huang's new letter, requested from inside R52 | Pending; writer has not uploaded it | Follow up appropriately; do not mark the letter received |
| Huang's same request after a later upload | Completed, with the application-origin association expected | Check that the R52 requirement now shows the intended letter |
| R52 application as a whole | Final submission not yet confirmed | Review all remaining requirements and the application's own submission state |
The last row prevents a common bookkeeping mistake. Checking off a letter task can be reasonable while the application remains unfinished. Maintain separate notes for the writer's response, the document's availability, the destination requirement and final submission.
For an existing document, verify the selected writer and version before moving on. If two similarly titled letters exist, a vague note such as “recommendation attached” is insufficient for your own review. Record the distinguishing title and date privately, without copying confidential content or unnecessary personal details into a shared spreadsheet.
Correct a writer's email through the existing request's process
An address error requires attention to both the saved contact and the already-sent request. Interfolio's email-change instructions prescribe canceling the old request, correcting the contact and sending a new request. Merely editing a contact does not rewrite the earlier request.
Suppose Nora notices that Huang's request went to an obsolete address before any letter was uploaded. Her correction record should distinguish the old request from its replacement. Confirm the correct address with Huang, follow the documented process for the affected request, and note which new request is current.
Do not label the replacement “completed” simply because its address is correct. The correction fixes the intended recipient; it does not establish that the recipient received, accepted or fulfilled it. A separate response or status change is still needed for each of those observations.
If the case already includes an uploaded letter, an active application deadline or an unclear request status, ask Interfolio support about that specific record before using cancellation as an experiment. Correcting an unfulfilled request is a different task from removing a stored recommendation. Keep the request date and application reference privately so support can distinguish the affected request from a stored letter.
Check missing requests and archived materials before starting over
Interfolio's missing-request help advises checking the writer's spam folder and confirming the address. A correct-address request can be resent through the proper route. The help also offers a writer-to-support option for supplying a confidential letter; the writer, rather than the applicant, sends that content to Interfolio.
Keep the conversation narrow: which request, which confirmed address, and whether the writer received it. Avoid sending several replacements while neither person knows which request is current. A successful resend is not evidence that the document has arrived, so return to the letter's status after the writer responds.
For a letter you previously received, check whether it is archived before asking for a new upload. Interfolio's best-practices article explains that archiving removes materials from the active list and that they can be restored. An absent item in the first active list you inspect therefore needs further investigation before you conclude that the writer's work has disappeared.
When contacting support, describe the document title, writer, approximate request or receipt date, application reference and the specific mismatch you see. Keep account credentials, private upload links and the letter itself out of a public troubleshooting post. No real request needs to be exposed for someone to explain the documented distinction between storage and attachment.
Review the destination's rules and delivery route before submitting
A due date in a recommendation request is a reminder, according to Interfolio's Dossier FAQ; it does not prevent a later upload. That technical capability does not extend the institution's deadline or guarantee that a late letter will be considered. Confirm the destination's rule when timing is uncertain.
Likewise, an institution may collect recommendations at different stages. Princeton's institutional guide describes both upfront and later requests. Its examples illustrate why a reference-contact requirement and a completed-letter requirement should be read separately. They do not determine another institution's policy.
Check the delivery route before paying for anything. Interfolio's plan comparison includes free letter requests and applications to Interfolio-hosted positions, with Dossier Deliver as a separate offering. A paid upgrade should not be assumed necessary merely because a confidential letter is involved.
For an external application, follow its accepted method. Interfolio's delivery-types guide describes document-specific email addresses for certain confidential uploads and explains that the external system's request still has to be triggered. It also identifies limitations where writer-specific questions prevent the service from completing the upload. Do not substitute that external-delivery workflow for attaching a letter inside an Interfolio application.
Finish with one concrete next action per letter
Before leaving the application, account for each required recommendation: the intended writer and purpose, what has actually been received, whether the correct item is attached, and any outstanding action. Then check the application's overall state independently. An unresolved letter can remain on your follow-up list without being mislabeled as lost, complete or submitted.
If you are continuing other applications, check recently posted jobs on LandOffer.ai. Keep this packet's next action specific: confirm reuse with a writer, correct one request, attach one received letter or resolve a destination's timing rule. Record the unresolved task and follow up on that item without asking to inspect confidential content.
Sources and Further Reading
- Interfolio: send and manage recommendation requests — request origin, confidentiality and letter statuses.
- Interfolio: update a writer's email after sending a request — correction process for an existing request.
- Interfolio: troubleshoot a request the writer has not received — address checks, resend and writer-to-support route.
- Interfolio: Dossier best practices — general versus specific requests and archived materials.
- Interfolio: Dossier FAQ and plan comparison — reminder dates and the free versus delivery-service boundary.
- Princeton: letters of recommendation — institution-specific collection models.
- Interfolio: delivery types — external delivery methods and limitations.


