Overall great! I'm still working on following every step. Need to figure out the linking!

Intro

This tutorial shows how to leverage Entities to support a household survey at scale.

This is helpful because it makes clear to the user why they would want to use entities instead of what they have currently. Maybe we also include scenarios of when it might be a good fit.

In this workflow, households have already been identified, sampled, and assigned to enumerators. We focus on enumerators visiting each of their assigned households to capture baseline data and build member rosters. They will then need to follow up both with the households and selected individuals over time

Diagram is great! We could make it aligned with our existing style?

Could we also make the objectives easier to scan? Maybe something like this...

What You Will Learn
By the end of this tutorial, you will be able to:

• Link Entity lists : Link individual members and operational forms to a parent household
• Handle pre-assigned workloads: Use already sampled and assigned households to specific enumerators
• Register households: Capture baseline data and register the household as an Entity.
• Enable follow-up workflows: Access and update these records during subsequent visits

Designing the Entity model

This section is very helpful! It would be great to get Andrew's thoughts on this too. I'm pretty sure he wrote a form post about it. I don't think we need a checklist but maybe we could pull out key things to consider in a bulleted list?

while Entities store the current state of real-world things that need to be accessed and updated over time.

I like this distinction!

Ending - Building the baseline form

The end kind of feels abrupt. Maybe we can say the intended outcome again? Do we recommend them testing it out with real people or what would be the best next step?