One defensible record for every Title IX and conduct case.
CampusResolve is the system of record for higher-education grievance resolution — a single-sourced case file, controlled communications, evidence integrity, an enforced-but-configurable process, and audit-ready export. Built to serve the institution and the parties alike.
Two things incumbent tools don't do.
Most case managers are admin-only filing cabinets. CampusResolve is designed around the two capabilities that actually reduce institutional risk.
A dashboard for the parties, not just administrators
Each complainant and respondent gets their own secure view — case status and phase, their own live deadline clocks, their submissions and channels, their procedural rights, and a support hub. A hub-and-spoke model means a party only ever sees their own side: the two parties never share a channel and never see each other's timers. Procedural legitimacy, by design — because a party who understands the process is a smaller liability.
- Own status & timeline
- Live deadline clocks
- Hub-and-spoke privacy
- Rights & resource hub
Produce a discovery-ready case package on short notice
The record doesn't just sit in storage — CampusResolve assembles it into an ordered, manifest-hashed export organized for legal use: state history, the communications ledger, evidence with chain of custody, notices with delivery receipts, determinations, and the audit trail. Every hour outside counsel doesn't spend reconstructing a file from scattered inboxes is real savings — which makes this the General Counsel's tool, not only the coordinator's.
- Full case-file package
- Manifest-hashed & ordered
- Party record fulfillment
- Accounting of disclosures
High-stakes matters run on email chains, shared drives, and hope.
Title IX and conduct cases carry real legal exposure — yet most institutions manage them across disconnected tools, with no single defensible record. CampusResolve replaces that fragility with one system of record.
Compliance risk
Missed deadlines, inconsistent process, and gaps in the record turn a hard case into institutional liability.
Fragmented evidence
Exhibits scattered across inboxes and drives make procedural fairness — and chain of custody — nearly impossible to prove.
No defensible trail
When a matter is challenged or litigated, institutions struggle to reconstruct who did what, when, and under which policy.
Everything a matter needs, in one case file.
The subsystems that intake, manage, and document a case — engineered for containment, procedural fairness, and a record that holds together.
Intake & triage
A report is not a case. Intake is its own record with structured triage into four outcomes — case opened, informal resolution, supportive-measures-only, or dismissed/referred out. Supportive measures are offered regardless of outcome, and the jurisdictional and framework calls are recorded as human determinations with reasoning and citation — never auto-decided.
- Report ≠ case
- Four triage outcomes
- Supportive measures
Pinned, configurable process
Cases run on versioned process definitions, not hardcoded logic. Ship with a counsel-reviewed 2020 Title IX formal-grievance template; each institution configures durations, day conventions, wording, naming, and branding above the federal floor. A case pins to its process version at opening and never silently migrates.
- Versioned & pinned
- Configurable above the floor
- Counsel-reviewed template
Deadlines & compliance
Deadline rules with calendar or business-day conventions and academic-break tolling. Clocks start on notice sent / deemed-delivered — never on read — as an auditable configuration value. Overdue alerts ping the assigned staff so a matter never quietly stalls past a legally significant timeline.
- Deemed-delivered on send
- Break-aware tolling
- Overdue alerts
Evidence integrity
Originals are immutable and SHA-256-hashed; redaction produces a derived file, never a mutation. A chain-of-custody log records every upload, disclosure, and status change. Controlled review windows govern reciprocal release — administrators decide precisely when one party's evidence becomes visible to the other.
- SHA-256 originals
- Chain of custody
- Reciprocal-release windows
Communications ledger
One ordered, hash-chained transcript of every communication — in-system messages, official notices, and memorialized meetings. Complainant-to-respondent contact is structurally impossible: no shared channel exists. Notices render into the ledger with per-recipient delivery and acknowledgment tracking.
- Hash-chained transcript
- Party-to-party blocked
- Official notices & receipts
Access control & audit trail
Attribute-based, deny-by-default authorization computes a scoped decision at request time from the person's live relationship to the case — a recusal removes access instantly. Every grant and denial writes to an append-only, hash-chained access log. The party dashboard is built by asking the same engine, never a parallel query path.
- Deny-by-default ABAC
- Append-only access log
- One engine, all views
Principles that keep the product on the right side of the line.
These govern every part of the system — and they are as much about restraint as capability.
The software upholds the framework; humans make the judgment calls.
CampusResolve faithfully applies the process an institution and its counsel hand it, and surfaces the points that require human interpretation. It never decides what the law requires — that stays with the people accountable for it.
Institutions set the ceiling; the product guarantees the floor.
Freely adjust durations, wording, naming, and branding. Values that carry legal risk warn and log an override. Integrity guarantees are locked and structural — never disableable by configuration.
A party can always see their own case.
Their submissions, their channels, case status, their deadlines, their rights, and the notices and determination they're owed — a locked floor no institution can switch off. Institutions may add transparency above it, never below.
A tool for organization and efficiency — not a substitute for counsel.
Outputs, templates, and reminders support professional judgment and are meant for review by a qualified user. Nothing in the platform is legal, medical, or clinical advice.
Credibility earned the hard way.
There are no shortcuts on the things that matter in a Title IX case. CampusResolve is grounded in real regulation, real institutional practice, and independent review — not marketing.
Grounded in federal law
Every encoded constraint carries its regulatory source and citation — e.g., 34 CFR §106.45 — so the authority behind each step is visible, never assumed.
Modeled on real institutions
Validated against actual published Title IX procedures from major universities — including Ohio State and Arizona State — not a generic template.
Independently reviewed
The access-control design was examined by an external security consultant. Full implementation review and SOC 2 are underway — on the roadmap, not yet claimed complete.
Tested for integrity
The access-control engine and audit trail are covered by 180+ automated integrity and access-control tests — the parts where a bug could leak a record get the most scrutiny.
The record is only worth as much as its integrity.
Security and auditability are designed in from the first component — deny-by-default access, an append-only audit trail, and structural tenant isolation — so a case can be reconstructed with confidence when it's challenged.
Your process has to survive the next rule change.
The 2020 regulations are the operative federal framework today; the 2024 rule was vacated nationwide, and a new one is expected. Because every case pins to a specific, versioned process definition, a framework change is an explicit, logged, notified event — not a silent migration that rewrites a case out from under the people in it.
Evaluated and recommended by professionals.
Coordinators, general counsel, and Title IX attorneys are exactly who this is built for. Their words go here — real, attributed, and only with permission.
[Add a real, attributed quote from a Title IX coordinator here — e.g., what changed about running a case, deadlines, or the party experience.]
[Add a real, attributed quote from a general counsel here — e.g., on litigation readiness, the defensible record, or reduced outside-counsel spend.]
[Add a real, attributed quote from a Title IX attorney here — e.g., on procedural fairness, evidence integrity, or the completeness of the record.]
Now partnering with a small number of founding institutions.
We're working directly with a handful of design-partner institutions to shape CampusResolve around real Title IX and conduct workflows. Founding partners get roadmap input, priority support, and founding-partner pricing.
Important notices
This software is provided for informational, organizational, and workflow-management purposes only. It supports administrative efficiency and does not replace professional judgment, legal advice, clinical judgment, or regulatory-compliance obligations.
Not professional advice. All outputs, reminders, templates, and automated workflows should be reviewed by a qualified user before reliance or external use. Nothing within the platform constitutes legal, medical, financial, or other professional advice, and it is not a substitute for consultation with licensed professionals. Users are solely responsible for decisions made based on information processed or displayed within the platform.
User-submitted data. Users are solely responsible for the accuracy, completeness, and legality of all data entered. The platform does not independently verify user-submitted information and disclaims liability for errors, omissions, or misrepresentations in user-generated content.
Automated & AI-generated outputs. Where the platform includes automated suggestions, summaries, or AI-generated outputs, such outputs are provided for convenience only, may contain inaccuracies or incomplete interpretations, and should not be solely relied upon for decision-making without human review.
Notifications. The platform may send notifications via email, SMS, or third-party integrations (e.g., Microsoft Outlook). Delivery is not guaranteed and may be affected by external providers, user settings, or network conditions. The platform is not responsible for missed, delayed, or undelivered communications.
Availability. The software is provided on an "as available" basis. We do not guarantee uninterrupted access, error-free operation, or continuous availability. Maintenance, updates, or external outages may result in temporary service disruption.
Third-party services. The platform may integrate with third-party services. We do not control, endorse, or assume responsibility for third-party systems, their availability, security practices, or data handling. Use of such integrations is at the user's own risk and subject to the third party's terms.
Limitation of liability. To the maximum extent permitted by law, the company shall not be liable for any indirect, incidental, consequential, or punitive damages, including loss of data, revenue, business opportunities, or goodwill arising from use or inability to use the software.
Security. While reasonable security measures are implemented, no system is completely secure. Users acknowledge that data transmission and storage over digital systems carry inherent risks. The platform does not guarantee absolute protection against unauthorized access, breaches, or cyberattacks.
Compliance responsibility. Users are responsible for ensuring that their use of the platform complies with all applicable laws, regulations, licensing requirements, and internal organizational policies.