People team
Sees every acknowledgment in the portal.
- Pages
- Home, Policies, Acknowledgments, Who's read what, Deadlines
A policy acknowledgment portal is where the people team publishes each policy as a file, gives every employee a deadline to read it, and sees name by name who hasn't yet. Anyone still outstanding gets a reminder as the deadline nears.
Pattern: RequestsDescribe it to EachEntry
“When we roll out a policy, every employee has to read it by a deadline. The people team needs to see who hasn't done it yet and remind them.”
Policies
| Information security policy | Security | 1 file | Oct 14, 2026 | Published | |
| Customer data handling (CCPA) | Security | 1 file | Oct 21, 2026 | Published | |
| Hybrid work policy | Ways of working | 1 file | Oct 22, 2026 | Published | |
| Code of conduct | Conduct | 1 file | Sep 29, 2026 | Published | |
| Workplace health and safety | Health and safety | 2 files | Sep 14, 2026 | Published | |
| Menopause support policy | Ways of working | 1 file | — | Draft | |
| Expenses policy | Finance | 1 file | — | Draft | |
| Travel and expenses (old) | Finance | 1 file | Mar 29, 2024 | Retired |
Showing 1–8 of 8
In plain English
EachEntry gives every people team and employee a sign-in of their own. Each employee sees only their own acknowledgments. It covers publish policies & see who hasn't read them. Acknowledgments, policies, key dates and who to ask live in EachEntry's own database, so there's no spreadsheet to keep in sync.
What it does
Policies lived as attachments on an all-staff email, so which copy people actually read depended on how far back they scrolled. In EachEntry the people team adds each policy with its category, effective date and the document itself, and marks it Published when it's live. Employees open the file in the portal instead of searching their inbox for "final".
Finding out who had read the new security policy meant cross-checking email read receipts against the staff list. In EachEntry each employee has a row per policy with a deadline and a status, so the people team filters to Outstanding and has the list in seconds. No more "reply all to confirm you've read this".
Chasing stragglers meant a string of increasingly polite all-staff emails. Each employee's row in EachEntry carries a deadline and a reminder date, and anyone still marked Outstanding gets a reminder in the portal and by email two days before the deadline. The people team stops writing "gentle reminder" subject lines.
Every person signs in to their own view. This is what each role in the demo gets.
Sees every acknowledgment in the portal.
Sees only their own acknowledgments.
The tables and fields EachEntry sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How EachEntry builds a portal
Upload and view files on the record they belong to, not in a folder named FINAL v2.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Search, filters, sorting, inline add and edit. The spreadsheet, minus the sharing accident.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. EachEntry sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and EachEntry builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited employees.