Scholiad helps your graduate students, postdocs, and researchers find opportunities and prepare application materials. The AI advisor features are configurable per institutional contract — including disabled entirely, if that's what your policy requires.
Three things, in plain terms — sized for procurement evaluation rather than student onboarding. Each is enforced at the application layer, not the marketing copy.
Scholiad aggregates a curated humanities and social-sciences source catalog — jobs, fellowships, funding, and calls for papers. Your students and researchers spend less time hunting across professional society sites, foundation pages, and university registries, and more time on their materials.
AI advisor features review student-authored drafts — they don't ghostwrite. Every interaction preserves an audit trail: the original draft and the AI's feedback, plus the student's revised version when they submit it. Positioned alongside writing-center feedback, not AI generation.
If your academic-integrity policy treats AI-assisted writing review differently, you can disable the AI advisor features for every student account under your license. The matching catalog stays; the AI features gate off.
§ IIISome institutional academic-integrity policies treat AI-assisted writing review differently than peer review or writing-center feedback. Scholiad respects those policy decisions — the configuration is yours.
Scholiad's AI advisor features — CV gap analysis, CV tailoring suggestions, cover-letter feedback, research-statement review, portfolio coherence audit, and venue discovery among them — are architecturally separable from the core job-matching catalog. Institutional contracts include a per-institution toggle that disables AI advisor features for every student account provisioned under the institution's seat license.
When AI advisor features are disabled, students retain full access to the matching catalog, posting alerts, saved searches, and application tracking. Only the AI advisor features gate off. This is enforced at the application layer (a config flag on the institution record; downstream UI gates consume it; test coverage enforces the gating) — not the marketing layer.
The relevant institutional comparison is not AI-assisted review versus none. Researchers who want AI feedback on job materials can find it off-platform, where the institution has no visibility. When AI advisor features are enabled under an institutional contract, that use is observable, bounded to source-cited feedback on the researcher's own draft, and fully audit-trailed. Disabling the features via the per-institution toggle removes that institutional visibility — it does not remove a researcher's access to general-purpose AI elsewhere.
The six items procurement and counsel typically ask about, with the architectural posture for each. Full detail and contract language live on the Partnerships page.
Every AI interaction writes an immutable row: the original draft and the AI's feedback, plus the student's revised version when they submit it. No deletions; revisions append. An institution-facing export of these records across a seat license is available as a contract deliverable.
A single flag on the institution record disables all eight AI advisor features for every account under your license. Downstream UI gates consume the flag; test coverage enforces the gating.
Before a document is sent to an AI provider, identifying contact details — email, phone, postal code, and links — and the account holder's surname are removed; the first name is kept so feedback stays personal. The user's stored document is never altered: it keeps its full text and is theirs. Scholiad does not use user documents to train AI models, and it contracts only with AI providers whose terms prohibit training on the content it sends. The AI runs only on the user's request.
Architectural commitments — including AI gating, INSERT-only ledger, and no-ghostwriting — are enforced by a continuously-run test suite, not by policy alone. Audit report available under NDA.
Institutional configurations are set at contract time by the Scholiad team. Roster and roster-revocation changes are handled directly by the team from Day 1, at no additional charge.
AI advisor calls run through a cross-vendor adapter layer. The AI provider is a configuration setting, not a hard-coded dependency — it can be changed without a code deploy, and Scholiad is not locked to any single AI vendor.
Four steps. Step three is conditional on AI advisor features being enabled under your contract — when they aren't, students proceed straight from step two to step four.
Students sign up with their academic email; the institution's license provisions their account against the seat allocation.
Day 1They search the aggregated catalog, save opportunities, and set alerts on disciplines, deadlines, and posting types. Filter UI grouped by field, stage, and funding type.
Always availableThey upload student-authored drafts. The AI advisor returns structural feedback — coherence checks, posting-fit signals, and missing-element flags. The audit trail preserves the process.
If AI advisor enabledThey assemble and export their application materials, track applications across the cycle, and archive placement outcomes for departmental reporting on the Alumni retention tier.
All tiersInstitutional buyers respect candor more than they respect marketing. Here is what Scholiad explicitly does not do, so you can evaluate it without surprises.
Scholiad does not guarantee or predict hiring outcomes. Match scores measure profile-posting alignment, not selection probability. Hiring is pool-, committee-, and field-determined; we surface opportunities, we don't pick winners.
Every AI advisor feature requires a student-authored draft as input. The AI returns feedback — coherence checks, structural notes, missing-element flags — but does not generate cover letters, research statements, or CVs on the student's behalf.
Scholiad complements institutional advising — DGS conversations, writing-center work, faculty mentorship. It doesn't replace any of them. Use it as a discovery and structural-review layer alongside the relationships students already have.
The institutional partnership program opens with a deliberately selective founding cohort for humanities-strong departments — chosen for depth of coverage and fit, not breadth of logos. The Founding Partner program is built for institutions that want to evaluate and help shape coverage before committing to a full license.
Before a document is sent to an AI provider, identifying contact details — email, phone, postal code, and links — and the account holder's surname are removed; the first name is kept so feedback stays personal. The user's stored document is never altered — it keeps its full text and remains theirs. The AI runs only on the user's request, and Scholiad does not use user documents to train AI models, and it contracts only with AI providers whose terms prohibit training on the content it sends. Feedback features do send the document's substance (with the contact block and surname removed) to a provider; we don't claim nothing is sent — we claim it's minimized, name-reduced, and audited. See the Privacy Policy →
Yes. The Founding Partner program is built for exactly this: a structured early partnership with a defined evaluation window, dedicated configuration support from the team, and pricing terms agreed as part of the institutional contract. The Partnerships page documents the program structure and how to begin procurement discussions.
When the toggle is set to disabled, every AI advisor feedback feature gates off for every account under your license: CV parsing, CV gap analysis, CV tailoring suggestions, cover-letter feedback, dual-source CV gap analysis, research-statement review, portfolio coherence audit, and venue & publishing discovery. The matching catalog, saved searches, alerts, application tracking, and the audit trail remain fully available. Gating is enforced at the application layer, with test coverage.
Today, no — institutional configurations are set by the Scholiad team at contract provisioning, and roster changes go through a documented support workflow. Day-1 roster and roster-revocation handling is available directly through the team for licensing partners.
Pricing is custom per seat count and deployment configuration (AI advisor enabled vs. disabled). Public tier names are Free, Plus, and Premium for individuals; institutional contracts roll seats under an institutional configuration. Contact the team — the Partnerships page documents the Founding Partner program structure for early cohorts.
Our infrastructure provider publishes its own SOC 2 Type II compliance documentation. Our security practices — transport encryption, one-way-hashed session tokens, log/secret redaction, pre-AI contact-detail removal, access controls, and rate limiting — are documented, and we complete security questionnaires for procurement review. A counsel-led privacy review is part of the pre-contract institutional-readiness work. We're glad to share our current security posture under NDA during procurement evaluation.
The team will route serious institutional inquiries to a 30-minute scoping call. If the Founding Partner program is the right entry point, we'll say so directly.