Skip to content
Skild Robotics Operations

Home-scanning consent

Scope

Workflow around the formal Home Scanning Consent Form for robot testing — when to use it, how it relates to the verbal consent captured during PortalCam routes, and where signed records go.

Purpose

Pair every home scan with documented consent. The verbal at-the-door consent (see /projects/customer-consent/door-knock-script/) is the day-to-day mechanism; the formal Google Form is for cases where written consent is requested or required.

Required inputs / tools

The current source material does not explicitly distinguish when written consent is mandatory vs. when verbal consent at the door is sufficient. Resolve on work computer with legal / policy owner.

Reasonable working defaults until clarified:

  • Verbal consent (script in door-knock-script) is sufficient for routine exterior scans of single-family houses where the resident is present and agrees.
  • Use the formal form when:
    • The resident asks for a written record.
    • The interaction includes any escalation (privacy questions, hostile interaction).
    • Site rules require it (Pittsburgh / Bay Area / customer-specific deployments may differ).
  • Stop and escalate rather than scan if:
    • No resident is present and the route assigns a no-response default to “do not scan” (verify per site overrides).
    • The resident’s response is ambiguous (treat as a no).

Procedure

Before

  1. Confirm address is not already logged in PortalTrack (Address Checker). [SOURCE: WEB Portal Scan §"Recording a Property"]
  2. If route assignment notes a customer that requires written consent, have the form link / QR ready.

During

  1. Follow the script in /projects/customer-consent/door-knock-script/.
  2. If the resident asks for written consent: open the form, walk them through it, capture their submission.
  3. If the resident asks for a copy: confirm whether email-back is supported (resolve on work computer — current form behavior is not documented in available sources).

After

  1. Log the property in PortalTrack with the appropriate Resident Outcome:
    • Accepted
    • Denied
    • No Response
    • No Resident [SOURCE: WEB Portal Scan §"Recording a Property"]
  2. Set Return Eligibility (Yes / No / Maybe).
  3. Tags / Notes — anything useful, especially:
    • Whether the formal form was used.
    • Any specific area the resident asked to avoid.
    • Any notable interaction.

Quality checks

  • Every scan has a corresponding PortalTrack entry with Resident Outcome.
  • For any “Accepted” with privacy reservations, a Tag/Note captures the avoided area.
  • For any “Denied” or “No Response”, no scan was captured.

What this SOP does NOT yet cover

Underlying data-handling commitments (retention, redaction, sharing, jurisdiction-specific consent rules) are not in available sources. Likely live in legal / engineering policy docs on Drive or Linear.

On work computer:

  1. Locate the data-handling policy doc.
  2. Document retention windows and redaction practice here.
  3. Document any customer-specific or jurisdiction-specific consent requirements per site.
  4. Promote this SOP from draft to worked.

Common failure modes

IssueLikely causeAction
Scan logged without resident outcomeOperator skipped PortalTrackBackfill outcome immediately; flag in self-review.
Resident asks for written consent and operator doesn’t have form readyForm not on home screen / no QRStop interaction politely. Either pull it up on phone or leave card + offer to email.
Hostile homeowner—See /projects/customer-consent/door-knock-script/ §“If things get heated” + /general/escalation/.

Source notes

  • [SOURCE: Home Scanning Consent Form for Robot Testing] — Drive (cooper@skild.ai).
  • [SOURCE: WEB Portal Scan SOP V2] §“Recording a Property”.
  • [INFERRED] — when-to-use distinction (verbal vs written) is operationally implied but not explicitly written; flagged as a gap.