RequiredAdmin
Identity check
Confirm legal name, profile photo, primary location, and contact method before guide approval.
legal_nameid_document_typeid_statusverified_at
Verified guide standard
✓ ↗ ♙
Make guide approval clear before the backend exists.
This page documents the static verification UX for travelers, guides, and admins. Later, these checks become guide application fields, admin decisions, trust scores, and verification timestamps in MySQL.
Required checks
3
identity + safety
Profile score
92%
target quality
Admin review
Manual
before approval
Verification checklist
Backend-ready checks that map to guide application and trust-score tables later.
✓
RequiredAdmin + guide
Local expertise review
Review destination knowledge, languages, sample tour ideas, and local experience evidence.
primary_citylanguagesyears_experienceexpertise_notes
RequiredGuide
Safety agreement
Guide accepts marketplace rules: public meeting points, no unsafe detours, no pressure, no off-platform payment requests.
safety_terms_accepted_atmarketplace_rules_version
RecommendedGuide
Profile quality
Guide profile should include a strong bio, clear languages, tour categories, availability notes, and real traveler-friendly details.
profile_scorebiotour_countprofile_review_status
OngoingAdmin
Ongoing marketplace monitoring
Reports, low response quality, suspicious requests, and repeated cancellations should affect guide status.
trust_scorereport_countlast_reviewed_ataccount_status
Guide approval workflow
1Apply
Guide submits profile and local expertise.
2Review
Admin checks identity, languages, safety agreement.
3Approve
Guide tools unlock and profile can appear in matching.
4Monitor
Reports and quality signals affect account status.
Traveler trust copy
Public pages should say “verified local guide” only after the guide profile has passed admin checks. Until then, use “guide applicant” or “pending guide”.
Read safety center