E-Sign is the signing layer inside Pitch N Hire — not a separate app you export to. An offer is built against the approved band in a block editor, routed to signers in order, and filed on the candidate record with the signer identity, timestamp and document version attached.
Offer, appointment, confirmation, promotion or transfer, experience, relieving, and self-service certificates.
Draft, sent, accepted, declined, revised and withdrawn — each recorded rather than overwritten.
The unsigned and the signed copy, so the completed file never overwrites the original.
Signing is first-party. No external e-signature provider is integrated or named.
E-Sign is a capability of two modules rather than a separate purchase: offer management inside the applicant tracking system, and HR documents inside the HRMS. We name it separately here because buyers look for it separately, and it is worth being clear about what it is — the group sells it as part of the hiring stack, and Pitch N Hire has never priced it as a standalone product.
On the hiring side, an offer is built in a drag-and-block editor — company header, offer title, paragraphs, a compensation table, key dates, a policy notice, a signature block and accept-or-decline buttons — with dynamic variables that fill from the candidate, role and compensation records when it is sent. Offers carry states: draft, sent, accepted, declined, revised or withdrawn. Revising reissues under the same offer and marks the record revised; deleting is neither, and should only ever apply to something created in error.
On the HR side the same flow issues offer, appointment, confirmation, promotion, transfer, experience and relieving letters from versioned templates populated from the employee record. You set who signs and in what order, reminders go out on the schedule you configure, and when the last signer completes, the signed file is filed on the record along with the trail of who signed, when and from where. Both the unsigned and the signed version are retained.
What the signing flow actually consists of, on both sides of the joining date.
A block editor for branded A4 documents: header, title, paragraphs, a compensation table, key dates, policy notice, bullet lists, a signature block, page breaks and accept-or-decline buttons. Arrangements save as templates and load next time.
Fields covering the candidate, company, role, dates, people, links and compensation, filled from the record when the offer is sent. The compensation figure comes from the band that was approved at requisition, not from a number retyped into a document.
You set who signs and in what order — typically the authorised signatory, then the employee. Each signer gets a link, the next is notified on completion, and reminders go out on your schedule. Everything in flight is visible in one list rather than in somebody's sent folder.
Signer identity, the signing timestamp, the document version and a full trail — which is the evidence an electronic signature relies on. When the last signer completes, the signed file lands on the record.
Templates and policies are versioned, so you can see which wording a person actually confirmed and when it last changed. Reissuing a revised policy does not clear the record of who confirmed the earlier one.
Visas, work permits, fixed-term contracts, certifications and identity documents tracked to their expiry dates, with access set per document type and every open, download and share logged with the user and the timestamp.
The five steps of the e-sign flow, as the HR documents module publishes them.
The letter is built from a versioned template with merge fields populated from the record, and the draft can be reviewed before it goes anywhere.
Decide who signs and in what sequence. For most letters that is the authorised signatory first and the employee second; approvals on the offer itself have already been recorded against the requisition.
Each signer receives a link, signs, and the next is notified. Reminders fire on the schedule you configure, and the status of every document in flight sits in one list.
When the last signer finishes, the signed file is placed on the record with the trail of who signed, when and from where. Both versions are retained — nothing is overwritten by the completed copy.
A stalled document can be cancelled and reissued. An offer with wrong terms is revised, which produces a new document under the same offer and marks the record revised — never resent as though nothing happened, and never deleted.
Four groups touch this, and the largest of them by headcount never logs into anything else.
Recruiters and talent acquisition managers building the offer against the approved band and watching its status from the same pipeline view they were already in.
HR executives and shared-services leads producing appointment, confirmation, transfer, experience and relieving letters at volume from templates that carry your own wording.
Hiring managers, finance approvers and directors who sign in a defined order — and who benefit most from the compensation figure being visible to a deliberately short list of people.
The biggest group. Self-service requests for an employment confirmation, address proof, salary certificate or bank and visa letter move straight into the same flow, so they receive a completed document rather than a draft.
Two of these are the most important sentences on this page, and both are the vendor's own.
The flow captures signer identity, the signing timestamp, the document version and a full trail, which is the evidence an electronic signature relies on. Whether a particular document must be signed in a particular way varies by jurisdiction and document type, so confirm your own requirements before moving a format across.
Yes — the offer document can carry accept and decline buttons, and the status on the record changes when they respond. Treat that as a recorded response rather than a legally executed signature; the two are different, and some legal teams accept only the second.
Yes. Templates are your wording with merge fields inserted where record data belongs, and several templates can exist for the same letter type, split by entity, location or employment type.
Revising reissues the offer with updated terms and marks the record revised, under the same offer. Withdrawing pulls back an offer already sent. Deleting is neither — it removes the record entirely, and should only ever apply to something created in error.
Against the employee or candidate record inside the platform, with access governed per document type and every open, download and share logged. Bulk export is restricted separately from viewing.
Yes, matched to employee records by employee code. Rows that match no record are returned rather than filed against the wrong person, so a migration cannot quietly misplace somebody's documents.
Talk to the group and a senior lead scopes it in writing, or go straight to the product's own site and look at it yourself. Neither route commits you to the other.
Name the number you need to hit. A senior lead replies within one business day and a costed plan follows within three working days.
Pitch N Hire's own site, where this lives inside offer management and HR documents — with the full letter library and the evaluation questions worth asking.
Everything the group sells around E-Sign — the company that delivers it, the nearest siblings, and the full list.