Platinum Courseware OPS
Every rule checked. Every change reviewed. Every original untouched.
An editing platform for courseware teams. It checks a training module against your templates, style guide and house rules, lists every issue for an editor to decide on, and writes the approved fixes into a checked copy, with a full report of what was found and done. It supports your editors. It never replaces them.
What is courseware?
A professional training course usually comes as a pair of documents for each module. They’re written to strict house standards, and they have to agree with each other.
The instructor guide
The slide deck the trainer presents from, with speaker notes behind every slide.
The learner guide
The written handbook learners read during the course and keep afterwards.
Hundreds of pages, thousands of rules
Editing courseware by hand is slow, repetitive and hard to do the same way twice.
Big documents
A single module can run to hundreds of slides and pages.
Many standards
Templates, a writing style guide, terminology, trademarks and legal notices all apply at once.
Documents drift apart
Titles, objectives, summaries and graphics stop matching between the deck and the guide.
Inconsistent results
Two editors checking the same module rarely catch the same things.
Check, decide, deliver
Upload the module
Add the deck, the guide or both, enter the module details and pick a workflow.
Run the checks
Run one stage at a time, or every stage at once.
Decide on each issue
See each issue in context, with the corrected wording beside it, and choose what happens.
Get a checked copy
Approved fixes go into a new copy, tested before you download it, with a report of everything decided.
Nothing changes until an editor says so
The platform finds the issues. People make the decisions.
- Fix. Apply the suggested correction, where it’s safe to do so automatically.
- Manual. Leave it for the editor to handle by hand.
- Comment. Leave a note in the document for the author or reviewer.
- Remembered. Decisions carry over when checks are run again, and repeated issues are grouped so they’re decided once.
Nine stages, from setup to sign-off
Checks are grouped into stages. Each workflow switches on the ones it needs.
- SetupModule name, number, dates and other details are right and consistent.
- StructureSections, titles, activities, labs and learning checks are where the template expects.
- Pre-editTemplate version, layouts, footers, legal notice and proofing language.
- Content reviewOptional assisted review notes on the content itself.
- FormattingFonts, headings, bullets, numbering, tables, captions and note boxes.
- GraphicsScreenshots in the guide replaced with clean graphics from the matching slides.
- SynchronisationDeck and guide agree: titles, objectives, summaries, learning checks and labs.
- Style guideHouse writing style, terminology and first use of trademarks.
- FinalisationThe last pass before release, including the presenter’s notes pages.
Your standards, applied the same way every time
Rules your team owns
House rules are kept as editable settings, with search, approval of imported changes, and a log of every change with its before and after.
Rules from your template
Upload a master template and its rules are extracted for you to approve.
Add your own checks
Teams can create new checks and build their own workflows without writing code.
Learns from your editors
When an editor accepts a wording as correct, the platform remembers it for next time.
Deck and guide side by side
Titles and headings from both documents are shown together, so mismatches stand out at once.
See the real page
Preview the actual slide or page with the issue highlighted before you decide.
Changes you can see
Fixes to the guide arrive as tracked changes and comments, so reviewers see exactly what moved.
A report for every module
A pass/fail summary, outstanding issues and a timestamped log of every decision, in one shareable file.
Your files are protected at every step
Originals never modified
The file you upload is kept exactly as it was. All work happens on a copy.
Tested before you get it
Every fixed copy is opened and checked in the same desktop applications your team uses. If it doesn’t pass, it’s discarded and nothing changes.
Accounts and checkout
On the team edition, each person signs in, roles control what they can see, and a project is checked out to one editor at a time.
Desktop or team server
Run it on a single PC, or host it for the whole team on your own infrastructure. AI assistance is optional and off by default.
The benefits at a glance
Time saved
One run replaces many manual passes through every slide and page.
Consistent quality
Every editor applies the same standard, in the same way, every time.
Fewer mismatches
Differences between deck and guide are caught before learners see them.
Editors stay in control
Nothing is written into a document until an editor approves it.
Safe files
Every fixed copy is tested before it’s offered, and originals are never touched.
An audit trail for free
The report and the rule history are produced as a by-product of the work.
Built for courseware teams
Editors
Spend time on judgement, not on hunting for the same issues page after page.
Team leads
Set the standard once, share workflows, and see where every module stands.
Quality and compliance
Legal notices, trademarks and house rules checked on every module, with a record to prove it.
Production teams
Hand off modules that match the template, and each other, first time.
Bring consistency to every module
Talk to us about Platinum Courseware OPS for your courseware team.
