HR teams running new hire onboarding through PandaDoc need nine core templates: offer letter, employment agreement, handbook acknowledgment, I-9, W-4, direct deposit authorization, benefits enrollment, confidentiality agreement, and a 30-60-90 day plan. Built right and connected through Make.com, these nine documents eliminate manual follow-up and deliver a consistent Day 1 experience every time.

Manual onboarding kills first impressions. Document chasing, version drift, and missing signatures waste hours per hire and expose the company to compliance gaps. PandaDoc solves the document layer. Make.com connects it to your HRIS, ATS, and calendar. Together they turn a nine-step paper trail into an automated sequence that fires when an offer is accepted and closes when Day 1 begins.

This guide covers each template in deployment order — the sequence that respects payroll deadlines, minimizes signature delays, and keeps compliance documents ahead of the first pay run.

Template 1: Offer Letter

The offer letter is the first document a candidate receives as a future employee, and it sets the tone for everything that follows.

Required variables: candidate full name, position title, start date, reporting manager, base compensation, FLSA classification (exempt/non-exempt), offer expiration date, and hiring manager signature block.

Build this template with a single conditional block that swaps between full-time, part-time, and contractor language based on a dropdown field set at send time. This eliminates the need for three separate templates and removes version control overhead from the HR team entirely.

Automation trigger: In Make.com, watch for a stage change in your ATS (Greenhouse, Lever, and Workable all support webhooks) to “Offer Extended.” Map ATS fields to PandaDoc variables and send the template automatically. The candidate receives a signing link within seconds of the HR coordinator updating the ATS record — no manual step required.

Connect the PandaDoc “completed” webhook back to Make.com to flip the ATS stage to “Offer Accepted” and trigger the onboarding sequence for Templates 2 through 9. Every subsequent template fires from this single event.

Expert Take

Offer letters that require candidates to print, sign, scan, and email back show measurable drop-off between acceptance and start. PandaDoc e-signature eliminates that friction entirely. If your offer letter still uses a PDF attachment, fix it before you benchmark any other onboarding metric.

Template 2: Employment Agreement

The employment agreement governs the legal relationship between the company and the new hire — compensation terms, at-will status, dispute resolution, and governing jurisdiction.

Required variables: all offer letter fields, plus governing state law, arbitration clause toggle, equity grant details (if applicable), and legal entity name.

This template requires legal review before deployment. Start from your attorney’s approved language and create PandaDoc variables only where substitution is safe: names, dates, titles, and compensation figures. Lock all substantive legal language blocks so they cannot be edited at send time.

Compliance note: Several states require specific language around non-compete enforceability, final paycheck timing, and at-will exceptions. Build state-specific conditional blocks or maintain separate templates per jurisdiction for multi-state hiring operations.

PandaDoc’s content locking and approval workflow features are essential here. No employment agreement should reach a candidate without a legal approval stamp in the audit trail.

Template 3: Employee Handbook Acknowledgment

The handbook acknowledgment documents that the employee received, read, and agreed to the current version of the employee handbook — creating the audit trail your legal team needs.

Required variables: employee name, handbook version number, handbook effective date, employee signature, and signature date.

This template is a single-page document, not the handbook itself. The handbook lives in your HRIS or intranet. The acknowledgment is the record. Embed a hyperlink to the current handbook URL so the signed document is self-contained and auditable without hunting for the right version.

Version control: PandaDoc carries a version stamp on every template. When the handbook updates, create a new template version rather than editing the existing one. Employees who completed onboarding before the update stay on the prior version; new hires get the current one. That distinction is load-bearing in employment disputes.

Schedule this template to send 24 hours after the employment agreement is signed, giving the candidate time to read the handbook before acknowledging it rather than signing blind.

Template 4: I-9 Employment Eligibility Verification

Form I-9 verifies that every new hire is legally authorized to work in the United States. Federal law requires completion within three business days of the start date — no exceptions.

Required variables: employee legal name, date of birth, address, Social Security number or alien registration number, citizenship status, and document list selections.

PandaDoc handles the signature and date fields on Section 1 (employee) and Section 2 (employer). The document review step — where an authorized employer representative physically examines identity documents — cannot be automated. Build a Make.com step that triggers a task for the hiring manager or HR coordinator to complete Section 2 in person on Day 1.

