Corgi Workflow Demo
A lightweight internal workflow concept for filing intake, approval routing, exception handling, and audit-ready change logging. Built to demonstrate how ambiguous, compliance-heavy operational processes can be translated into structured product systems.
Filing Intake
Workflow Status
Intake Received
Complete
Checklist Generated
Complete
Compliance Review
Active
Legal Approval
Pending
Final Ready
Pending
Audit Log
10:02 AM
Request created by Operations
Initial filing request submitted with fund metadata and effective date.
10:11 AM
Checklist generated
Workflow requirements, reviewer assignment, and exception flags initialized.
10:24 AM
Disclosure revision detected
System recorded text update requiring compliance review before final publishing state.
10:41 AM
Review queue updated
Exception surfaced for date mismatch between intake submission and source timing notes.
Exception & Review Queue
Disclosure language requires compliance validation
Change was detected after checklist generation and must be reviewed before legal approval is routed.
Review
Effective date mismatch
Source notes reference a timing dependency that does not yet match the filing’s current effective date.
Alert
Legal approval not yet initiated
Routing remains blocked until compliance review clears the outstanding disclosure and timing issues.
Pending
Design Notes
Why this concept: The goal is to show how a messy, manual workflow can be translated into a structured internal product surface that supports intake, approvals, exception handling, and auditability.
What this demonstrates: Operational workflow thinking, review-state design, change visibility, exception surfacing, and clean internal UI execution in a controlled environment.
How I’d evolve it: Versioned records, evidence capture, role-based permissions, structured approvals, export-ready outputs, queue ownership, and reconciliation states fed by upstream API or file-based inputs.