Rishabh Prajapat | UIUX Design Portfolio

GET VEEVZ

An internal workspace for creator clip review and payout verification. This case study explains how a finance team moved from fragmented manual checks to a single auditable environment.

VISUAL STORYTELLING TRANSCENDS THE ORDINARY. PHOTOGRAPHY & VIDEOGRAPHY STUDIO.

Back to Projects

Project Type

Website Redesign & Repositioning

DESIGN PROJECT

ROLE

Strategy · IA · Design System

LEARNING PLATFORM

CLIENT

Get Veevz (Nexus Media)

Designer

Rishabh Prajapat

Pilot Window

Sep 8, 2026

MVP Launch

September 8, 2026

Scale Gate

October 26, 2026

Protecting margin through auditable verification.

A structured verification system was designed to make critical information traceable, measurable, and easier to validate. By replacing assumptions with clear evidence and auditable checkpoints, the framework reduces uncertainty while protecting operational and commercial margins.

LIVE PROJECT

THE

PROBLEM

Identity &

System

Manual verification was slow, fragmented, and prone to human error.

Before the workspace, moderators had to verify creator clips, payout history, and social data across separate browser tabs. Each record took approximately 30–60 seconds to verify, creating a fragmented workflow and increasing the risk of manual errors. This made it difficult for the team to consistently protect the target 10–12% commission margin.

[EXAMPLE DATA · INTERNAL WORKSPACE]

CONCEPTUAL WORKFLOW COMPARISON

BEFORE

1. Open payout record 2. Open creator profile 3. Open social API 4. Open ledger history 5. Decide

AFTER

1. Open payout record 2. Review creator, fraud, and ledger in one panel 3. Decide

SYNTHESIS NOTE · SEP 11, 2026

Sub-30-second verification paths and live keyboard shortcuts/undo were reported in synthesis notes, but no raw logs or current pilot values were supplied.

VERIFIED VIEW RATIO

98.42%

RISK ASSESSMENT

MEDIUM (42)

STATE

T2 PENDING

PRE-SUITE REALITY

Manual verification created a fragmented, capacity-limited workflow.

Before the suite, moderators spent 30–60 seconds verifying each clip while cross-referencing social APIs, KYC statuses, and ledger histories across separate browser tabs. This fragmented process made evidence harder to trace, increased manual effort, and ultimately constrained the team’s daily verification capacity.

PAIN METRIC [BEFORE]

30-60s

Average manual verification duration per individual clip before optimization, limiting maximum daily capacity.

MARGIN AT RISK [TARGET]

10-12%

Commission margin that structured evidence and KYC verification is designed to protect.

"THE SYSTEM MUST SURFACE EVERY TRUST SIGNAL BEFORE A PAYOUT DECISION."

RESEARCH & CONSTRAINTS

Human actors and rigid operational realities

Rather than relying on 50 remote interviews, the workflow was mapped through deep working sessions with Akshat and Smit the people directly operating within the system every day. Their firsthand experience exposed the real constraints, repetitive tasks, and operational dependencies shaping the existing process. This grounded the product direction in actual workflow realities rather than assumptions or theoretical user behaviour.

RESEARCH METHOD

Direct stakeholder sessions. Operational workflow mapping. Zero synthetic personas.

Note: Creator experience is an acknowledged research gap - deferred to post-pilot.

[PERSONA_01] Akshat · Finance & Moderation Lead

Manages daily T2 review SLAs, flags anomalies, and routes disputes. Needs extreme information density and zero-friction keyboard actions. Cannot lose context switching between tabs.

[PERSONA_02] Aryan · Founder & T3 Admin

Resolves high-risk escalations, governs system parameters, and authorises bank-settlement payouts. The final gate before money moves.

[PERSONA_03] Smit · Solo Tech Lead

Executing the entire production cycle alone. Demanded systematic, pre-designed component assets with clean, auditable states - no ambiguity.

LAUNCH CONSTRAINTS

Desktop 1440px only

24h SLA threshold

Immutable ledger

Invitation-only access

STRATEGIC DECISIONS

What we killed to succeed

