Agent setup
Set up Document / PDF Intake Ledger.
Turn repeated PDFs, scans, and document folders into one structured ledger with missing fields and source trace.
First proof
Five sample documents extracted into a clean table with confidence notes, missing fields, and source links.
Queued job
Intake-to-first-proof packet with source manifest, first run steps, acceptance tests, and approval boundary.
Kickoff pack
Client-ready kickoff message, source request, 48-hour plan, and operator checklist.
What we need
- Document samples
- Target fields
- Naming rules
- Exception examples
- Review owner
Accepted samples
- five PDFs or scans
- target field list
- example completed report
- exception examples
Role playbook
Choose owner, operator, or technical admin mode above. The selected role is added to this setup request as a routing hint.
Owner
- First action: Approve the first proof target: Five sample documents extracted into a clean table with confidence notes, missing fields, and source links.
- Approval focus: Scope, price, payment route, external sends, connector writes, and first production run.
- Success signal: Owner can decide whether the worker saves time, reduces risk, or moves revenue before any recurring claim.
Operator
- First action: Collect the starting source pack: five PDFs or scans, target field list, example completed report.
- Approval focus: Confirm sample quality, missing fields, edge cases, and whether the first proof matches daily work.
- Success signal: Operator can repeat the workflow with less manual checking and fewer missed follow-ups.
Technical admin
- First action: Map the approved source boundary for professional services data before any connector access.
- Approval focus: Accounts, permissions, API/export path, audit logs, vaulting, and rollback plan.
- Success signal: Technical admin can explain what the worker can read, what it cannot do, and how every action is logged.