How to require initials on every page
Requiring initials on every page means placing an initials field at the same spot on each page of a document, so the signer confirms they reviewed that specific page rather than only signing once at the end. Done manually, that can mean a signer typing or drawing their initials ten separate times for a ten-page document — which is exactly the kind of repetitive step that automatic initials propagation is built to remove.
Why initials on every page matter
A single signature at the end of a document proves the signer accepted it as a whole, but it doesn't show they actually reviewed each individual page. For longer contracts, requiring initials on every page gives a clearer record that the signer went through the document section by section, not just the signature block at the end.
Positioning initials fields manually
When preparing the document, you place an initials field wherever you want the signer to confirm that specific page — typically in a consistent spot (a corner, a margin) so it's easy for the signer to find on each page as they go.
Letting initials fill in automatically
Rather than making the signer type or draw their initials separately on every single page, a signing platform can detect that the same signer has multiple initials fields in the same document and, once they complete the first one, automatically apply the same initials to the rest — while still keeping each one as its own recorded field completion in the audit trail, not a single blanket action. This cuts a ten-page, ten-initials document down to one real action from the signer's perspective, without removing the page-by-page record.
What the signer actually experiences
The signer completes the first initials field as normal — drawing or typing their initials once. From there, the remaining initials fields for that same signer fill in on their own, with a brief notice showing how many fields were just completed, and an option to undo it if that was done by mistake. If the signer edits one of the auto-filled fields individually afterward, that field becomes independent again, without affecting the others that are still linked.
Does this work for signatures and dates too, not just initials?
The same propagation principle can extend to other repeated fields for the same signer with a matching label — a repeated signature field, a signing-date field, or a repeated text field like a printed name. For a full signature specifically, it's common for the platform to ask for a one-tap confirmation before applying it to the other instances, since a signature carries more weight than an initial.
Can the sender turn this off?
Yes — automatic propagation across repeated fields is typically on by default, since it's what most signers want, but a sender can turn it off for a specific document if they have a reason to require the signer to complete every repeated field individually.
This still produces a real record for every page
It's worth being clear about what propagation does and doesn't change: every initials field, including the ones filled in automatically, is still recorded as its own completed field in the audit trail, tied to the same identified signer and timestamped individually. Propagation removes repetitive manual action, not the underlying record.
When requiring initials on every page actually makes sense
Not every document needs page-by-page initials. For a short agreement where the signature block already covers the whole document's acceptance, per-page initials can be unnecessary friction. They tend to matter most for longer contracts where you want evidence the signer reviewed each specific section — a multi-page lease with distinct clauses on different pages, or a policy document where you want confirmation the reader got past page three, not just that they scrolled to the signature line at the end.
Initials vs a full signature on each page
Initials and a full signature serve different purposes within the same document. A full signature, usually placed once (or on a small number of key pages), represents the signer's overall acceptance of the document. Initials, placed on every page, represent confirmation of that specific page's content — they're a lighter-weight mark, which is part of why automatic propagation matters more for initials than for a full signature: asking a signer to draw a complete signature ten times would be excessive, but confirming they want the same initials repeated is a smaller ask, which is also why many platforms ask for a one-tap confirmation before propagating a signature but not before propagating initials.
Troubleshooting: initials not propagating as expected
If initials fields aren't filling in automatically across pages, check that each field is assigned to the same signer and that the fields were placed as the same field type consistently — a field accidentally configured as a different type, or assigned to the wrong signer, won't be recognized as part of the same repeated group. Reviewing the field list before sending the document is the easiest way to catch a mismatch like this before it reaches the signer.
Combining initials with other repeated fields
Initials are often placed alongside a repeated date field — for instance, a "date reviewed" field on each page alongside the initials. When both are configured for the same signer with a consistent label, both can propagate together once the signer completes the first instance of each, keeping the page-by-page confirmation pattern consistent without requiring separate manual entry for each field type.
Deciding where on the page to place the initials field
Consistency in placement matters more than the exact spot you choose. A corner that's free of body text on every page — commonly the top or bottom right — tends to work well across different document layouts, since it avoids overlapping with content that varies in length page to page. Placing it somewhere that shifts position relative to the text (say, directly under the last line of each page) can mean the field lands awkwardly on pages with less content, which is a minor but avoidable source of a messy-looking signed document.
Set this up on your document
Esignapi positions initials fields wherever you place them in the document, with automatic propagation across repeated fields turned on by default for a smoother signing experience.
Frequently asked questions
Does automatic initials propagation reduce the legal weight of the signature?
No — each propagated field is still individually recorded in the audit trail as a completed field tied to the identified signer, with its own timestamp. The feature changes how many manual actions the signer takes, not what gets recorded.
Can I require initials for only some pages, not all?
Yes, you place initials fields only on the pages that need them — there's no requirement to add one to every page if your document doesn't call for it.
What if different signers need to initial different pages?
Each signer's fields are configured independently, so one signer can have initials fields on different pages than another signer on the same document.
Can a signer undo an auto-filled initials field?
Yes, immediately after the fields are auto-filled, the signer typically sees an option to undo that action, which reverts those fields back to incomplete.
Does this feature work the same way on mobile?
Yes, the signing experience, including initials placement and automatic propagation, works the same way from a phone browser as from a computer.