Writing a cover letter for an internal role

An internal letter has a different problem from an external one. The reader knows your work, so the letter cannot introduce you. It has to argue about the next job instead.

ConxfolioPublished 2026-09-12

— they know what you do. Tell them what you would do.

An internal application inverts the usual problem. Externally, the letter's job is to make a stranger interested enough to open the résumé. Internally, the reader already has an opinion about your work, formed over months, and the letter cannot change it by describing that work back to them.

So it has to be about the next job. What the role needs, what you would do in it, and which parts of your record are evidence for that rather than for the job you already hold.

What changes in the opening

Name the role and say you already work there, in one clause. It removes the puzzle immediately and it changes how everything underneath is read. What it should not do is spend a sentence on gratitude for the current position, which reads as a preface and delays the argument.

The reason paragraph also changes. Externally, the reason is why this employer. Internally, that question is already answered, so the reason becomes why this move: what you have seen from inside that made the role interesting, and what you would want to change in it.

What stays exactly the same

The proof paragraphs. Two to four things you did, each with a result. A panel that already knows the context still does not know the numbers, and an internal panel is the audience most able to check a figure, which is a reason to use real ones. Everything on what belongs in a letter applies here without modification.

The cover letter builder works the same way for an internal posting as an external one: paste the posting, connect your evidence, and the proof paragraphs come back selected from your own lines, each carrying the line it came from. Requirements the evidence cannot support are listed and not claimed, which matters more internally than anywhere else.

The first risk: claiming credit that has witnesses

An external reader cannot check whether you led the migration or contributed to it. An internal panel can, and often includes somebody who was in the room. The cost of an overstated claim is therefore much higher inside than outside, and it is not limited to this application.

The discipline that keeps this safe is the same one the engine applies. If you can point at the line of evidence, write it. If the honest sentence is "worked on" rather than "led", write that; a panel that knows the project will read the accurate version as confidence rather than modesty.

The second risk: writing about the department

Internal letters drift into diagnosis. The team has a problem, the process is broken, here is what is wrong. Some of that is the strongest material you have, because you can see things an external candidate cannot. All of it is dangerous in the letter, because it is read by people who own the thing you are describing.

The safe form is forwards and specific: what you would do in the role, expressed as an action rather than a criticism. "I would want to shorten the handover between support and engineering" says the same thing as a paragraph about a broken handover, and it puts you in the job rather than in the argument.

Where your history is already complicated

If you have held several roles at the same employer, the letter is the place to make the progression legible in one sentence, and the résumé is the place to lay it out properly. Listing multiple roles at one company covers the structure that keeps the dates readable, which matters because an internal panel will often attach your existing record to the application anyway.

Keep it short

Shorter than an external letter, not longer. You have less to introduce, so the same evidence takes fewer words. The check step reports the reading length of your draft against a guide of 140 to 420 words and calls it a guide rather than a rule, and an internal letter sitting at the lower end is doing nothing wrong.

Write it so Monday still works

The constraint nobody mentions: most internal applications are unsuccessful, and you will still be in the building afterwards. A letter built entirely on checkable evidence, with nothing said about anybody else, is a letter you can be shown six months later without discomfort. That is a lower bar than it sounds and most internal letters clear it easily, provided the diagnosis paragraph stays out.

Everything else about the document is ordinary. The four parts are the four parts, the header is the header, and the export is free in either PDF or DOCX.

What to do about the timing

Tell your manager before the panel does, unless the process is explicitly confidential. It is a courtesy with a practical edge: an internal process leaks, and finding out second is the version that damages a working relationship.

The letter itself should not mention the conversation. A panel reading that you have discussed the application with your manager has been given information about your department rather than about your candidacy, and it invites a question the letter cannot answer. Keep the document about the role and handle the relationship outside it, which is the same separation that keeps the diagnosis paragraph off the page.