Client Onboarding Tracker — Demonstration

SELF-DIRECTED DEMONSTRATION

Context

This demonstration uses fictional accountancy-practice records to show how a small professional-services team could monitor onboarding from engagement to handover. All names, dates and statuses are samples.

Operational problem

When document requests, access arrangements and deadlines sit in separate inboxes, the team cannot quickly answer three basic questions: what is missing, who owns the next action and when was the client last updated?

Approach

I designed one row per client with stage-specific controls for the engagement letter, identity checks, data access and opening information. Those inputs feed a concise overall status, next action, due date and last-update field.

Deliverables demonstrated

• Onboarding tracker with clear stage fields • Named owner and immediate next action • First-deadline and follow-up dates • Exception-led overall status • Notes for handover context and agreed boundaries

Key design decisions

The tracker separates stage completion from overall delivery status. It records access status but never credentials. One next-action field prevents competing follow-up lists, while the last-client-update field makes communication gaps visible.

Result of the demonstration

The sample lets a manager distinguish clients that are ready for handover, still in setup, waiting for the client or at risk. It creates a practical agenda for a short weekly review. No performance improvement is claimed because the data is fictional.

Boundaries

The tool supports operational coordination. It does not make accounting, tax, legal, AML or regulatory decisions.

Related service https://contra.com/s/EgRFWbkb-client-onboarding-and-reporting-sprint