Software Training Video

Admin Portal Walkthrough

A two-part software training video that takes a brand new administrator from first sign-in to running the whole portal without help. Every screen explained, in the order you actually meet it.

Camtasia Two-part series Captioned and chaptered

Recorded and edited in Camtasia at 1080p. Both masters are large, so nothing downloads until you press play.

About the Series

The video that replaces the help desk ticket

Every software rollout hits the same wall. The build is finished, the client is pleased, and then the people who have to use the thing every day open it for the first time and nobody has shown them where anything is. What follows is weeks of the same four questions arriving by email.

This series was made to end that. It was produced for a community association portal, the kind of system where a volunteer board member with no technical background has to approve a resident, publish a notice and upload a budget without calling anyone. Two parts, and by the end of them an administrator can run the portal unaided.

What part one covers

  • Signing in for the first time and what the dashboard is telling you
  • Member records: finding a resident, editing details, approving a pending registration
  • The approvals queue and what each decision actually does
  • The document library, how categories work and who can see what
  • The events calendar, including how an event reaches the public website

What part two covers

  • Broadcasting a message to residents and choosing who receives it
  • Building and sending the newsletter
  • The photo gallery and the FAQ section
  • Keeping the portal and the public-facing site in sync, which is where most mistakes happen

Why a screen recording beats a written manual

A PDF manual describes an interface. A screen recording shows one. When an administrator can see the cursor move to the exact button, in the exact place, with the real data on screen, there is nothing left to interpret. That is the whole advantage, and it is why software training video remains the cheapest way to cut support volume after a launch.

The craft is in the restraint. Nothing is sped up through the parts that matter. Zoom-ins and callouts appear only where a control is genuinely easy to miss. Every word spoken is captioned, partly for accessibility and partly because a good share of people watch this sort of thing muted at their desk. Both parts are chaptered, so six months later somebody can jump straight to the two minutes about the document library instead of scrubbing through a quarter of an hour.

How we build these

We record against a real instance with realistic data, never a sanitised demo with three fake users, because the empty version is exactly the one that leaves people stuck. The script is written from the actual tasks the role performs rather than from the menu order, which is why part one follows a first day and part two follows a normal week.

The output is a plain MP4 that drops into any LMS, an intranet, a help centre or a welcome email. When the interface changes, the affected chapter gets re-recorded on its own instead of the entire series being redone. This sits inside our custom e-learning development services, and the same approach runs through the custom software projects we hand over. You can also see the portal itself in the Manage It Easy live demo.

Frequently asked

How long should a software training video be?
Short enough that nobody defers it, which usually means under fifteen minutes per part. The mistake is treating that as a word budget and talking faster. If the system genuinely needs half an hour of explanation, split it along the way the role works rather than compressing: this series runs as a first day and then a normal week, so an administrator can stop after part one and still be able to do something useful.
What software do you use to make training videos?
Camtasia for screen-recorded walkthroughs like this one, because the zoom, callout and captioning tools are built for exactly this job and the project file stays editable for years. Where a module needs the learner to click rather than watch, we build in Captivate or Storyline instead and publish it as SCORM or xAPI. The tool follows the task, not the other way round.
Can a software training video be used inside an LMS?
Yes. The deliverable is a standard MP4, which every LMS, intranet and help centre will accept, and it can equally sit in a welcome email or a shared drive. If you need completion tracking rather than just playback, the video is wrapped in a SCORM or xAPI package so the LMS records who finished it and when.
Do training videos need captions?
In practice, yes, and not mainly for the reason people expect. Captions are an accessibility requirement under WCAG, but the larger everyday audience is staff watching with the sound off at a desk or on a shop floor. An uncaptioned video is simply unusable for a sizeable share of the people it was made for.
What happens when the software changes after the video is made?
Only the affected chapter is re-recorded. That is why these are chaptered and why we keep the editable project file rather than handing over a flat export. A button moving in the document library should cost you two minutes of new footage, not a reshoot of the whole series.
Is a walkthrough video better than a written user manual?
For learning an interface, yes, because a manual describes a screen and a recording shows one. Written documentation still wins for reference: looking up one setting is faster in a searchable page than by scrubbing a video. Most rollouts we work on end up with both, and the video is what cuts the support tickets in the first fortnight.

Rolling out software to people who did not ask for it?

Tell us what the system does and who has to learn it. We come back within one business day with a realistic scope and timeline.