Signing, terms and clauses / Initials and date boxes
Per-page initials boxes and date fields sized for handwriting
Small boxes for a signatory to initial each page or enter a date by hand, used where every page has to be shown to have been seen.
Why this block is harder than it looks
These are the only boxes in a document sized for a pen rather than for type, and they are almost always drawn too small, because they are designed by looking at them on a screen where nobody is writing in them. The second difficulty is that an initials box has to appear on every page, which means it belongs in the page margin, and page margin content is subject to a different and smaller set of layout rules than the body.
The decisions that make it work
Reasons rather than a description of the code. Each of these is a choice that has a wrong answer, and the wrong answer is usually the default.
- Size for handwriting: 10mm of height and 25mm of width is a workable minimum for initials, and a date needs about 40mm.
- Put per-page initials in a page margin box so they repeat automatically, rather than trying to inject them into the flow of every page.
- Draw an open box or a baseline rule, not a filled tint. People write on white and a tinted box gets left empty.
- Label it once, small, outside the box. A label inside the box is written over.
- Where the date is to be handwritten, do not pre-print a format mask with slashes. It constrains the handwriting into an unreadable shape and different people fill masks differently.
- Keep the box clear of the trim area and of anything the printer cannot reach, since these are frequently printed on cheap devices with generous unprintable margins.
The fragment
Markup and the CSS it needs, and nothing else. It expects a document that already has a page rule and a base stylesheet, so paste it into one rather than opening it on its own.
<style>
@page {
size: A4;
margin: 25mm 20mm 30mm;
@bottom-right {
/* repeats on every page without touching the flow */
content: element(initials);
}
}
.initials-box {
position: running(initials);
text-align: right;
font-size: 7pt;
color: #666;
}
.initials-box .label {
display: block;
margin-bottom: 1.5mm;
letter-spacing: 0.06em;
text-transform: uppercase;
}
.initials-box .box {
display: inline-block;
width: 25mm;
height: 10mm; /* sized for a pen, not for type */
border: 0.5pt solid #999;
}
</style>
<div class="initials-box">
<span class="label">Initials</span>
<span class="box"></span>
</div>What breaks when it is built the obvious way
Making the box the height of a line of text. It looks proportionate on screen and it is about a third of the height a person needs, so the initials overflow it and the document looks like it was filled in badly rather than designed badly.
How to prove it survived pagination
Print a page and initial it with a real pen, then have somebody with larger handwriting do the same. If either set of initials touches the border, the box is too small. Then confirm the box appears on every page including the last.
Where it sits in a finished document
This page is one block. The document it belongs to has a page rule, a base stylesheet, a header and everything else around it, and repeating all of that here would make thirty pages that say the same thing. The tenancy agreement template is a complete file with this block already in it, so take that and change the fragment rather than assembling one from parts. The property doing most of the work here is covered on its own page, with the support caveats that belong there rather than here.
Frequently asked
Will this fragment work on its own?
Not as a whole document. It has no page rule, no margins and no base type, because those belong to the document rather than to the block, and duplicating them in every fragment would mean thirty copies to keep in step. Paste it into a template that already has them.
Why does it look right in a browser and wrong in the PDF?
Because a browser window is one continuous surface and a document is a stack of fixed rectangles. Nothing in a scrolling view exercises a page boundary, so every break rule in the fragment is inert until the content is paginated. Render the real thing with enough content to cross two or three boundaries, then look.
Do I need a special option on the render request for this?
No. Everything on this page is CSS and markup, which is your side of the boundary. What the render has to give you is a real page size with real margins, and after that the layout is decided by the stylesheet.
Other parts of a document
The blocks that sit next to this one, and one from the next group along so you are not sealed inside a single kind of problem.
A company registration footer that repeats on every page
Registered company name, number, registered office and any regulatory statement, set small at the foot of every page because it has to be on every page.
A prepared, checked and approved block that fits on one line
Three or four named roles with a signature space, a date and sometimes a stamp, showing who produced a document and who released it.
A revision and version marker that is visible on every page
The document's revision letter or number, its date, and often a short change note, printed so that anyone holding a copy can tell whether it is current.
A running header that shows the current section on every page
A line at the top of each page carrying the document title and, ideally, the section the reader is currently inside.
Tenancy agreement, as a complete file
The whole document with this block already in place, ready to copy and change.
@top-center and the margin boxes in paged output
The property carrying the weight here, with its real support status.
Every part of a document
The full list, grouped by the kind of problem the block poses.
Paste the fragment into the playground inside a page rule and see what it does at a real page size. That is the only way any of this gets confirmed.