Agreements Hub
Send, sign, counter-sign and track every piece of client paperwork — NDAs, MSAs, master agreements — from a single hub. Audited, sealed, and stored.
What the Agreements Hub does
The single place to manage every signed agreement with your clients.
The Agreements Hub lives at Admin → Agreements. It replaces the old "email a PDF, ask them to sign and scan it back" workflow with an audited, branded e-signature flow where every event is logged, every signed copy is sealed with a hash, and Aligra counter-signs automatically (or manually with one click).
Reusable bodies for NDAs, MSAs, terms etc. with {{merge tags}}
Pick a client & contact, pick templates, customise, send
Every view, sign, decline, IP, user-agent — exportable as JSON or PDF
Locked once countersigned; SHA-256 hashed so tampering is detectable
The hub is gated by a feature flag (nav_v2_enabled in system_settings) so it stays hidden in production until you flip the switch. See your deploy notes for the exact SQL.
The starter library
Pre-built templates you can adopt, edit, or fork.
TempClock ships seven starter templates covering the most common paperwork: Mutual NDA, Master Services Agreement, Worker Confidentiality, Data Processing Addendum, Hardware Loan, AWR Acknowledgment, and a System Use Acceptance. Each has placeholder merge tags so the same template can be sent to dozens of clients.
Browse the starter library
Go to Admin → Agreements → Templates. Each starter row carries a small STARTER badge. Click any row to preview its body and merge tags before adopting it.
Customise without losing the starter link
Edits to a starter template create a new version. The "Reset to starter" button on the editor toolbar reverts your customisations and pulls in any upstream improvements TempClock ships in a later update.
Compare against upstream
The Diff vs starter button shows exactly which lines you've changed. Handy before a compliance review or when you want to know if it's safe to reset.
Publish
Templates start as Draft. Toggle to Active before the send wizard will let you pick them. Archived templates stay in the library for audit but can't be sent again.
Merge tags live inside {{ }}. Common ones are {{client.name}}, {{contact.name}}, {{date.today}}, and your custom-field tags like {{custom.deal_value}}.
Sending paperwork — the 4-step wizard
How to ship one or more documents to a client contact.
Click the orange + Send paperwork button from any Agreements page. The wizard walks you through four screens and dispatches the email at the end.
Step 1 — Client & contact
Type to search your client list. Once you pick a client, the wizard shows their saved contacts underneath. If the right contact isn't there, hit + Add contact: name, email, role, and whether they are the primary contact for this client.
Only active contacts can receive paperwork — deactivated ones stay in the contact list for audit but won't appear here.
Step 2 — Pick templates
Choose one or more active templates to bundle into a single send. Templates are filtered by category so it's easy to find what you need. The wizard previews the merge-rendered body using the chosen client + contact so you can see exactly what they'll get.
Step 3 — Customise
Each template can have custom fields defined by you (e.g. deal value, contract start date). The wizard surfaces them here as form inputs. You can also write a short cover note that appears at the top of the recipient's landing page — useful for context like "Please sign by Friday so we can kick off Monday."
Step 4 — Review & send
The final screen summarises everything: recipient, documents, custom field values, expiry date.
Hit Send and TempClock dispatches the email and logs a sent event
against every doc in the bundle.
Tracking sends — three views
Overview for the bird's-eye view, per-client for detail, activity log for forensics.
Overview (Admin → Agreements)
One row per client. Shows their primary contact, how many docs are awaiting signature, how many they've signed, and when they last interacted. Use the search to narrow to one client; click any row to open their detail page.
Four stat tiles at the top: Clients on file, Awaiting signature, Viewed today, Expiring < 7 days.
Per-client detail
Click a client to see Awaiting docs (amber panel at the top), Signed docs (with download links), the client's contacts, and a live activity timeline on the right column.
From here you can re-send a link, copy the recipient URL, jump to countersign, or download the sealed PDF.
Activity log (Admin → Agreements → Activity)
Every event across every send, filterable by event type, client, and date range. The export buttons on each row give you a JSON or PDF audit certificate for that send — handy if a client questions a signature.
Send was drafted
Email left your server
Recipient opened the link
Recipient signed a document
Aligra counter-signature applied
Final PDF generated & hashed
Recipient declined the bundle
Link past its expires_at
Hash mismatch on view (rare, flagged)
Reminder email fired
What the recipient sees
A simple, mobile-friendly signing flow — no account required.
The recipient receives an email with a single button. Clicking it opens a branded page on your domain at
/sign/<token>. There\'s no login, no app to install — just the documents.
Paperwork from Aligra Recruitment Ltd
Hi Sarah, please review and sign the documents below.
The signing pages carry no tracking cookies, no analytics, no admin chrome. They're intentionally calm and minimal so the recipient stays focused on the documents.
Counter-signing — auto vs manual
How Aligra's signature gets applied to bundles that need it.
Templates carry a signing mode: recipient_only, aligra_only, or both. For "both" templates, the recipient signs first, then Aligra counter-signs to finalise.
Auto countersign (recommended)
Templates with Auto countersign enabled apply your on-file Aligra signature immediately after the recipient signs. The doc transitions signed → awaiting_countersign → sealed in seconds and the recipient receives the sealed PDF by email.
Manual countersign
Templates without auto-countersign sit in the Admin → Agreements → Countersign queue until you act on them. Each row offers two buttons: Apply on-file signature (instant) or Draw new (signature pad modal for a fresh signature).
This is useful when you want a senior person's name on a high-value contract rather than the default signatory.
Sealed PDFs are locked. The final hash is stored in the DB and recomputed at every download — if the file on disk has drifted by even a byte, the download is blocked and a tamper_attempt event is logged.
Expiry & renewals
How long links stay live, and what happens at expiry.
Link expiry
Each send has an expires_at timestamp. The default is 30 days from dispatch but you can change it per send. After expiry the link returns a friendly 410 and the recipient is told to contact the sender.
Auto-expire sweeper
A cron job (cron/agreements_sweep.php) runs hourly and flips any past-due
sends to expired, logging an expired event. The same cron sends
reminder emails for sends approaching expiry (default: 7-day warning).
Renewing an expired doc
Expired sends can't be revived — that would break the audit trail. Instead, open the client page and use the send wizard again to dispatch a fresh bundle. The previous expired send stays visible in the activity log.
Templates that need yearly renewal (NDAs, GDPR DPAs) work best with a 365-day expiry so the cron quietly reminds you and the recipient at the right time.
The Aligra signature setup
Upload a one-off image so counter-sign happens with a click.
For auto-countersign to work TempClock needs an on-file Aligra signature. Set this once on Admin → Agreements → Settings.
Upload the image
Use a transparent PNG of the signatory's real signature, ideally 600×200px at 300 dpi. Drop it into the file picker on the settings page.
Set the signatory name
This appears next to the image in the sealed PDF. Use the legal name as it appears on the signature itself, e.g. James Adair, Managing Director.
Test it
Send yourself a test send (see below). After you sign it, TempClock should auto-countersign within a second and you'll see the sealed PDF in your inbox.
Until the on-file signature is configured, the countersign queue will warn you in yellow and offer the Draw new option. Either works — the on-file version is just faster.
Test sends
How to walk through the recipient flow end-to-end without writing to production data.
Every template has a Send test button on the editor that dispatches a real
email to you, marked as is_test=1. Test sends:
Use test sends when adding or editing a template, when onboarding a new admin user, or after any deploy that touched the signing pages. They're the cheapest sanity check.
Know who turned up — and pay every hour right.
Face-verified clock-ins, live geofencing and payroll-ready timesheets in one system. Tell us how your shifts run and we will show you how it fits.
UK-hosted · Set up in under an hour · No app for your staff