Job Description

I’m supporting a client on a programme where a lot’s been built. A lot’s been delivered. But the documentation? It’s an ickle bit all over the place.

That’s where you come in.

This is a D365-led transformation that’s been running for a couple of years. They’re heading into end-to-end testing now, with go-lives lined up for later this year.

Plenty of artefacts exist… design docs, recordings, notes in DevOps… But no single, coherent view of how it all actually works.

Your mission if you choose to accept it (sorry, that was lazy) is to take everything that exists (and everything that lives in people’s heads) and turn it into something structured, usable, and built to last.

What you’ll be doing:

• Turning complex technical info into clear, structured documentation
• Pulling knowledge from architects, SMEs, and third parties
• Creating consistency across formats, language, and structure
• Filling in the gaps where documentation doesn’t really cut it
• Building a proper “single source of truth” for IT teams post go-live

Think less “note taker”… more translator, organiser, and finisher.

What my client need:

• Proven experience as a Technical Author in complex transformation programmes
• Comfortable working across D365 / ERP / integration-heavy environments
• Someone who can challenge, structure, and not just document what’s given
• Experience working with tools like Azure DevOps (or similar)
• Able to work with multiple stakeholders and get clarity from ambiguity

This is a 6-month contract paying £550–£600 per day (depending on experience), fully remote, and part of a genuinely interesting transformation programme with key milestones across the summer and Autumn.

Interested? Hit the link to apply in this advert or reach out for more information.