See manifesting built for the way your dropzone runs

True todayThe tandem-waiver demo keeps a sample record in your browser. This board reads that record and sets the matching tandem guest's waiver flag. If no record is found, the board shows a default sample record and says so. Both pages must be opened in the same browser on the same site for the record to be shared.

PlannedA production version would store waivers on a server with access controls, so desk, tablets and manifest all see the same record. That is not built.

The three demo pages agree on these values. If a path changes, update it in all three pages.

• Dropzone home: /dropzone-home/
• Tandem waiver demo: /tandem-waiver-demo/
• Manifest board (this page): /dropzone-manifest-demo/

The waiver demo writes its sample record to localStorage under the key fs-demo-tandem-waiver, as an object with a guest name and a status. This board also accepts an array of such objects.

localStorage.setItem("fs-demo-tandem-waiver",
  JSON.stringify({guest:"Dev Okafor", status:"signed"}));

The waiver demo's "Continue to manifest board" link should point to /dropzone-manifest-demo/#demo. As a fallback when storage is blocked, it appends ?guest=Dev%20Okafor&waiver=signed to that link (before the #demo), which this board also reads.

Guest names are matched case-insensitively against this board's fictional tandem guests. Status values signed, complete, completed and done count as a completed waiver.

Snippet for the waiver demo file

The waiver demo is a separate file and cannot be edited, deployed or confirmed from this page. This is the code to apply there. It assumes a form with id waiver-form and a text input named guest, plus an anchor with id continue-link that starts hidden. Adapt the ids and field name to that file.

Markup the snippet expects (adjust to the existing page):

<form id="waiver-form">
  <label for="w-guest">Guest name</label>
  <input id="w-guest" name="guest" required>
  <button type="submit">Sign sample waiver</button>
</form>
<a id="continue-link" href="/dropzone-manifest-demo/#demo" hidden>
  Continue to manifest board</a>

Script:

var KEY = "fs-demo-tandem-waiver";
var BOARD = "/dropzone-manifest-demo/";
var form = document.getElementById("waiver-form");
var link = document.getElementById("continue-link");

form.addEventListener("submit", function (e) {
  e.preventDefault();
  var guest = form.elements["guest"].value.trim();
  var stored = false;
  try {
    localStorage.setItem(KEY,
      JSON.stringify({ guest: guest, status: "signed" }));
    stored = true;
  } catch (x) {}
  link.textContent = "Continue to manifest board";
  link.href = stored
    ? BOARD + "#demo"
    : BOARD + "?guest=" + encodeURIComponent(guest) +
      "&waiver=signed#demo";
  link.hidden = false;
  link.focus();
});

For the Dev Okafor flag to clear, the guest name entered in the waiver demo must be Dev Okafor (any letter case). Other names are stored but do not match a board guest. If the waiver page's CSS sets display on the link, make sure it does not override the hidden attribute. Place the script after the form and link in the HTML, or wrap it so it runs after the page has loaded.

Verify after deploying the waiver demo

Do these steps on the live site, in one browser tab session, after the waiver demo change has been deployed:

1. Press Clear shared sample record below. Dev Okafor's flag should show missing.
2. Press Check the three demo paths. Each path should report HTTP 200, and the waiver page should show the markers it contains.
3. Open the tandem waiver demo in this same tab, enter Dev Okafor, submit, then use "Continue to manifest board".
4. On the board, the waiver panel should read "From waiver record" for Dev Okafor with a green "Waiver complete" chip. Open this section again and press the path check once more to refresh the gate below.
5. Tick the confirmation in the verification gate and press Mark handoff verified. It only enables when every condition holds.
6. Optional, for the storage-blocked fallback: press Open fallback link test. The board should show the flag cleared with the source "link". This does not count toward verification.

Until you have run these steps, treat the handoff as unverified. This page cannot run them for you and does not pre-mark itself as verified.

Check the handoff

These checks run in your browser when you press a button. Results describe what your browser sees right now. They are not a recorded test.

Verification gate

The gate keeps its progress in this browser tab's session storage only. The sequence matters: clearing the record resets it. The test button's record never counts, and neither does the URL fallback.

True todayThis demo holds no operator data. It uses fictional names and keeps nothing after you reload.

PlannedOur intent is that the dropzone owns its data, can export it, and can ask for deletion. We would write this into a pilot agreement. No production system exists yet, so there is no hosting or retention policy to point to.

True todayNot in the demo. There is no import feature and no file upload on this page.

PlannedThe likely approach is a CSV import with column mapping and a preview before anything is saved. We would start from a sample export with redacted or dummy rows. We have not confirmed compatibility with any specific software's export format.

True todayThe board makes no network calls while you use it, so it keeps working once the page has loaded. The only exception is the optional path check in the builders' section above, which fetches the three demo pages when you press it. The demo does not store data, so a reload resets it.

PlannedReal offline support is not built. The goal would be to queue changes on the device and sync when signal returns, with clear handling of conflicts. We would design and test it with you on your field before calling it reliable.

No claim is made. The demo is a workflow prototype. Compliance requirements would be reviewed with you and the right advisers, not assumed.

That is what a pilot conversation is for. We are not claiming parity with any existing product. We would start by learning which parts of your manifest day cost you the most time and decide together whether a small pilot makes sense.