Build a first procedure mini-course, from blank editor to a checked lesson

Prepare four small pieces before opening the editor

Use the completed room-booking brief as a safe practice project. The fictional rule is simple: entering a request does not confirm a room; check overlap first; overlapping requests go to the room owner. Do not paste a confidential workplace procedure into an unfamiliar service to try these steps. This walkthrough follows published documentation, not a hands-on test of a paid account.

Save the title “Check before confirming a room,” the fictional source version, one normal case and one overlap case in your own working document. You should be able to explain the intended answer without looking at the authoring interface. If not, finish the lesson brief first.

Open the manual route and assemble the page pack

The documented dashboard route is Create mini course → Create from scratch. In the editor, Add Page or a plus control between pages opens the page menu. Content blocks can be added from the right-hand menu. Start with text; a decorative video is not needed to test this decision.

1. Rule: write the three-sentence fictional rule and label it as an example, not company policy.
2. Worked case: existing booking 10:00–11:00; complete new request 13:00–14:00. Explain that the intervals do not overlap, while other local prerequisites still matter.
3. Practice: change the request to 10:30–11:30. Ask what the coordinator should do next. Use the complete options from the scenario question.
4. Explanation: identify the 10:30–11:00 overlap and the room-owner route. Explain why a row in a list is not confirmation.

Keep the first version easy to inspect

Use a short heading per page and put each time interval on its own line. Check that an answer is not revealed by an image caption or by the wording of a navigation button. If a question requires a supported interactive page type, confirm the actual answer and feedback controls in your editor; do not assume an ordinary text block records a scored response.

An unscored text exercise is still useful for a facilitated discussion. Label it as such and use a separate answer key. It is a poor substitute when you need individual response records. This is a reason to choose the appropriate interaction, not to describe every lesson as a quiz.

Separate content release from settings changes

The August 2026 publishing help says courses begin as drafts. For an already-live course, draft or edited page content needs publication; settings and page order change immediately. Preview on a live course shows its released version. Check which state you are reviewing rather than treating every save as a learner-visible update.

Our practical release check is to compare the visible rule, case, options and explanation with the working document. Confirm the intended access boundary before sharing. Keep an incomplete exercise in draft; do not publish it merely to make a link work.

Know what a successful first build demonstrates

A readable course proves that you assembled a lesson, not that learners can perform the job. Ask a reviewer to explain the overlap without seeing the key, then inspect the ordinary and exception paths on a small screen. Record any ambiguity and revise the relevant page. A ten-minute review that catches an unsupported exception is more valuable than a polished animation.

Once the exercise is coherent, use the sharing decision guide to choose a direct link, embed or restricted route. Keep your source and answer key outside the merchant account too, so future maintenance does not depend on remembering why an option was written.