Content editor. Your handover

You are the staff member writing what students actually see. The weekly briefings, the student resources, the Ask Anything answers, the events copy, the help routes. Sometimes that's a dedicated content editor; often it's the platform owner wearing a second hat; occasionally it's a small editorial pool. Either way, this is your reference for the voice, the workflow, and the editorial guardrails.

What's already done for you

By the time you reach this page, First Six has:

• Built Write with AI into the composer. A Claude-backed drafting partner, on the button next to each block, to-do and event, that has your tenant's tone, brand, cohort, and week context in scope. It drafts; you decide.
• Set your institution's brand: logo, accent colour, sender email. The visuals are read-only in the console (an admin can edit the institution name and short name at Settings → Institution). They show up in every notification email and on every page automatically, so you don't have to lay them out.
• Built audience targeting into every block, todo, event, and resource item. The tagging vocabulary comes from your student-import data (programs, campuses, year levels) plus the student-group flags you've enabled.
• Shipped a starter set of briefing templates (where one exists for your institution profile) so you're not staring at a blank page.

Your editor surface

You have access to these areas of the console. The platform owner sees them too:

Drafting help isn't a destination: Write with AI sits on a button inside the composer, next to each block, to-do and event.

You do not see Settings, the Cohort settings page, the help inbox, individual student records, or Insights. Those are admin and responder surfaces. If you need a cohort created, a brand colour adjusted, or a new audience tag enabled, ask the platform owner.

The voice (this matters more than the mechanics)

First Six's voice is calm, plain, and short. The student reading your what-matters block at 11pm on a Sunday is anxious. They don't need cheerleading, and they don't need a wall of text. They need to know what matters this week and what one thing they should do about it.

A few rules of thumb:

• Don't pretend. If something is hard ("the first week feels overwhelming"), say so. Students trust the platform more when it acknowledges what they're feeling than when it papers over it.
• No exclamation marks in welfare-adjacent copy. Reserve them for events or wins. A welfare prompt with an exclamation mark reads as performative.
• One idea per block. If your what-matters block has three ideas, it has zero. Pick the one.
• Concrete, not aspirational. "Drop into the library between 2 and 4 on Tuesday" beats "make sure to seek support if you need it".
• Address the student directly. Second person, present tense. Avoid "students should". They don't think of themselves as "students" when they're reading at midnight.

The publish workflow

Every piece of content has a status: draft or published. Students only see published. The implication: you can draft as much as you want without affecting what's live.

Audience targeting (the part that catches people)

Every block, todo, event, and resource item carries an audience tag list. By default, content is shown to everyone in the cohort. The moment you add a tag, the content is only shown to students with that tag.

That cuts both ways:

• Good: show a tutoring drop-in only to first-in-family students who'd benefit; show a program-specific welcome only to that program.
• Bad: accidentally tag your "where to eat on campus" resource link with only the main-campus tag and lock out every regional-campus student.

Working with Write with AI

Write with AI is a Claude-backed drafting partner built into the composer. You don't navigate anywhere for it: each content kind has its own button, on a briefing block, a to-do and an event. It has the tenant's tone, brand colour, cohort, week, audience, and any tags you're targeting in scope when it drafts. So it won't suggest something that contradicts your brand voice unless you push it to.

It writes into the editor for you to approve. It never publishes, and it never sends anything to a student.

It can also get things wrong. It writes fluently whether or not it is correct, and it has no way to know your census date moved or that a service was renamed, so a wrong date reads exactly like a right one. Check every date, place, name, cost and deadline against something authoritative before you publish it to students. A draft you correct is still much faster than a blank page; the thing to avoid is skimming.

(There is a separate Admin assistant in the sidebar for institution admins. That one is for setup and administration, cohorts, audiences, integrations and team, rather than drafting, and it isn't part of your role. If you click it and land back on Home, that's why.)

Use it for:

• A starting draft of a what-matters block or top to-do.
• Rewriting your draft in three different tones to compare.
• Generating audience-specific variations (the same idea phrased for international students vs domestic).

Don't use it for:

• Final-pass copy that goes to students unread. Always read it.
• Anything in a help route, especially crisis routes. Those copy decisions are yours, not the model's.
• Welfare-sensitive language (mental health, crisis, distress). The assistant is trained to be helpful, not to navigate your institution's actual safeguarding policy.

When to ask for help

• Brand or tone questions: the platform owner. If the answer is "raise it with First Six", they'll do that.
• Audience tags missing: the platform owner (tags are generated from student imports; missing tags usually means the import didn't include the field).
• A help route doesn't have a destination: stop publishing. The platform owner needs to wire the actual on-call response. See Set up your safety net.
• Anything that feels like the platform misbehaving: support@firstsix.com.au.

Related