A new chapter looks good on you. Let’s build yours ↗
ai freelancer.Your free toolkit ↗
Operations & automation · PRACTICE LAB

Design a small intake workflow that fails safely

A workflow map, test log, and operator handoff using synthetic records.

Fictional practice project. Use it to demonstrate your process, not to claim a client relationship, qualification, or measured business result.

The brief

Northline Studio is fictional. It wants new project inquiries organized for human review. Design a test workflow that creates one review task per valid inquiry. No automated prospect messages, production credentials, or real customer records are needed.

Your source material

SYNTHETIC INPUT RECORDS
A: inquiry_id=demo-101, email=person-a@example.com, service=Presentation, brief=Refresh a 10-slide pitch
B: inquiry_id=demo-101, email=person-a@example.com, service=Presentation, brief=Refresh a 10-slide pitch (duplicate event)
C: inquiry_id=demo-102, email=(empty), service=Content, brief=Newsletter pilot
D: inquiry_id=demo-103, email=person-b@example.com, service=Other, brief=Need help; please contact me
Task fields: inquiry_id, requested service, brief, review status.
Rules: missing required fields go to an exception queue; a repeated inquiry_id must not create another task; unfamiliar services get a “Needs clarification” label.
Failure scenario: task system returns an error before creation. Demonstrate a bounded retry or manual recovery route without duplicating the task.
All tasks remain unassigned drafts until a human reviewer acts.

Work through the project

  1. Describe the manual process before choosing any automation software.
  2. Draw validation, duplicate handling, task creation, and exception paths.
  3. Run the four records through a paper simulation or sandbox prototype; state which you used.
  4. Simulate the connection failure and record recovery behavior.
  5. Write a handoff with an off switch, reviewer responsibility, and a list of untested conditions.

A judgment call worth noticing

A happy-path demo is incomplete evidence. A useful test log records the input, expected result, observed result, and whether the result came from a simulation or an executed prototype.

Want to see a complete example?

Compare the brief, draft corrections, finished output, and review notes after making your own attempt.

Open the worked example ↗

Review your sample

Mark a check only after inspecting your output. Clicking saves these checklist ticks on this browser. Nothing is sent to an AI model. You can clear progress from My saved resourcesAI workflow planner.

Make the work portfolio-ready

Include the fictional brief, your artifact, two decisions you made, and the checks you performed. Explain where AI helped and what you changed. Separate self-review from feedback you actually obtained. Do not claim an outcome you did not measure.

Draft the sample case study ↗

Explore another practice lab