yoink.team Start a list

Disaster response check-ins

After a flood the list is households and the volunteers are whoever turned up. Neither of those is known in advance, and the coordination has to work anyway.

What goes wrong

What the list looks like

Wellness checks — Thursday

  1. Wellness checks — Block 14, 9 addresses
  2. Wellness checks — Block 15, 12 addresses
  3. Wellness checks — Block 16, 7 addresses
  4. Water drop — Riverside flats, 3 floors
  5. Generator check — community centre
  6. Phone check-ins — list A, 20 households
  7. Phone check-ins — list B, 20 households

One item per line, pasted from wherever you keep them. That paste is the entire setup — there is no project to configure.

Open this example →

How it runs

Questions

Is this reliable enough for safety-critical work?

No, and the terms say so plainly. There is no uptime guarantee and a claim is not a guarantee that anybody went. Treat it as coordination, never as the only record of whether a household was checked.

Does it work without a data connection?

It needs a connection to load and to take an item, but it is a small page with no app to install, and it works without JavaScript on a bad link.

How do we keep vulnerable people's details off it?

Keep items at the level of a block or a list name. Anyone holding the link can read the board, and in a live response those links get forwarded.

Can we lock the board once teams are out?

Yes. Locking stops new claims while leaving the board and the record readable, which is usually what you want once everyone is deployed.

Close to this

Start this list →

You get two links: one to share, one to run it with. No email, no account, nothing to confirm. How it works.