How do you manage course maintenance and life cycles

From a Course Package Company (think: Skillsoft)

1. Who's responsible?

Our product managers, ultimately, were responsible. Even if they didn't assign the "expiration" or "revision" date for each course, they designated how it should be assigned. For example, many of our courses were medical, so it was based on different accrediting bodies.

We used a database system called Quickbase to store these dates, and we had reports that would spit out what was coming up for expiration. Product managers would then decide what to do with each course on a case by case basis. Sometimes it was just letting it go through our "standard revision cycle" which was pushing it out to a SME to look over, make any minor changes, and so on.

2. How often?

At minimum, that company set every 4 years courses would get reviewed. Some required yearly maintenance. It entirely depended on whether or not there were any accreditation on it that dictated the length of time it could exist without a review, or if new laws/mandates came out and courses were affected.

3. What's included?

There were several different types of updates. Some were "minor changes" where we needed to update a few sentences here and there, some were "major changes" where over 50% of the course needed to be updated. We would include them into our cycles based on the length of time something took to do. Occasionally, a course was completely replaced by a new course because the old course had such outdated information.

I just joined a new company and I'm discovering how they go through it so if it's compelling, I'll include that too :)