The system deliberately removed unnecessary complexity, fragmented workflows, and manual dependencies that slowed verification and weakened operational clarity. By eliminating redundant steps and consolidating critical evidence into a more structured workflow, the experience was designed around faster decisions, stronger traceability, and greater operational efficiency.

KILLED PATHWAYS

Three Separate Dashboards

Separate tools made operators repeatedly switch context to assemble payout evidence.

Minimal Flat Design

Hides active-state severity. A pending fraud flag looks identical to a clean record.

Mobile-First Layout

Complex ledger tables cannot be safely collapsed to phone viewports without losing essential evidence density.

Warning Gates on Every Action

Repeated confirmations interrupt reversible review actions. Confirmation stays on irreversible settlement.

SELECTED APPROACH

One Unified Environment

Structured domain panels keep fraud context, KYC status, and ledger history in a single viewport.

Desktop-First Density

27-inch operational display. Every status signal is visible without scrolling.

Proactive Alerts

KYC expiry and fraud flag changes surface before Akshat opens the record - not after.

Confirmation Only for Settlement

3-second undo buffer protects against miskeys on triage. Hard modal reserved exclusively for irreversible bank settlement.

SYSTEM ARCHITECTURE

Three integrated operational surfaces

Three connected operational surfaces were designed as one cohesive engine, allowing data to move seamlessly from initial ingest through triage and into final auditable settlement. Each surface serves a distinct operational purpose while remaining connected through a shared data and evidence flow. This creates a unified system where information stays traceable across the entire verification and settlement lifecycle.

FINANCE LEDGER

Two-panel design keeps fraud context visible.

Traditional single-list interfaces force moderators to repeatedly open and close records, disrupting their review workflow. The two-panel layout keeps critical information including fraud scores, KYC statuses, and control checklists visible alongside the active record. By eliminating unnecessary context switching, the interface supports faster evaluation, more informed decisions, and a more continuous verification process.

T2 Pending Review · Finance Payout Ledger

SLA critical: 24h review threshold · 8 records · 3 selected for batch

EXPLANATORY VISUAL

Two-panel payout review

Selected payout stays visible while fraud context, verification evidence, and approval controls are reviewed in one place.

EXPLANATORY VISUAL

ALL DATA IS EXAMPLE DATA

ILLUSTRATIVE PAYOUT TABLE

Selected payout stays visible while fraud context, verification evidence, and approval controls are reviewed in one place.

SELECT

CREATOR / AMOUNT

STATUS

RISK

SLA

☑

@sofi · ₹3,400

PAY-2026-001241 · Daily Rituals

T2 Pending

Pending

05:18

Sep 4

›

□

@mitra · ₹8,250

PAY-2026-001234 · Summer Vibes

T2 Pending

Verified

08:42

Sep 4

›

☑

@anaya · ₹6,900

PAY-2026-001241 · Daily Rituals

T2 Pending

Pending

05:18

Sep 4

›

□

@rohan · ₹4,175

PAY-2026-001234 · Summer Vibes

T2 Pending

Verified

08:42

Sep 4

›

□

@priya · ₹12,400

PAY-2026-001234 · Summer Vibes

T2 Pending

Verified

08:42

Sep 4

›

5 of 8 payouts shown

Showing 5 of 8 payouts

FRAUD CONTEXT DETAIL PANEL

Selected payout context

Fraud score, creator trust, KYC, sync health, payout amount, and audit context stay visible while the moderator reviews verification evidence and guarded approval.

SELECTED PAYOUT

@sofi · ₹3,400

PAY-2026-001241 · Daily Rituals

T2 Pending

SUBMITTED

FRAUD SCORE

CREATOR TRUST

4.8

KYC

VERIFIED

SYNC HEALTH

HEALTHY

PAYOUT AMOUNT

₹3,400.00

AUDIT CONTEXT

Creator has 4 approved clips and no recent disputes. Payout amount is within campaign range and sync health is healthy.

VERIFICATION EVIDENCE

Evidence visible before approval

✓

Campaign assignment

Complete

✓

KYC verified

Complete

✓

Sync health healthy

Complete

✓

Amount calculated

Complete

GUARDED APPROVAL

Approval is guarded by selected payout, visible verification evidence, and moderator decision.

● Approve

○ Escalate

○ Reject

