Compliance Workflow Tool

Problem

Trade-compliance teams still track export-control and sanctions changes with alerts, spreadsheets, and manual policy review. In a company with global products, that creates too much ambiguity around who needs to review a rule, which policy language is affected, and what evidence is left behind.

What I built

A focused case-study workflow for Qualcomm-style export compliance: detect a BIS or OFAC update, match it to affected policies and product lines, draft a policy redline, route it through legal and trade reviewers, and preserve an audit trail.

Outcome

The Qualcomm conversations helped move the product from a broad compliance assistant toward a sharper trade-control workflow where the buyer pain is concrete: policy owners need a defensible path from regulatory change to approved operating language.

What I learned

• Learned that generic compliance summaries are not enough. Teams need the exact policy clause, responsible owner, approval step, and audit record.
• Narrowed the product from general compliance to trade controls because export and sanctions changes create urgent, traceable operational work.
• Used the Qualcomm case study to make the demo specific: advanced-chip export controls, restricted-party screening, licensing escalation, and policy redlines.