Canonical identity
Official name, former names, institution category/type and establishment context.
University Intelligence
A living intelligence record for every issuer.
Identity · Campuses · Contacts · Recognition · Coverage
Each university record can connect its official identity to campuses, programmes, domains, results/verification/transcript portals, verification contacts, source provenance, recognition history and known credential coverage.
Issuer profileUniversity intelligence
Canonical identityUniversity of Example
Former names · type · establishment year · headquarters
LocationsMain + approved campuses
State/country and programme context
Verification routesEmail #1/#2 · Phone #1/#2
Portal, results and transcript routes where available
Source-firstAuthoritative routes outrank appearanceMinimum evidenceEscalate only what can resolve uncertaintyHuman gateSerious adverse outcomes require reviewAuditableMaterial actions preserve lineage
WHAT BONAFIDE DOES
Purpose-built verification capabilities.
Each capability is a visible part of the verification workflow—not a hidden AI score.
Location graph
Headquarters, approved campuses/off-campus centres, state/country and relevant jurisdiction.
Digital identity
Official website/domain, results portal, verification portal and transcript portal.
Trusted contacts
Verification/COE/registrar emails and official phones where available, each with provenance class.
Recognition history
Historical regulatory status with effective dates rather than a present-day-only label.
Document coverage
Known credential types, years/versions and verification-route availability.
EVIDENCE MODEL
Change is recorded; history is not overwritten.
When a domain, contact, campus or recognition status changes, Bonafide keeps old/new values, source evidence and review history. A stale A1/A2 route can lose automation eligibility until reconfirmed.
- Contact/domain/portal change monitoring
- University/campus/programme/regulatory change detection
- Periodic A1/A2 contact reconfirmation
- Document-version clustering and review queue
- Source snapshot/hash retention where legally permitted
Issuer profileUniversity intelligence
Canonical identityUniversity of Example
Former names · type · establishment year · headquarters
LocationsMain + approved campuses
State/country and programme context
Verification routesEmail #1/#2 · Phone #1/#2
Portal, results and transcript routes where available
WORKFLOW
From input to defensible evidence.
Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.
01Seed record→
02Validate source→
03Add campuses/routes→
04Version changes→
05Measure response quality
DESIGNED FOR
One evidence model. Role-specific operations.
The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.
Admissions teams
Issuer context beside each credential
Verification operations
Trusted routes and responsiveness history
Data acquisition
Controlled source refresh and approval
DECISION DISCIPLINE
Unknown ≠ fake.
Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORMEstablish what is bona fide.