Build a Compliance Evidence Engine

Regulated filing is a software problem: capture the record, keep the digital link, know the obligation, prove what you sent. Over six stages you build that engine, writing code in the page with instant checks and a marked deliverable each stage. The project output is owned by Mai Studies and may be licensed or sold; you keep the right to show your own work in your portfolio.

12 weeks 90 guided hours Advanced

See membership

No account needed to buy. Pay with your card and we create your student account from the email you enter, with this programme ready inside it for twelve months.

Build a Compliance Evidence Engine course artwork

What you will achieve

Capture records so that any later change is detectable
Express filing obligations as rules a machine can evaluate
Assemble a signed evidence pack for a submission
Carry correlation identifiers through every call and store them
Turn provider error codes into remediation a non-technical user can act on

Entry guidance

— Comfortable writing JavaScript functions
— Interest in regulated or financial software
— Around seven hours a week for twelve weeks

Original Mai Studies learning material. This is a professional completion programme, not a regulated qualification or university accreditation.

Programme syllabus

6 applied modules

Lessons: 12
Assessed tasks: 6
Practice questions: 119
Timed mock papers: 4

Stage 1: Capturing a record you can stand behind

Make every record tamper-evident from the moment it arrives.

2 lessons · 20 practice questions · 1 assessed task

1. Capturing a record you can stand behind — notes37 min study · 3 learning objectives · practical activity
Make every record tamper-evident from the moment it arrives.
2. Capturing a record you can stand behind — build it35 min study · 3 learning objectives · practical activity
Build capture with versioning, then write your definition of a record and the boundary cases you decided to exclude.

Stage 1 deliverable: Capturing a record you can stand behind — marked out of 100, pass at 80%

Stage 2: Obligations as rules a machine can evaluate

Work out what is due, and when, from the records themselves.

2 lessons · 19 practice questions · 1 assessed task

1. Obligations as rules a machine can evaluate — notes37 min study · 3 learning objectives · practical activity
Work out what is due, and when, from the records themselves.
2. Obligations as rules a machine can evaluate — build it35 min study · 3 learning objectives · practical activity
Write the obligation evaluator and handle the three edge cases named above, with a test for each.

Stage 2 deliverable: Obligations as rules a machine can evaluate — marked out of 100, pass at 80%

Stage 3: Assembling the evidence pack

Build the file that proves what you sent and why.

2 lessons · 20 practice questions · 1 assessed task

1. Assembling the evidence pack — notes36 min study · 3 learning objectives · practical activity
Build the file that proves what you sent and why.
2. Assembling the evidence pack — build it36 min study · 3 learning objectives · practical activity
Assemble and seal a pack for one submission, then write your retention rule and the deletion procedure at the end of it.

Stage 3 deliverable: Assembling the evidence pack — marked out of 100, pass at 80%

Stage 4: Submission, identifiers and retries

Send it, and be able to say exactly what happened.

2 lessons · 20 practice questions · 1 assessed task

1. Submission, identifiers and retries — notes36 min study · 3 learning objectives · practical activity
Send it, and be able to say exactly what happened.
2. Submission, identifiers and retries — build it36 min study · 3 learning objectives · practical activity
Build the idempotency key and retry policy, then write the reconciliation procedure for an unknown outcome.

Stage 4 deliverable: Submission, identifiers and retries — marked out of 100, pass at 80%

Stage 5: Error mapping and remediation

Turn a provider code into something a person can act on.

2 lessons · 20 practice questions · 1 assessed task

1. Error mapping and remediation — notes37 min study · 3 learning objectives · practical activity
Turn a provider code into something a person can act on.
2. Error mapping and remediation — build it34 min study · 3 learning objectives · practical activity
Build the mapping with a safe default, then classify every error you have into user-fixable, software-fixable and provider-only.

Stage 5 deliverable: Error mapping and remediation — marked out of 100, pass at 80%

Stage 6: Reporting, export and the handover

Prove the whole thing works to someone who did not build it.

2 lessons · 20 practice questions · 1 assessed task

1. Reporting, export and the handover — notes36 min study · 3 learning objectives · practical activity
Prove the whole thing works to someone who did not build it.
2. Reporting, export and the handover — build it34 min study · 3 learning objectives · practical activity
Build the summary and a CSV export, then walk a non-technical reader through the system and record what confused them.

Stage 6 deliverable: Reporting, export and the handover — marked out of 100, pass at 80%

Timed mock papers

Build a Compliance Evidence Engine: timed mock paper 1 — 180 minutes, 30 objective questions plus written and computational tasks
Build a Compliance Evidence Engine: timed mock paper 1 — 180 minutes, 30 objective questions plus written and computational tasks
Build a Compliance Evidence Engine: timed mock paper 2 — 180 minutes, 30 objective questions plus written and computational tasks
Build a Compliance Evidence Engine: timed mock paper 2 — 180 minutes, 30 objective questions plus written and computational tasks

Lesson pages, assessed tasks and mock papers open the moment you join this programme. Teaching material is studied online; the notes you write are yours to download.

What students say

No ratings yet.