If you search for Companies House identity verification deadline, PSC verification requirements 2026, or ACSP verification tracking, you mostly land on official guidance. That is useful for the rule itself. It is less useful when the real question is operational: how does a firm keep dozens of client companies, directors, PSCs, owners, blockers, and due windows visible without rebuilding the same spreadsheet every week?
This guide is for that practical layer. It is not legal advice, not an ACSP registration guide, and not a substitute for the official Companies House wording. It is a checklist for building a verification tracker that still works once the client portfolio gets large.
If the immediate question is which role has which due window, start with Companies House Identity Verification Deadline for Directors and PSCs and then use this page as the operating checklist.
What a Companies House verification tracker needs to answer
The useful tracker is the one that answers these questions before a partner, manager, or client asks for an update.
Who needs to act right now?
Which role is still outstanding: director, PSC, or both?
Which due window applies to that role?
What is blocked or waiting on a client?
Who owns the next step inside the firm?
What proof exists that the team reviewed and followed up?
Companies House identity verification deadline in 2026: there is no single portfolio-wide date
In practice, there is no one deadline column that covers the whole portfolio. The trigger depends on the role. That means a workable tracker needs to support several due patterns at once rather than one vague field called deadline.
The operational model below is the practical shape many firms need to track across directors and PSCs.
Director obligations Use the next confirmation statement due date as the operational deadline. Keep the next made-up date visible as well, because it affects related PSC timing.
PSC who is also a director Track a separate PSC obligation. The working window starts the day after the confirmation statement date and lasts 14 calendar days. Filing early does not move that window.
PSC who is not also a director Track the first 14 days of the PSC's birth month as the working window. This is a different obligation path from the director-linked PSC case.
PSC added on or after 18 November 2025 Treat it as a separate new-role window and track the first 14 days from the role start date where the source record supports that timing.
The important operational point is simple: if the same person is both director and PSC at the same company, the tracker still needs two obligations.
PSC verification requirements in 2026: what breaks spreadsheets first
The reason PSC verification requirements 2026 become messy in practice is not just the rule itself. It is the fact that PSC work often sits beside director work, confirmation statement timing, and client follow-up inside the same team queue.
If the immediate question is only the PSC side, use PSC Verification Requirements 2026 for Small UK Firms for the narrower breakdown before coming back to the broader tracker workflow.
A single person can have two obligations at the same company If someone is both a director and a PSC, the tracker should keep two separate obligations. Completing one should not silently complete the other.
PSC-only rules and director-linked PSC rules are not the same A birth-month window is not the same thing as a post-confirmation-statement window. A useful tracker must separate those paths clearly.
New PSC roles need visibility, not guesswork When a new PSC appears, the team still needs a manual workflow for owner, blocker, and completion state even if the public data does not expose final completion clearly.
Unsupported or messy PSC records should be surfaced Corporate PSCs, protected-information cases, and weak source data should be flagged for review rather than quietly dropped from the operational picture.
ACSP verification tracking checklist
If you are running ACSP verification tracking across a client book, this is the checklist that usually matters more than another rules summary page.
Keep one live portfolio list of tracked companies If the company list lives in three spreadsheets, the verification tracker will never be reliable. The company set itself needs one source of truth.
Track obligations at role level, not just person level The same person can be a director and a PSC. The tracker needs to show the role and the rule path, not just the person's name.
Store confirmation statement dates for every tracked company Without the next confirmation statement due date and made-up date, the team cannot manage director obligations or the linked PSC timing confidently.
Separate PSC window types instead of using one generic deadline column PSC birth-month windows, post-confirmation-statement windows, and new-role windows should not be collapsed into one vague due-date field.
Keep owner, blocker, and next step visible on the obligation A tracker is only useful when it shows who owns the work, what is blocked, and what needs to happen next without opening another document.
Review new windows and overnight changes every day The real operating rhythm is not a monthly spreadsheet tidy-up. It is a daily review of what changed, what opened, and what still needs attention.
Do not auto-complete obligations from assumptions The tracker should not mark work complete just because the team expects it to be complete. Completion needs an explicit status change.
Surface unsupported cases as needs-review Messy real-world cases should create review work, not hidden gaps. Silent omission is worse than an explicit exception queue.
Keep exportable proof of what the team reviewed If a partner, client, or reviewer asks what was in scope and what is still open, the answer should come from a reusable artifact, not a rebuilt status note.
Where Entity Watch fits
Entity Watch is not an identity verification service, not an ACSP registration tool, and not a filing agent. It sits on top of Companies House public-register data and gives firms a shared workflow for the part that usually becomes manual: what changed, who needs to act, what is blocked, and what proof exists right now.
In practice, that means watchlists for tracked companies, separate director and PSC obligations, owner and blocker fields, recent activity, a daily review layer, and reusable proof output when someone asks for a current status pack.
Common questions
What is the Companies House identity verification deadline in 2026?
There is not one single portfolio-wide date. In practical tracking terms, directors usually tie to the next confirmation statement due date, while PSC obligations depend on whether the PSC is also a director, the PSC's birth-month window, or a new-role window. Use the official Companies House guidance for edge cases and legal interpretation.
What are the PSC verification requirements in 2026?
Operationally, firms usually need to track separate PSC paths: PSC after confirmation statement, PSC birth-month window, and new PSC role timing where relevant. The important workflow point is that PSC work should not be collapsed into the same rule as director work.
Do ACSPs need a separate verification tracking process?
If the firm only handles a very small number of companies, a light process may be enough. Once the client portfolio grows, ACSP verification tracking becomes a portfolio-management problem: owners, blockers, due windows, and proof all need to be visible in one place.
Can Entity Watch verify identity documents, submit personal codes, or act as an ACSP?
No. Entity Watch is not an identity verification service, an ACSP registration tool, or a filing agent. It is an alerts and workflow layer that helps firms track directors, PSCs, due windows, blockers, ownership, and proof across a client portfolio.