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.
- 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
- Input. Forms, emails and PDF documents.
- n8n intake. Receives and sorts each item.
- Language model. Reads the fields from invoices and contracts.
- Review step. A staff member checks each result.
- The firm’s system. A sheet, a CRM or a practice tool.
- 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
- Capture the request.
- Validate the required fields.
- Classify the matter or service type.
- Route it to the correct staff owner.
- Send an acknowledgment, or ask for the missing fields.
- Log the action.
- Update the reporting tables for the operations review.
More work
- Stay for the exhale
I turned a yoga teacher's classes into a membership product. I did the strategy, the design, the build and the operations.
- A bank reconciliation that explains each difference
A working sample of the reconciliation method from my years as Operations & Finance Lead. Excel formulas match 119 bank lines to 121 ledger entries, explain each difference and reconcile to 0.00.
- SQL case studies: revenue share, donor segments and a 3NF schema
Three SQL studies on small course datasets. Each one starts with a business question. Every figure is query output that you can run again.