Remote hire note: For fully remote hires, an authorized representative completes Section 2 on behalf of the company. Document the representative’s name and relationship to the employer in your records. USCIS provides clear guidance on this process through its authorized representative policy.

If your team still completes I-9s on paper, that is a compliance liability PandaDoc and Make.com resolve directly and permanently.

Template 5: W-4 Federal Tax Withholding

The W-4 tells payroll how much federal income tax to withhold from each paycheck. Every new hire completes it before their first pay run — no exceptions.

Required variables: employee name, Social Security number, filing status, and withholding adjustments (Steps 2–4 of the current IRS form).

The IRS redesigned the W-4 in 2020, eliminating allowances and replacing them with dollar-amount adjustments. Any pre-2020 template in your system is non-compliant and must be replaced immediately. Audit your current template against the IRS’s published current-year version before deploying this sequence.

After the employee signs, Make.com sends the completed W-4 data to your payroll system (ADP, Gusto, Paychex) via API. Manual entry of payroll tax data is where withholding errors start — automate the handoff entirely.

State withholding: Most states require a separate withholding form. Build a parallel template for each state where you employ workers and trigger it alongside the federal W-4 based on the work location field in your ATS record.

Template 6: Direct Deposit Authorization

Direct deposit authorization gives payroll legal permission to deposit wages into the employee’s bank account and is a prerequisite for the first pay run.

Required variables: employee name, bank name, routing number, account number, account type (checking or savings), deposit percentage or amount for split deposits, and employee signature.

This template handles sensitive financial data. PandaDoc encrypts completed documents at rest. Route bank account data through PandaDoc’s secure form fields only — never through email. Make.com delivers the completed data directly to your payroll system via encrypted API connection, with no human intermediary touching the account numbers.

Send this template simultaneously with the W-4 so both payroll documents arrive and process together. Stagger them and you guarantee a delayed or failed first paycheck — the fastest way to destroy a new hire’s confidence in the company.

Expert Take

The two most common new hire payroll failures are a missing direct deposit form and a W-4 that never reached payroll before the first pay run. Sending both templates in a single Make.com sequence — triggered by employment agreement completion — eliminates both failure modes in one build.

Template 7: Benefits Enrollment Form

Benefits enrollment captures the new hire’s elections for health, dental, vision, life insurance, FSA/HSA, and 401(k) — and federal law gives employees 30 days from their start date to make elections.

Required variables: employee name, effective date, plan selections per benefit category, dependent information (name, date of birth, SSN for each dependent), and beneficiary designations.

This is the most complex template in the sequence. Build it with conditional sections that show or hide based on employment type (full-time vs. part-time) and enrollment tier (employee-only, employee plus spouse, family). A part-time employee who sees full-time-only plan options will submit incorrect elections — conditional logic in PandaDoc prevents that at the template level rather than through manual review.

Connect completed enrollment forms to your benefits administration platform (Rippling, BambooHR, Namely) via Make.com. Manual re-keying of benefits elections creates errors employees discover on their first medical claim — the worst possible moment for an HR ops failure.

Make.com automations that cover the full employee lifecycle treat benefits enrollment as one of the highest-ROI connections in the entire HR automation stack.

Template 8: Confidentiality and Non-Disclosure Agreement

The NDA protects proprietary information, trade secrets, and client data — and it is a condition of employment, not an optional add-on to negotiate after the fact.

Required variables: employee name, effective date, definition of confidential information scope, confidentiality term (during and post-employment), governing jurisdiction, and signature blocks for both parties.

Like the employment agreement, this template requires legal review before deployment. Variable fields are limited to names, dates, and jurisdiction — all substantive language is locked. Non-compete provisions within the NDA require particular care: the FTC’s 2024 non-compete rule introduced significant uncertainty, and several states (California, Minnesota, North Dakota, Oklahoma) bar enforcement entirely. Legal counsel sets the language; PandaDoc enforces it through locked content blocks.

Build a mandatory approval step into this template’s PandaDoc workflow so a legal or HR approver signs off before the document reaches the employee. That approval stamp is the audit trail that proves someone with authority reviewed the specific version the employee signed.

Template 9: 30-60-90 Day Plan

The 30-60-90 day plan sets expectations for the new hire’s first three months — documenting role objectives, success metrics, and manager commitments as a two-way agreement rather than a one-sided checklist.

