What I send your IT team
- The exact DNS records to change (usually an A record for the bare domain and a CNAME for www), with the old values noted for rollback
- A security header report for the preview link, so they can verify it themselves
- Where each form's submissions are stored and who receives them
- Who holds the domain, the repository and the hosting account, and how to put them in your company's name
- Netlify's compliance documents for their file
Limits worth knowing
Straight answers before you decide, because your IT team will ask:
- SLA. Netlify's Pro plan has no uptime SLA. Enterprise includes one, at custom pricing.
- Request logs. Per-request log export is an Enterprise feature on Netlify. If you need request logs, Cloudflare can sit in front of the site; its per-request logs need the Business or Enterprise plan.
- Sensitive uploads. If résumés or other personal data must stay inside your own systems, the form can route there instead of Netlify.
If any of those are requirements, that's what the advanced security tier is for.
An engineering client's IT and security lead reviewed this setup on a call and approved the static approach over WordPress.