Do not let the agent classify the relationship
Contractor agreements can touch worker classification, payment terms, IP, confidentiality, and tax workflows. Those are human and counsel decisions. The agent should not decide whether someone is properly treated as a contractor.
The agent's role starts after the organization has selected the right approved template for the situation.
Use variables that are easy to inspect
The dry run should show the contractor name, email, company name, effective date, role or project label, and any other approved variables. If a field requires judgment, do not hide that judgment inside the agent prompt.
This keeps the template reusable without pretending every contractor relationship is the same.
- Recipient name and email.
- Company legal name.
- Effective date.
- Project or role label.
- Compensation fields only if already approved.
- Webhook metadata for onboarding.
Store the signed agreement where onboarding can find it
After signature, the workflow should store the signed PDF and hash next to the contractor record. The agent can then report that the agreement is complete and the next onboarding step can proceed.
This is the point of using an API instead of ad hoc email attachments: the signed record becomes structured workflow state.