Required variables: employee name, position title, start date, hiring manager name, 30-day objectives, 60-day objectives, 90-day objectives, and signature blocks for both employee and manager.

This template works differently from the compliance stack. The hiring manager drafts objectives before sending, then routes the document to the new hire for review and countersignature. PandaDoc’s comment and field-completion workflow supports this collaborative build natively — no email thread, no shared Google Doc with version conflicts.

Send it on Day 1 after the compliance documents (Templates 1–8) are complete. The 30-60-90 plan is the bridge from paperwork to performance, and its signed status in PandaDoc gives it legal and cultural weight that a verbal conversation never carries.

Expert Take

Most onboarding failures are not compliance failures — they are expectation failures. The 30-60-90 plan is the one template that directly prevents the “I didn’t know what was expected of me” exit interview answer. Making it a signed, two-way document changes the psychological contract from the first day.

Deployment Order and Automation Architecture

Deploy the nine templates in this sequence to respect payroll deadlines and signature dependencies:

1. Offer Letter — pre-hire
2. Employment Agreement — same day as acceptance
3. Confidentiality / NDA — same day as #2
4. I-9 — sent five business days before start, completed Day 1
5. W-4 and Direct Deposit Authorization — sent together, three days before start
6. Handbook Acknowledgment — two days before start
7. Benefits Enrollment — Day 1
8. 30-60-90 Day Plan — Day 1, after the compliance stack closes

In Make.com, this runs as a multi-step scenario triggered by the ATS offer acceptance webhook. Each step fires after the previous document is marked complete in PandaDoc, with a fallback reminder sequence that fires at 48-hour intervals for any unsigned document. Make.com’s HR document management scenarios provide the building blocks for the entire flow.

Store signed documents in three locations: the HRIS document vault, a Google Drive or SharePoint backup folder, and PandaDoc itself for the native audit trail. Make.com’s “document completed” webhook triggers all three storage writes automatically — no manual save required.

Build Mistakes That Kill the Sequence

Teams that build these templates in isolation — without connecting them to the broader onboarding workflow — create a prettier version of the same manual process. The twelve critical PandaDoc automation mistakes cover the full failure catalog. The three that damage new hire experience most are:

• No UAT with a real candidate flow. Every template must pass end-to-end testing with a real email address and a real signature before going to production. Reviewing the editor in preview mode does not count as a test.
• Variables without default values. If a required field is blank at send time, the candidate sees raw syntax like {{start_date}} in the document body. Map every variable to a fallback default.
• Single-scenario architecture. One Make.com scenario handling all nine templates becomes brittle. Break the flow into logical modules: pre-hire (Templates 1–3), payroll (Templates 4–6), Day 1 (Templates 7–9). Failures isolate instead of cascading.

Frequently Asked Questions

How long does it take to build all nine templates?

A well-resourced HR ops team builds and validates the nine templates in three to four weeks, working through them in the deployment order above. Each template requires user acceptance testing with a real candidate flow before going to production. Legal review of Templates 2 and 8 is the most common timeline constraint — schedule it before you start building, not after.

Do these templates work for international hires?

Templates 1, 2, 3, 7, and 9 work internationally with country-specific variable sets. Templates 4, 5, and 6 are U.S.-specific: the I-9 covers U.S. work authorization, the W-4 covers IRS federal withholding, and the direct deposit format is U.S. banking. For international hires, swap in country-equivalent identity verification, tax withholding, and banking templates and route them through the same Make.com sequence using a country-based conditional branch.

How do I version templates without breaking active onboarding flows?

PandaDoc supports template versioning natively — each template carries a version stamp. New hires entering the flow after a version change use the new template; in-flight hires complete the version that started their flow. Never edit a live template directly. Create a new version, update the Make.com module to reference the new template ID, and deactivate the old version once all in-flight documents are closed.

Where do signed templates get stored?

Make.com fires a second scenario on PandaDoc’s “completed” webhook that stores the signed PDF in the HRIS document vault (Workday, BambooHR), in Google Drive or SharePoint as a backup copy, and in PandaDoc itself for the native audit trail. Three-location storage is the minimum standard for enterprise HR compliance and the baseline 4Spot builds to on every client engagement.