> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/how-to-guides/create-related-checklist-from-workflow.md).

# Create Related Checklist from Workflow

Use the guided **Create related records** workflow step to spawn a photo or document checklist when a parent record reaches a status — for example six inspection photo slots when a job is Scheduled.

{% hint style="info" %}
**Shipped 9 Aug 2026**\
Part of guided Automation in the [9 Aug 2026 Release](https://docs.notionapps.com/release-notes/9-aug-2026-release).
{% endhint %}

## When to use this

* Field jobs need a fixed set of photo slots after assignment.
* Onboarding needs a standard document checklist per client.
* You previously chained many Create record steps and want one guided step.

## Prerequisites

* Parent sheet (Jobs, Requests, …) related to a child checklist sheet.
* Status options that mark when the checklist should appear.
* Workflow Foundation entitlement.

## Steps

1. Open Workflow Foundation → create or edit the workflow that runs when status becomes **Scheduled** (or your trigger status).
2. Add **Create related records** (or start from the **Create photo checklist** recipe).
3. Choose the parent → child relation and the template rows (slot names / required flags).
4. Optionally publish a Task or Decision so supervisors see progress in Work Queue.
5. Publish the app and move a test parent record to the trigger status.
6. Confirm child rows appear and field users can complete them from their list/form.

## Tips

* Prefer **Create related records** over N separate Create record steps.
* Keep slot names stable so e2e and field training stay consistent.
* Pair with [Work Queue Screen](https://docs.notionapps.com/screens-and-components/types-of-screens/native-automation-and-operational-screen-guides/work-queue-screen) when humans must claim follow-up.

## Related

* [NotionApps Workflow How-To Guide](https://docs.notionapps.com/automation/notionapps-workflow-how-to-guide)
* [Client Review Hub in 15 Minutes](https://docs.notionapps.com/guides/client-review-hub-in-15-minutes)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/how-to-guides/create-related-checklist-from-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.