Approve payout

Reject payout

Selected payout

The selected payout stays visible on the left so the moderator can compare the list row with the detailed fraud context on the right.

Visible verification evidence

Verification evidence such as campaign assignment, KYC, sync health, and amount calculation are visible before the moderator approves.

Guarded approval

Approval is guarded by the selected payout, visible verification evidence, and a moderator decision that can be approved, escalated, or rejected.

WHY THIS WORKS

The left 3px blue border instantly identifies selected payouts during batch review. Risk scores (38-57) and KYC status badges occupy fixed columns - the eye scans vertically without needing to open a record. The batch confirmation button only appears when > 0 records are selected, eliminating accidental submissions.

MODERATOR QUEUE

One clip. Zero context switching.

The triage workflow was designed to minimise interaction friction without compromising accountability. Context-scoped keyboard shortcuts enable moderators to approve, reject, request revisions, flag, or escalate clips without navigating away from the active record. A three-second undo buffer provides a recovery window for accidental actions, balancing operational speed with control.

KEYBOARD MAPPING [CONTEXT-SCOPED]

[A] Approve · [R] Reject

[V] Revision · [F] Flag · [E] Escalate

Scoped strictly to active triage card - never fires inside form fields.

FAST-TRACK CRITERIA [AUTO-APPROVE ELIGIBLE]

Trust > 80 · Fraud < 20 · Amount ≤ ₹5,000

TARGET: > 15 clips / hour throughput

ADMIN OPERATIONS

Proactive oversight, not reactive firefighting.

The oversight dashboard consolidates SLA trajectories, queue depths, fraud rates, and pending KYC escalations into a unified operational view. By making critical performance indicators visible before service levels deteriorate, the system helps operators identify emerging bottlenecks, prioritise interventions, and address risks before they escalate into SLA breaches. The result is a shift from reactive issue management to proactive, evidence-driven operational control.

QUEUE DEPTH

Illustrative data

FRAUD RATE

1.42%

Illustrative data

UPTIME

≥99.5%

Uptime target

Operational Design Patterns

PATTERN · ModeratorTriageCard

Encapsulates total views, creator context, risk thresholds, and localised keyboard listeners into a singular focusable container. Every piece of evidence needed for a decision lives inside one module.

PATTERN · Auditable LedgerRows

Strict high-density row structures using monospace font layers for precise tabular alignment of transaction IDs, amounts, and dates. The left-border treatment communicates selection state at a glance.

PATTERN · 3-Second Undo Buffer

Removes warning dialogs from non-destructive triage actions without removing accountability. Speed and safety co-exist. Modals are reserved strictly for irreversible bank settlement.

VISUAL SYSTEM

Uncompromising design tokens built around function, not preference.

Every design token was assigned a clear functional role to maintain consistency, usability, and operational clarity across the interface. Colour was treated as a communication mechanism rather than a branding choice, with distinct states indicating risk severity and guiding operator attention. This creates a purposeful visual system where every element reinforces information hierarchy, supports faster interpretation, and enables consistent decision-making.

GOVERNANCE & COMPLIANCE

THE DESIGN

SYSTEM

Maker-checker controls and immutable governance built into the architecture.

Governance was established as a foundational design requirement rather than an additional layer applied after implementation. The architecture incorporates maker-checker separation, structured approval workflows, and immutable audit trails to support accountability across critical operational actions. Each control is designed to strengthen traceability, preserve decision history, and align the system with rigorous audit requirements.

DUAL ROLE ENFORCEMENT

The person who reviewed a payout cannot also execute payment. Role and approval-tier checks keep the maker and checker separate.

MASKED PII PATTERNS

Creator identities remain concealed (A*** S***) until explicit permission gates trigger. Reduces bias in the initial risk assessment - moderators evaluate signals, not identity.

PERSISTENT AUDIT TRAILS

Immutable logging of timestamps, IP addresses, and user-IDs on every state change. Disputes trigger linked adjustment records - original transactions are never overwritten.

FINANCIAL THRESHOLD RULES

30-day rolling payout caps. 5-10 day fraud hold triggered by velocity anomalies. 5% safety reserve enforced on all T2/T3 creators during pilot.

DUAL ROLE ENFORCEMENT

