Organising project phases

There's no "best" format for the final round of testing. You could create a checklist in Word or Excel. That's really a matter of preference. 

Here's my post about what should be on that list for quality-assurance testing: TIP: Quality-assurance (QA) testing is a vital step | Articulate - Community 

Love this question Aïda_Domínguez​ — and I think this could be a great place to see a wide range of commenters since like JudyNollet​ mentioned this is probably something that every project does slightly differently. 

But, for me when I'm launching a new project in this vein I find it can be helpful to create a pretty prescriptive quality assurance form to make sure you're soliciting the right feedback. I find when I'm more open-ended about the feedback I'm looking for it may still be high quality, but it might not actually cover all the bases.

It can be more helpful to direct people on the steps you want them to take and have you tell them specifically about them—so for example, have them respond separately about things like typos or grammatical errors or broken links, vs things like "how engaging or helpful was this piece of content." 

Really curious to hear how others in this community approach quality assurance—gonna tag in some folks I think might have something interesting to say here: KellOrding​ CherylStGermain​ ChrisMcAllis074​ ErinParks​ PhoebeSterdan-0​ 

A lot of the e-learning I have been creating is derived from powerpoint decks that were developed internally by some of the leaders here. I have mainly been using those as the base - but then mapping them out in an order that lends itself better for e-learning. As it's all powerpoint, a lot of the content is getting updated to be more interactive and engaging, so I've taken a number of creative liberties. It then goes through a gauntlet of approvals and revisions. So TLDR - I don't have a proper system, I use the content given to me as the base and then adjust as I see fit.