Platform onboarding
Humans But Guided can run as the grading engine behind your own learning programs—not only as a tool individual professors sign up for on their own.
This guide is for platform partners: organizations that deliver education to schools, departments, or training networks and want consistent, AI-assisted grading across many instructors and institutions.
What HBG gives platform partners
Grading infrastructure under your brand — Universities and faculty interact with your program and identity. HBG powers scoring, feedback, and audit trails behind the scenes.
Faster time-to-feedback at scale — Professors spend less time on repetitive draft feedback and more time on judgment calls that matter.
Consistent quality across orgs — Manage prompts, course templates, and rollout patterns so every deployment starts from the same baseline instead of one-off setups.
Human judgment stays central — AI assists; professors and course assistants review and edit. Audits capture what changed and why—important when you're accountable to institutions for output quality.
Efficient reuse — A well-built course template or prompt library can roll out to new professors and sections with far less setup work than starting from scratch each term.
A path into the LMS — HBG supports deeper integration with learning systems (including Canvas via LTI), so students can submit work where they already learn when you're ready for that step.
How the partnership works
HBG is built for an embedded model: you own the institution relationship; we operate the grading platform.
| You (platform partner) | HBG |
|---|---|
| Distribution and commercial relationship with institutions | Grading engine, admin tools, and platform reliability |
| Professor and course onboarding at each site | Prompt infrastructure, org provisioning, and usage visibility |
| Quality review of AI output in your deployments | Engineering, product quality, and technical escalation |
| Grading philosophy and responsible AI positioning with your customers | Minimum quality standards and platform support |
Institutions pay for access through your program. You set customer-facing pricing and packaging. HBG earns a share of that revenue as your infrastructure provider.
That split lets you invest in implementation and QA—the work institutions feel directly—while HBG focuses on keeping the engine dependable as you grow course volume.
What you'll set up
Platform teams work in admin surfaces, not the day-to-day professor workspace:
Organizations — Provision the schools or departments that will run courses on HBG.
Prompt versioning — Control which analysis and feedback instructions are live, who can access them, and how updates roll out.
Course templates — Define assignment phase patterns at the platform level, then copy them into each organization so professors inherit a proven rollout structure.
Quality control — Monitor grading activity, review audits, and inspect usage to catch drift before it reaches students.
LTI connections — When an institution uses Canvas (or similar), connect platforms so assignments and submissions flow through familiar LMS workflows.
See Users → Platform for how this role relates to professors, assistants, and students.
A sensible way to start
Most platform partnerships begin with a pilot: a bounded set of courses and professors where you can validate adoption, workflow fit, and output quality before expanding.
A strong pilot answers practical questions:
- Do professors actually use the review workflow, or skip straight to publishing AI drafts?
- Does feedback quality meet the bar your institution partners expect?
- Can your team onboard a department without heroics every week?
- What does reusable setup look like when the same course runs again next term?
Treat the pilot as proof for your sales and success motion—not just a technical test. When you stand in front of the next institution, you should be speaking from observed results, not a slide deck alone.
Getting started
- Align on scope — Which institutions, courses, and timeline belong in the first deployment?
- Provision organizations — Create org structure and access so professors can sign in under your program.
- Stand up templates and prompts — Platform-level course templates and prompt versions become the defaults professors inherit.
- Onboard professors — Point instructors to Professor onboarding and support them through workspace, rubric, and grading setup.
- Establish QA cadence — Review sample evaluations with your team on a regular rhythm; escalate model or configuration issues to HBG.
- Measure and expand — Use usage and audit signals to decide when to add courses, orgs, or LMS integration.
Where professors fit in
Professors still own day-to-day teaching inside their workspace. Your job is to make their path repeatable: clear access, solid templates, and quality guardrails so each course doesn't reinvent the wheel.
When they're ready for detail, send them to the product guides—workspace, rubrics, grading, self-paced learning, and audits.