The person who reviewed a payout cannot also execute payment. Role and approval-tier checks keep the maker and checker separate.

PERSISTENT AUDIT TRAILS

Immutable logging of timestamps, IP addresses, and user-IDs on every state change. Disputes trigger linked adjustment records - original transactions are never overwritten.

MASKED PII PATTERNS

Creator identities remain concealed (A*** S***) until explicit permission gates trigger. Reduces bias in the initial risk assessment - moderators evaluate signals, not identity.

FINANCIAL THRESHOLD RULES

30-day rolling payout caps. 5-10 day fraud hold triggered by velocity anomalies. 5% safety reserve enforced on all T2/T3 creators during pilot.

PILOT STATUS & SCALE GATE

Evidence of

Utility.

October 26 go / no-go parameters

The Scale Gate evaluation is structured around predefined performance targets that determine whether the system is ready to progress beyond the pilot phase. Each metric serves as an evaluation criterion rather than a claimed outcome, establishing clear expectations for operational efficiency, verification accuracy, and governance. All metrics represent target thresholds, not achieved results. Final pilot outcomes will remain unconfirmed until the evaluation window closes.

SCALE GATE TARGET CRITERIA [8 PARAMETERS]

[01]

Net Margin Retention ≥ 10%

TARGET

[02]

Dispute Rate ≤ 3.0%

TARGET

[03]

Fraud Precision ≥ 80%

TARGET

[04]

SLA Compliance ≥ 95%

TARGET

CONTINUED

[05]

Throughput ≥ 15 clips/hour

TARGET

[06]

Proactive Detection ≥ 90%

TARGET

[07]

Uptime ≥99.5% OR API stability ≥95%

TARGET · NOT MEASURED

[08]

Appeal Rate ≤ 2.0%

TARGET

DECISION FRAMEWORK

8 / 8 → GO

Proceed to complete automated infrastructure scale-up.

7 / 8 → REVIEW

Emergency 4-week fix and validation sprint.

ACTIVE RISK MITIGATIONS

View-Sync Gateway Outages

Local view cache falls back to manual verification triggers to prevent review queue starvation.

Moderator Capacity Limits

Auto-triage fast-tracks clean payouts - only flagged cases route to manual review.

WHAT WE ARE NOT CLAIMING YET

Validated 10k/day scale · Completed mobile dashboards

Creator-facing research outcomes · Full accessibility certification

RETROSPECTIVE

PROJECTED

IMPACT.

Key design discoveries that shaped the system.

The project revealed critical insights into how operational workflows, information visibility, and governance requirements influence system design. These discoveries informed decisions around contextual triage, streamlined verification, proactive oversight, and embedded audit controls. Together, they established a design direction grounded in operational realities, reducing unnecessary complexity while strengthening efficiency, traceability, and decision-making.

DISCOVERY 01

Compliance Drives Information Architecture

Maker-Checker requirements shaped the ledger hierarchy and made decision ownership visible. The pilot will test whether these safeguards reduce errors.

DISCOVERY 02

Shortcut Context Scoping

Scoping single-key actions strictly to active triage cards prevents dangerous miskeys inside form fields. The boundary between speed and safety must be architecturally enforced.

SOURCE NOTE · SEPTEMBER 11, 2026

• The supplied synthesis reports MVP launch on September 8 and a sub-30-second verification path.

• It reports keyboard decisions and undo as live in the early pilot.

• Dashboard figures are illustrative; no current pilot dataset was supplied.

• Scale targets remain subject to the October 26 decision.

EXECUTION

CASE

TAKEAWAYS

The four-step production journey

A clearly defined four-step production journey was introduced to make the delivery process transparent and predictable. The page guides visitors through the ongoing content cycle, showing how each stage moves from initial planning to production, refinement, and delivery. This gives prospective clients a concrete understanding of what happens after engagement and sets clearer expectations around the working process.

STAGE 01

Onboarding & Audit

Setting brand guidelines and visual assets.

STAGE 02

Weekly Content Sprints

Raw video ingestion and editing.

STAGE 03

Review & Refine

Collaborative revision and sign-off.

STAGE 04

Launch & Iterate

Publishing and analysis of performance.