Military OS product walkthrough
Produced October 23, 2026, using synthetic local captures from October 23, 2026, fictional local training demonstration.

Training records, with association responsibility
Military OS keeps training and qualification records alongside the people an association serves. This demonstration uses fictional people and two sample training types, with no real provider or accreditation claim.
We will follow an association-run induction and an external first-aid certificate. Staff enter administration, then open Training and Qualifications. Only authorised people administrators can use these records.

Define what the association records
A definition is a reusable name and description. Chapter Officer Induction is training created by the association. Staff can record that a member completed it, using an association attendance or completion source.
Community First Aid Certificate is our fictional external qualification. Its name in this list does not make it verified or recognised. Recognition here means a separate decision to accept a person’s record for association use.

Record an association-run completion
Here, Alex Morgan completed the Chapter Officer Induction. Jordan chooses Alex, selects the training item, records the completion date and explains which association record confirms attendance.
Saving records a verified association completion, with Jordan identified as the recorder. It does not mean an external provider assessed Alex, and it does not automatically grant association acceptance.

Read the record before using it
The saved record separates three questions. Verification records what was checked. Date validity shows whether the issue and expiry dates are current. Association acceptance records whether the association has agreed to use it.
The completion source and verification history remain attached to Alex’s record. Expiry and revocation are also separate, so a past check does not guarantee that a qualification is still usable today.

Record an external qualification manually
For the second example, Jordan records Alex’s fictional first-aid certificate. The issuer is the organisation that awarded it. The evidence source says where staff obtained the supporting record.
Jordan chooses an issuer record, names the fictional provider’s learner record and adds its reference. These are manual entries. Selecting a provider portal or registry as a source does not connect Military OS to that service.

Save the dates and inspect the evidence
The issue and optional expiry dates are recorded next. After saving, the external qualification is unverified and not accepted. A recorded source is a starting point for review, rather than proof that a check has happened.
The evidence area is private to people administrators. Supporting documents can be added before review when private storage is configured. This example uses the recorded fictional source and staff notes, with no attached certificate.

Verify first, then make an association decision
Jordan records the fictional source check and saves a staff verification. The verification becomes verified, while association acceptance remains a separate decision.
Jordan then records why the association accepts this certificate for the sample volunteer role. That acceptance does not turn the association into an accrediting body or establish recognition by another organisation. The decision and review history stay on the record.

One register, two kinds of responsibility
The register now contains an association-run completion and a manually reviewed external qualification for Alex. Staff can see verification, acceptance and validity without treating them as the same thing.
Third-party training provider integrations are not available yet. They can be added in response to association requests, with the provider and required workflow agreed first. The screens shown here manage records and staff decisions; they do not deliver an online course or automatically check a provider.