White Tower
Project manifest

Discovery workshop

HANCA - Discovery Workshop

Head and Neck Cancer Australia

Thursday 29 October 2026, 3:00–4:00pm Sydney

Confirm the launch priorities, platform structure and learner experience.

Begin

Today, 3:00–4:00pm Sydney

Agenda

3:00–3:05Introductions and workshop purpose 3:05–3:12Business objectives, audiences and launch priorities 3:12–3:18Brand, presentation and reference examples 3:18–3:28Information architecture and platform structure 3:28–3:43Learner journey and functional rules 3:43–3:50Templates, modules and reporting 3:50–3:55Content, assets and supplier dependencies 3:55–4:00Decisions, actions and next steps

3:00–3:05 Introductions

Who is in the room

  • Roles on the HANCA side and on the White Tower side.
  • Decision and approval owners for content and the manifest.
  • What today needs to achieve: a validated draft manifest, not a finished specification.

Who will manage the platform day to day?

Who reviews content and approves the manifest?

We'll update the manifest and send it through for review.

3:05–3:12 Objectives

What the platform is for

  • Which courses are included in the first release?
  • Target learner groups and how they reach the platform.
  • Problems the platform should solve, in your words.
  • Success measures and a target launch window to aim for.

Which outcomes matter most for the first release?

What would tell you, six months in, that this is working?

3:12–3:18 Brand

Look, tone and references

  • The existing HANCA website is our visual reference. This is not a rebranding exercise.
  • Confirm the tone for healthcare-professional education.
  • Learning platforms you like, and what you like about them.
  • Accessibility needs, including contrast, readability and captions.
  • Brand assets: who owns logos, imagery and approved copy.
Open current HANCA website Opens in a new tab

3:18–3:28 Structure

Proposed structure for discussion

Where does the hand-off from the main website happen?

What should public visitors see versus signed-in learners?

Open the manifest to annotate structure Opens in a new tab

3:28–3:43 Learner journey

From registration to certificate

Which professional details are required at registration?

What can learners change themselves after registering?

What happens if a learner stops part-way and returns?

3:28–3:43 Completion rules

When is a course finished

What tells us the course is complete?

Which body, activity IDs and hours apply at launch?

What should sync to Salesforce on registration, enrolment and completion?

How do we handle existing contacts, or a learner using another email address?

Evaluation must not block certificates or CPD hours.
  • Vmation content delivery, LearnDash completion rules and Salesforce responsibilities each need an agreed owner.

3:43–3:50 Templates and reporting

What each screen must show

Templates

  • Course tiles and course detail pages.
  • Learner dashboard and profile.
  • Certificate layout and fields.
  • Which information is required on each, with examples you supply.

Reporting

  • Enrolment, progress and history reports for administrators.
  • Accreditation attendance export to Excel, from agreed fields.
  • Evaluation reporting, separate from completion records.
  • An export format to confirm with your accreditation body, not a direct system upload.

What information is required on each template, and who supplies examples?

3:50–3:55 Content and assets

What we need from you

Agree an owner and due date for each input.

  • Course packages from the content supplierOwner and date to confirm
  • Activity IDs and hours for launch coursesOwner and date to confirm
  • Certificate and export examplesOwner and date to confirm
  • Evaluation questionsOwner and date to confirm
  • Brand assets and approved copyOwner and date to confirm
  • Licences and platform access for nominated administratorsOwner and date to confirm

3:55–4:00 Next steps

Before we close

  • Read back the decisions made and the questions still open.
  • Assign an owner and date to every action.
  • Book supplier-specific technical follow-ups, including SCORM details and Salesforce mapping.
  • Agree the review and approval process for the updated manifest.
I will revise the manifest and send it through for review. You will have time to work through it after today.

Working documents

Where everything lives

Project manifest

The manifest is our working record for structure, workflows and responsibilities.

Open project manifest
Requirements registerNew tab HANCA websiteNew tab

Google Drive permissions are unchanged. Ask if you need access.