## People sourcing pilot worksheet

This proposed worksheet helps scope a pilot. It is not a contract and contains no filled results.

### Scoping questions

- What role brief, seniority and geography define the target?
- Which organizations or organization types are in scope?
- Which public source list is permitted, and must each row retain an evidence URL?
- Which fields are required beyond `profile_url`, `role`, `organization`, `observed_at`, `evidence_url` and `match_status`?
- What refresh interval and observation-time format do you need?
- What output format should be reviewed: JSON, CSV or another agreed format?
- What expected volume and delivery boundary should be assessed?
- What evidence is enough to mark a row `accepted`?
- Which identity conflicts or missing fields must enter the review queue?
- What permitted-use, deletion, correction and retention rules apply?

### Acceptance worksheet

- [ ] Every accepted row has a profile URL from a permitted public source
- [ ] Every accepted role and organization value has supporting evidence
- [ ] Every row includes an evidence URL and observation time
- [ ] Identity ambiguity enters a review queue
- [ ] No sensitive trait or private contact field is inferred
- [ ] `accepted` means eligible for human review, not a hiring recommendation
- [ ] Output format and field names match the agreed scope
- [ ] Deletion, correction, permitted use and retention rules are recorded

### Pilot output to agree

Proposed output: a people sourcing file with public professional evidence, dates and match statuses, plus a separate identity review queue. ProxyLane must confirm feasibility, scope, price and these acceptance rules before any work or purchase terms are agreed.