Skip to main content
Use this checklist before a large export, a citywide research pass, or a sync to Atlas.

1. Check The Command

2. Prepare Scout

For scripts, pass credentials through the shell:

3. Check Readiness

Do not start a large run until Scout is ready for the work you plan to do.

4. Run A Small Pass First

Start with one known public page:
Then test the place and issue set:

5. Check Browser Rendering When Needed

If the sources depend on JavaScript, test a bounded crawl:
Scout should use normal HTML first and keep browser renders within the budget.

6. Review The Results

Check source title, URL, date, type, and context before export or sync. Do not treat a name as current just because Scout found it.

7. Export Or Sync

Export reviewed people:
Sync a reviewed run:
Keep uncertain work private to a workspace:

Ready To Scale

A large run is ready when:
  • Scout is ready for direct runs, search discovery, and sync.
  • A small direct URL run and a small place-and-issue run both produce useful results.
  • Browser rendering stays bounded when it is used.
  • Sampled entries include source context that supports the claim.
  • Exported files preserve source fields.
  • Sync returns a receipt and does not directly publish public records.