Find your way around, understand what is needed and keep your programme moving.
19 answers
Your administrator must give your email address access first. Open Course Designer, enter that address and choose Send email code. Enter the code from the latest email and select Verify email code. No password or authenticator setup is required. Check spam if the email is missing; ask your coordinator if you cannot access the assigned workspace.
Link to this answerIt is optional. In Account security, choose Set up authenticator only if you want to enable it. Add Course Designer in your authenticator app by scanning the QR code or entering the setup key, then enter the six-digit code and choose Verify authenticator. Before setup is completed, Continue without setting up or Cancel setup lets you leave. An incorrect setup code does not block email-only access. Once enabled, the authenticator code is required after email verification on later sign-ins. If you lose an enabled authenticator, contact your administrator for account recovery. Email codes and authenticator codes are different.
Link to this answerFollow Brief → Programme plan → Lesson content → Materials → Review and release. Agree the audience, objectives and teaching sources; plan modules and lessons; develop lesson content; create the required files; then complete human review and release. The guide recommends the next step from the current saved version and your access. Being on a later page does not mean earlier requirements are complete.
Link to this answerOwners manage the workspace and team. Owners and Editors author programmes and teaching content. Reviewers and Owners perform permitted reviews; assigned stages and the organisation's approval policy may restrict decisions further. Viewers inspect work without editing. A reviewer assignment does not by itself give authoring access. If the intended task is unavailable, ask your workspace Owner to check your role and assignment. The guide cannot grant access or approve work.
Link to this answerIn Programmes, select New programme. Enter a recognisable test name, choose Start with a role or Start with existing teaching content, select Organisation standards and Material language, then Create programme. Use your assigned test workspace and agreed standards. The Brief also supports starting with a programme brief. Start with one module and two short lessons for a small test.
Link to this answerDescribe the audience, programme purpose and language. Choose the relevant framework role or teaching content. Select the actual reviewed passages to use, then write objectives or select Suggest learning objectives. Inspect the proposal, use suitable suggestions with Use this proposal, and confirm objectives and capability alignment where prompted. Use selected teaching content is the source-based route. Create learning content with AI from this brief is a separate route requiring an explicit creation instruction and human accuracy review.
Link to this answerUploading a file does not complete its reading and classification review. In Teaching content, open the source, inspect its original pages and extracted passages, correct reading errors, complete classification and resolve the review requirements before making the edition available. Sources selected in a programme are tied to a saved edition and specific passages. Ask a source editor to resolve pending review; do not treat an unreviewed upload as validated evidence.
Link to this answerNo. A teaching source can be a complete course, but its module names, lesson sequence, objectives and timings describe that source. They remain useful for navigation and citations. Define this programme’s own modules and lessons from its audience, objectives, duration and depth. Combine or split relevant source passages as needed. A separately attached programme-brief reference can guide design only after you explicitly agree to use selected passages, and proposed details still need separate acceptance. In Programme plan, unassigned lessons are shown without an invented module. Use Separate imported source headings from the lesson plan to preserve untouched imported headings as source references. Authored lessons are protected. Materials, the outline and the guide use the programme’s active plan.
Link to this answerIn Programme plan, complete Time and approach, Module structure and Lesson plans. Check objective coverage and that lesson timings fit the programme duration. Work through Before you develop the lessons, following each action to its location. When the substantive checks are resolved, an Owner or Editor can select Confirm learning plan. A changed plan can need fresh confirmation.
Link to this answerConfirm the learning plan first. In Lesson content, choose a lesson under Work on a lesson. Use Write lesson content for manual authoring or Draft this lesson for an AI proposal; you can focus on an explanation, practice or assessment section. Read and refine the content, evidence, answers and facilitator guidance. Use this proposal accepts suitable AI work. A stale proposal needs to be refreshed before it can be applied.
Link to this answerIn Materials, choose the required output and included lessons, review the options and prepare its content. Drafting depends on a confirmed plan and content for the selected lesson. Inspect the preview, then create the editable PPTX or DOCX where offered. Create a PDF from the saved editable file when available. Under Files for this material, download and open the actual file. Check its language, scope, saved version and formatting. Missing files for the current version must be created again.
Link to this answerCheck Preview and download audience before creating assessment outputs. Participant materials should exclude answer keys and facilitator-only notes. Facilitator and internal instructional/review packages can contain answers. Download and inspect the actual participant files before sharing them. Editing shared lesson content can affect several outputs, so recheck affected materials.
Link to this answerOpen Review work for assigned programmes or Review and release within a programme. Checks and evidence holds evidence decisions; Changes to address holds findings; Reviewers and stages holds assignments and stage decisions; Files and release holds outputs and production approval; Version history holds saved editions. Instructional approval, production approval and release are separate human decisions. Follow the organisation's assignment, sequence and independence rules. AI advice never approves or releases a programme.
Link to this answerProgramme editing shows Saving…, Changes waiting to save or All changes saved. Wait for All changes saved; use Save now if offered. Reopen the programme to check persistence. If a newer version or conflict is reported, retain your changes and follow the recovery instructions; do not assume a stale write succeeded. The guide uses saved progress and asks you to save first when changes are pending. Other editors may have explicit save controls.
Link to this answerFor content generation, read the job's progress message; you can leave and return to its proposal. Review a failed job's message before retrying. Manual authoring remains available. Ask the guide answers app-operation questions and links to Help; it does not change programme content. If guide AI is slow, unavailable or at its usage limit, use the page checklist and Help articles. Ask the guide again after your page or progress changes.
Link to this answerProgramme standards define learning requirements, branding, available materials and review responsibilities. Organisation resources hold policies, templates and reference files. Subjects & topics organises teaching content. Roles & skills helps you explore career roles, required capabilities and proficiency levels. Owners and Editors can edit permitted setup records; publishing standards and managing team access have separate permissions. Technical configuration and diagnostic records are in Technical tools → Technical audit.
Link to this answerOpen Technical tools in the sidebar, then Technical audit. File-processing history shows completed work and detailed errors. Source diagnostics keeps reading warnings. Framework imports & comparisons contains source mappings, reference tables and edition differences. Templates & fonts configures production templates for a chosen standards set. Programme diagnostics contains requirement references and processing records. Owners also have Domains & hosting. You do not need these tools to follow the everyday programme workflow. Editors and Owners can make permitted configuration changes; other roles can inspect the available records. Important reading checks and review decisions remain on the relevant source or programme page.
Link to this answerSend your test coordinator the task and page, your role, test programme, what you expected, what happened and the exact message. State whether the result remained after reopening. Add a screenshot or downloaded example where useful, excluding credentials and private content. Mark Passed, Blocked, Failed or Not tested, and separately whether the task was easy or hard to find. Help does not automatically submit feedback; use the destination supplied by your coordinator.
Link to this answerOpen Ask the guide from your workspace. It uses the selected page, lesson or material, your verified workspace role and the saved programme's readiness, approvals and files. Ask What can I do here?, How do I do it? or What should I do next? Navigation buttons lead to registered app pages; Help links open the relevant FAQ in a separate tab so your work stays open. The guide cannot edit, approve or release work. Conversations stay in the current page session and reset when the working context changes; the app stores limited usage metadata, not the conversation. Your questions are sent to the configured AI service, so leave out passwords, codes and unrelated personal information.
Link to this answer