Ask about a record

Pick a candidate or school, then run a saved prompt or ask anything about them. For general questions across the whole mirror, use Chat.

School health check

Combines the reliable shift-volume trend with contact-log notes to flag at-risk schools and suggest remediation. Turn on note access in Settings for the qualitative read; without it you still get the volume signal and note counts.

Prompt library

Saved, reusable prompts. Fill in the details and Gully drafts it, grounded in your data. Pick a response mode for tone: precise, balanced, or creative.

How Gully defines things

Plain-English explanations of the terms Gully uses when it answers — what counts as an open shift, a regular, an available member, a genuine restriction, and which school-term calendar it follows. The term dates and the blanket-restriction list at the bottom can be edited; everything else is for reference.

Configure prompts

The admin library behind the prompts. Edit each prompt's spec (exactly what Gully should produce, which data points matter, the tone), its default mode, and which record types it applies to. Use Test on a prompt to try it on a real record and see exactly what's sent to the model — edits are tested live, before you save. Saved changes apply immediately across the Ask page and the Library.

Users

Who can use Gully and what they can see. Assign each person a role, their office scope and PII tier, set manager → consultant mappings, and enable or disable access. On Azure, people appear here on their first sign-in; locally you can add them by Entra object id to test. Changes apply on their next request and are written to the audit log.

Roles & permissions

Tick what each role can do. Changes take effect on each user's next request. Sensitive capabilities (marked ⚠) are admin powers — granting one is logged. The Admin role keeps a non-removable floor so you can never lock yourself out.

Sync the mirror

Pull fresh data from Entire into Gully's local mirror. A normal sync is incremental: members update in seconds, but availability, qualifications and expertise are fetched per member, so a full run can take 1 to 3 hours. It runs on the server, so it is safe to navigate away or close this tab once it has started. The same job also runs automatically each night.

Report data (CSV exports)

Restrictions, requests and contact logs aren't in the API — Gully pulls them from your saved Entire session. Paste your session below, then refresh. Takes a minute or two.
(Professionals and visa / work-rights are pulled manually for now — their report only exports an on-screen grid, so they can't be auto-pulled yet.)

Settings

Control which records Gully can return and how it behaves. Scope changes are enforced in the database (filtered views), not just suggested to the model.

Saved reports

Validated, reusable reports that run the same trusted SQL every time, with no model guesswork. Pick one to see its results, its caveats, and an optional written summary.

Work rights — visa 6-month cap

Working Holiday teachers (visa 417/462) and how long they have left at each school under the 6-month-with-one-employer rule. Most urgent first. Mark a teacher "acknowledged" (they have permission to work longer, you've actioned it, or they've left that school) to clear it without it disappearing. Decision-support for team leaders — not a compliance verdict.

Open blocks

Schools with a run of unfilled vacancies in the term (a "block"), and the proven regulars who can cover them. Blocks where no one is available are shown first — those are the gaps to chase. Pick the term/office and tune the matching below.

Review queue

Answers that errored, ran out of steps, or were flagged. Fix the SQL, save the correction, promote a good one to the golden set, or dismiss it. This is how Gully learns from real use.

History

Every question, the SQL Gully wrote, and the answer it gave.