Scribe naming standard

Format

[AUD]-[CAT]-[NNN]: Plain-language title

AUD — which Knowledge Base the guide feeds
CAT — which category within that KB
NNN — 3-digit sequence number, unique within that AUD-CAT pair, assigned in creation order (001, 002, 003…)
Plain-language title — phrased the way the reader would actually search for it, not how the process owner describes it internally

The code is for search, filtering, and admin tracking. It is never shown in the published, student- or staff-facing article title — only the plain-language part goes public.

AUD codes

Code	Meaning
`STU`	Feeds the Student knowledge base
`STF`	Feeds the Staff knowledge base
`BTH`	Near-identical process on both sides, captured once, published twice

CAT codes

Code	Category	Owner (current)
`JRN`	Student journey	CCO pre-census / COO post-census
`SAL`	Sales & Conversion	Sunny Grande
`ADM`	Admissions & Onboarding	Carol Nahal
`DIG`	Digital Channels	Hugo Venter
`CPO`	People & Culture	Shinu Simon
`FAC`	Facilities & Assets	Danial Robertson
`CAM`	Campus Operations (incl. student services)	Kylie Whitney
`ITS`	IT	Dave Schwarz
`FIN`	Finance	Henrik Ekstrom (interim) → Edward Loneragan, Nov

Codes attach to the category, never to the person holding it — ownership changes (like the Finance handover in November) don't force a rename of anything already captured.

Journey-stage tag (JRN only)

JRN guides also carry the journey step number in brackets, since that's the backbone the whole playbook is built on:

STU-JRN-014 [Step 09]: How to submit your assessment  Worked examples

STU-FIN-006: How to pay your tuition fees by instalment
STF-CPO-012: How to submit a parental leave request
STU-JRN-003 [Step 04]: How to enrol in your units
STF-FAC-021: How to book the AV room at Park St
BTH-ITS-002: How to reset your JMC password

Scribe folder structure

Mirror the AUD-CAT pairs as Scribe Groups/folders — 12 folders total (3 Student-only: STU-FAC, STU-FIN, STU-ITS; STU-JRN; 4 Staff-only: STF-FAC, STF-FIN, STF-ITS, STF-CAM; STF-CPO; plus STU-SAL, STU-ADM, STU-DIG for the pre-census journey categories, and a shared BTH folder for dual-audience guides). Each of the 8 owners saves into their own folder(s) — this keeps the code and the folder location redundant on purpose, so a miscoded title still lands in the right place.

Rules

Codes are uppercase, hyphen-separated, no spaces.
Sequence numbers are never reused, even if a guide is retired — an archived STU-FIN-004 stays retired rather than being reassigned.
Retiring a guide: move it to an ARCHIVE folder and append (superseded DD-MM-YYYY) to the title. Don't delete outright — Service Hub tickets may still reference the old code.
Updates to an existing process are edited in place in the same guide, not renamed or re-numbered.
Plain-language titles start with "How to…" for task guides, or a plain question for reference guides — match how the reader would phrase the search, not how the owner describes the process internally.

Scribe naming standard

One consistent code per guide, across all 8 documenting areas, so guides can be searched, filtered, and traced back to the right Knowledge Base category without relying on memory or folder location alone.