# Design a workflow with human checkpoints

AI Content Creation | Module 19: Build a repeatable production workflow

## Your goal

Decide where automation helps and where review is required.

Break production into intake, source checking, drafting, editing, access review, approval, and release. Each step should have an input, an output, and someone responsible.

Automation can copy approved fields into a template or prepare a draft. It should not decide that an unsupported claim is true or that an asset has permission.

Keep an audit trail with the source version, prompt, draft, edits, and approval. If a problem appears later, this record helps you find which assets need correction.

## Source pack

FICTIONAL PRACTICE BRIEF: Green Bench is a student repair club. It runs a free notebook-cover repair workshop on Saturday, 14:00 to 16:00, in Room B. There are 12 places. Learners bring one worn notebook; tools and scrap card are provided. Register using the club form. No date, form URL, access arrangements, impact figures, or testimonials have been supplied. Ask the organiser about missing details before publishing. This is a creative exercise, not a real event.

## Worked example

Map a small content workflow and its approval gates.

### Workflow

Intake the brief, confirm sources, draft the message, edit for clarity, review access and permissions, then request final approval.

### Human gates

A reviewer confirms the factual claims and asset permissions. The organiser approves event details before anything enters a publishing queue.

### Record keeping

Save the source version, prompt, draft, edited file, and approval note under a shared asset name so changes are traceable.

## Your work

Map a small content workflow and its approval gates.

### Workflow

Write at least 8 words.


### Human gates

Write at least 8 words.


### Record keeping

Write at least 8 words.

## Review your work

- [ ] Every stage has a clear output.
- [ ] Human review covers claims and release.
- [ ] The records support later corrections.

Completeness checks do not assess creative quality or factual accuracy. Review the actual work yourself or with a mentor.

## Quiz

1. Which step needs evidence and an accountable decision?
   A. Final approval of facts and permissions.
   B. Naming a draft file.
   C. Copying a heading into a template.

2. An automated workflow moves drafts directly to publishing. What is missing from this course workflow?
   A. A more decorative file name.
   B. A guarantee that all future claims will be correct.
   C. A human approval gate for facts, permissions, and release.

## Quiz explanations

1. A: Automation can assist production, but approval requires a responsible review.

2. C: Drafting automation does not replace accountable approval.

## Further reading

[Anthropic: prompt engineering overview](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/overview)