Workv.Digital & systems

North Western Melbourne PHN information design and build for mental health services

I built the tools a busy mental health team runs on. An operations manual, a hand-coded staff wiki, training for new starters, and the models behind weekly reporting.

i.

The context

Primary Health Networks plan and commission health services for their region. In the mental health team, intake staff and clinicians work from procedures that span teams and systems, and when information is hard to find, everyone’s day gets slower.

I built the infrastructure that fixed that. The manual everyone works from, the wiki they search it in, the training that gets new people up to speed, and the models that make the weekly numbers reliable.

Role
Mental Health Communications Support Officer
When
April 2025 – July 2026
Teams
Intake and clinician teams
Built with
HTML, CSS and JavaScript, hand-coded · SharePoint · Excel · Power BI
ii.

What I built

  1. i.

    The Operations Manual

    104 pp.

    I built the Mental Health Operations Manual, a 104-page, 25,000+ word resource spanning clinical and intake workflows across teams. Complex procedures became navigable, task-based guidance that staff use for day-to-day reference and consistent service delivery.

  2. ii.

    Staff wiki

    Hand-coded · HTML · CSS · JS

    A branded internal wiki I designed, built from scratch and coded by hand, with clear navigation and full search, so intake and clinician teams find what they need in seconds.

  3. iii.

    Cheat sheets & training

    4.4K words

    Quick-reference cheat sheets and training material for new employees, 4,400 words that take someone from their first day to working confidently in the system.

  4. iv.

    Intake & tracking models

    Excel · SharePoint

    Models I built to improve data quality and power weekly performance reporting and stand-ups.

  5. v.

    Reporting & service resources

    Power BI

    Reporting improvements and the staff-facing service resources teams rely on, including provider mapping.

  6. vi.

    Staff training

    Delivery

    Training and development on the tools and digital workflows, with clearer channels, standards and handovers.

iii.

What carries over

This is where I learned to build information systems at scale, and every part of it is a production skill.

Web development

A working internal site, designed and coded by hand.

Information architecture

Deciding what goes where, so people find it without asking.

Content design

Plain-language, task-based writing for people under time pressure.

Systems & data

Tracking that makes the weekly report quick and reliable.

iv.

By the numbers

  • Built the 104-page Mental Health Operations Manual
  • Designed, built and hand-coded the staff wiki
  • Wrote the cheat sheets and training for new employees
  • Built the intake, tracking and reporting models
  • Mapped providers and trained staff

104

page operations manual I built

Delivered

25K+

words of task-based guidance

Delivered

4.4K

words of cheat sheets and training for new staff

Delivered

v. In short

Most producing happens before anyone sees the work, in making a complicated operation easy to run. Here I built that from the ground up, for a whole service.