Client intake system: from process map to data design

A systems-analysis design for service intake: capture, validate, classify, route, reply, log and report. It applies course methods to the intake problems that I saw in consulting.

Role
Systems analyst (coursework)
Period
2024 – 2025 · rebuilt in 2026
Stack
Process mapping, Data modelling, Requirements
Evidence
Sample data
Question
Intake arrives by forms, emails and shared spreadsheets, and staff route it by hand. How do we get complete data, clear owners and a record of each step?
Data
Course concepts (process models, DFDs, data modelling) and the workflow audit template from my automation work.
Method
Map the current process. Set the system boundary. Define the entities and audit fields. Write acceptance tests for each step: validate, classify, route, reply and log.
ResultSample data
A requirements-to-design pack with a process map, a data model and acceptance tests.

A recreated concept design, not the original coursework and not a live client system.

The automation pattern from my consulting work

  1. Input. Forms, emails and PDF documents.
  2. n8n intake. Receives and sorts each item.
  3. Language model. Reads the fields from invoices and contracts.
  4. Review step. A staff member checks each result.
  5. The firm’s system. A sheet, a CRM or a practice tool.
  6. Reports. Weekly reports and follow-up emails.

Wrong field: fix and resend.

The workflow pattern that I built for small legal and financial firms, 2023 – 2025. The intake design on this page starts from these problems. Pattern only, with no client names.

The target flow

  1. Capture the request.
  2. Validate the required fields.
  3. Classify the matter or service type.
  4. Route it to the correct staff owner.
  5. Send an acknowledgment, or ask for the missing fields.
  6. Log the action.
  7. Update the reporting tables for the operations review.