Two women discussing social media wall setup with tips on a whiteboard.
Photo by Walls.io on Pexels

Operations

Part of Social media training operations: a state-machine guide

A six-state social media training workflow, from intake to exit through synthetic practice

Run a social media training service in England through six recorded states: intake, independent approvals, synthetic practice, assessment, release and exit.

A six-state social media training workflow, from intake to exit through synthetic practice

Treat every course run as a sequence of permission checks, not as a calendar item. Each move depends on a named owner, a current artefact and a clear stop test; practice stays synthetic until release is approved. That keeps unfinished design, learner admission and access to a live account from becoming one decision.

How do I decide whether the next hand-off is safe?

Move forward only when the named owner supplies the required artefact and its stop test is clear. A delivery manager cannot waive a failed specialist decision to protect the timetable, and a completed slide deck alone does not authorise enrolment or access to a live social account.

StateOwnerRequired artefactStop condition
1. Intake and designService ownerIntake recordA blank field or unconfirmed status
2. Independent approvalSpecialist reviewersDecision for each gateA failed or expired gate
3. Build and practiceContent and platform ownersLocked version and script logReal data appears in practice
4. Assessment rehearsalAssessorsMarked synthetic submissionJudgement depends on an unpublished preference
5. ReleaseService ownerSigned release packA decision or learner register is missing
6. CloseService ownerReconciliation recordEnrolments or access remain unreconciled

Treat the table as the control sheet for a course run: each hand-off relies on its artefact and stop test. A restart or renewal needs current evidence, so an old approval cannot simply be copied into a new run. The broader operations and delivery routine can sit alongside these state checks.

What must I know before designing the course?

The service owner should confirm the learner group, workplace task and decision authority before design begins. If an intake field is blank or course status is uncertain, keep the service at intake instead of letting later decisions assume an answer that has not been confirmed.

Record the target audience, task, delivery period, course status, content version and decision authority. The record should identify the learner population and the work it needs to perform, rather than leaving later reviewers to infer those points from the course materials or the intended timetable.

List employees, contractors and external customers separately. Their working arrangements and the purposes for using their data may differ, so do not treat those groups as interchangeable when setting up intake. A missing distinction is a reason to pause and clarify the record, not a detail to fill in during delivery.

How should I describe the course and its certificate?

Describe the learning outcome and course status precisely, and make no recognition claim unless evidence supports it. The learning lead should turn the workplace task into observable objectives, synthetic practice and a versioned assessment before the course is offered to learners or buyers.

Qualifications, examinations and assessments in England are regulated. Check any claim that a certificate is regulated against the Register of Regulated Qualifications, which includes GCSE, A level, AS level and vocational qualifications in England and Northern Ireland. Keep intake open only once course status has been confirmed.

For example, a three-day complaints-handling course has eight learners, six employees and two contractors. Their task is replying to posts on the brand account. The intake record names the current locked version, marks the course as internal and unregulated, and identifies the service owner as decision authority; any blank field stops intake.

Who needs to clear the design before practice begins?

Use separate specialist decisions for privacy and PECR, accessibility and equality, security, commercial contracts, advertising and consumer claims, and employment and education status. Each topic needs an owner and a decision before the course run can move into its next state.

Send the same design pack to each reviewer. Ask each to record pass, fail or limited approval, with the supporting evidence, scope, expiry and condition for return. A failed or expired decision blocks the hand-off even if the timetable would otherwise allow the course to proceed.

For privacy, specify what personal information is needed before starting and use only what is necessary, following data protection by design and by default. Apply the separate learner data checks, and use the launch evidence review to check what the course must show before release.

Keep related review topics visible in their own decisions. Records may need to address reasonable adjustments, accessible communication, security, two-factor authentication, storage limitation, misleading advertising, consumer protection and regulated qualifications, alongside the evidence and scope for each relevant specialist gate.

What should a synthetic practice space allow?

Use a locked content version in a non-production area that cannot publish to a real audience. Learners should rehearse with invented brands and synthetic records, not customer or personal data, and the practice environment should have no route to live publication.

Give the practice workspace separate credentials and no publishing tokens. Ask the platform supplier whether two-factor authentication can be required for every user and whether privileged administrators can be separated from standard users. Save the supplier's answer with the build evidence rather than treating it as an informal assurance.

Test enrolment and removal, accessible navigation, practice posting, support, assessment submission, correction, incident reporting and export. The scripts should cover the tasks learners and operators need to complete before the course is released, including the steps for handling a correction or reporting an incident.

For every script, record the operator, date, version, expected result, actual result, evidence location, defect owner and retest decision. This makes it possible for another operator to check what happened and whether a defect was corrected, rather than relying on an undocumented impression that the exercise worked.

If practice fails, return the work to build. If real personal or customer data appears, stop the exercise and use the incident route. Rehearse the listed risk scenarios in the synthetic area so problems are found before live delivery.

How can I check whether assessment decisions are consistent?

Before admission, ask assessors to mark one common synthetic submission against the proposed rubric and resolve any material disagreement. This rehearsal tests whether the assessment can be applied consistently for the course run and its current content version.

A short private course does not become an apprenticeship, so apprenticeship assessment rules are a comparison only. Record pass conditions, adjustment routes, repeat attempts, moderation and evidence retention. Stop if the proposed judgement relies on a preference that has not been published in the agreed assessment approach.

What must be ready before learners are admitted?

The service owner should release the course only after signing a complete pack and admitting the approved learner population. If a required decision or eligible learner record is absent, hold enrolment; timetable pressure is not evidence for the release decision.

The signed pack contains current specialist decisions, synthetic results, the assessment rehearsal, eligible learner register, support contacts and rollback authority. Admit only the population covered by those materials. Approval does not automatically extend to another learner group or a different content version.

During delivery, log access failures, adjustments, support events, assessment attempts, corrections and incidents. A learner error may lead to feedback and another permitted attempt, while a flawed source, example or rubric sends the affected version back to design. Record training hours without overstating what they demonstrate.

What needs to happen when a course run ends?

At closure, reconcile enrolments, withdrawals, attempts and accepted evidence, remove access, apply the retention decision and confirm that exports can be read. The reconciliation record is the artefact for the final state, and the service should not be marked closed while any of those checks remains incomplete.

Agree return or deletion terms with the platform supplier before the course starts, not when access is being removed. At closure, check that exports are readable and apply the agreed retention decision to the records; include both outcomes in the reconciliation record.

Review the workflow after a serious defect, unauthorised release, platform change or failed rehearsal. A restart or renewal needs current evidence, and each approval remains tied to its stated scope, expiry and return condition before another release is considered.

What should I do first?

Start with the service owner's intake record and confirm the audience, task, course status and decision authority. These details determine whether design can proceed; do not build or enrol learners to fill gaps that should have stopped the first hand-off.

  • Record the learner population, workplace task, delivery period, course status, content version and decision authority.
  • Check any regulated-certificate claim against the Register of Regulated Qualifications.
  • Send the same design pack to separate owners for each specialist decision.
  • Lock the content version and test the non-production practice area.
  • Rehearse marking with a common synthetic submission before admission.
  • At closure, reconcile enrolments, withdrawals, attempts and accepted evidence.

More in Operations