Read the internal vacancy as a set of responsibilities
Start by identifying what the new role is expected to do, not just its title or department. Mark the recurring responsibilities, decision areas, collaboration needs, and stated qualifications. Then distinguish requirements you can support with current-employer evidence from requirements that need a careful qualification. Internal readers may recognize the organization, but they still need to see how your experience relates to this vacancy. Avoid copying every phrase from the posting. Select the parts that determine whether your current work is relevant, and note any language that could reveal confidential information if repeated in the letter.
Gather verifiable evidence from your current role
Use career notes, approved records, project documentation, or your own work history to assemble evidence. Include responsibilities you actually held, deliverables you completed, systems you used, and collaboration you can describe without disclosing restricted information. For each item, write what you did, the setting, and the outcome only when the outcome is documented. Do not turn a temporary contribution into ownership of a whole program, and do not treat proximity to a project as participation in every decision. If a fact is incomplete, flag it for review rather than filling the gap with a plausible detail.
Choose connections instead of repeating your job history
Select the strongest evidence for the new role and explain the connection in plain language. A current responsibility may demonstrate a transferable practice without proving that you have already done the target job. For example, documenting a recurring process can support a claim about structured communication, but it does not automatically prove formal process ownership. Make your contribution visible by using precise verbs such as maintained, reviewed, coordinated, documented, or supported when those verbs are accurate. If the role involves a new system or decision level, name the related experience and state the boundary clearly.
Explain internal motivation without private assumptions
An internal application benefits from a specific reason for wanting the role, but that reason should come from your work interests, relevant experience, or the contribution you want to make. You can describe interest in improving a process, supporting a type of customer, or developing a capability named in the vacancy. Do not imply that you know confidential staffing plans, that a manager has endorsed your move, or that eligibility has already been confirmed. If your motivation includes a conversation, use only what you were authorized to repeat and make clear whether it was information or your own interpretation.
Address gaps with useful, factual wording
A missing requirement does not need to dominate the letter, but ignoring it can create an inaccurate impression. Identify what you have done that is related, what you have not yet done, and how the evidence supports your readiness to learn or contribute. Avoid promising a result you cannot guarantee. You might state that you have used a related tool, supported users of a process, or reviewed comparable information, while acknowledging that the target role requires a broader application. Keep the wording proportionate: one clear limitation followed by relevant evidence is more useful than a long explanation.
Review the letter for internal accuracy and privacy
Before sending, check every statement against your notes and the vacancy. Confirm that dates, responsibilities, ownership, systems, and outcomes are accurate. Remove details that are confidential, speculative, or unnecessary for the application. Read the letter as if you were a reviewer who knows the company but does not know your daily work: would the evidence and motivation still be clear? If you use Radaryno, its optional cover letter can be generated from your career notes in the offer language; the kit selects relevant experience, reports gaps, and asks rather than inventing. Files and generated documents stay on your computer, while AI provider access remains separate from the one-time kit purchase.
| Current evidence | Target responsibility | Useful connection | Avoid writing |
|---|---|---|---|
| Maintained an internal reporting workflow and documented changes | Own recurring operational reporting | Explain the workflow, your responsibility, and the relevant reporting habit | Claiming the new team already expects you to join |
| Coordinated a process update across two departments | Improve cross-functional processes | Describe the coordination and the change you verified | Saying senior leaders endorsed your move without evidence |
| Supported colleagues with a documented tool procedure | Help users adopt a shared system | Connect the procedure to user support and clear communication | Calling yourself the team expert without a factual basis |
| Reviewed recurring errors and proposed a correction | Improve quality or reduce rework | Describe the issue, your analysis, and the proposed action | Inventing a measured improvement that was never recorded |
Worked example: moving from evidence to motivation
Fictional example: An employee in the finance operations group applies for an internal process analyst vacancy. Their notes show that they maintained a monthly reconciliation guide, answered questions from regional colleagues, and documented recurring discrepancies. They begin by separating these facts from assumptions about the analyst team.
The employee then chooses the evidence that matches the vacancy. The reconciliation guide supports process documentation, colleague questions support clear communication, and discrepancy records support careful review. The letter does not claim that the employee has already performed formal process analysis if the notes do not show that work.
Next, the employee explains motivation through the work itself. They can say that improving repeatable processes and helping colleagues use them well is the type of contribution they want to make. They should not say that a private team need or an expected promotion caused the application unless that information is confirmed and appropriate to share.
Finally, the employee identifies a boundary honestly. If the vacancy asks for experience with a system they have only observed, the letter can state what they have used, name the related experience, and express interest in developing the missing capability. This is clearer than presenting adjacent experience as direct experience.