Do not let incomplete intake become accepted setup in STAR.
Client Onboarding
Client Onboarding governs the threshold between intake and accepted record. It decides what enters STAR, what stays blocked, and what still needs an explicit owner, so missing detail, unresolved exceptions, absent documents, and informal approvals do not enter the firm as if they were settled.
Block what is still unresolved before the rest of the firm has to inherit it.
The first failure is accepting the record too early.
Most firms do not fail here because intake stops moving. They fail because a client record is created while the firm is still carrying conditions it intends to sort out later.
The billing contact is not final. Engagement detail still needs clarification. A required document is assumed to be coming. A special handling exception is understood verbally but has not been approved cleanly. Once the record exists in STAR, those conditions stop looking like open decisions and start looking like follow-up someone else will absorb.
What has to be true before STAR gets the record
Client Onboarding turns readiness into an enforceable threshold instead of a loose judgment call.
Required setup detail is complete
Client, contact, billing, engagement, office, partner, manager, and related setup detail is present where the firm depends on it.
Required documents are actually in hand
The documents the firm treats as prerequisites are attached, usable, and no longer sitting in side follow-up.
Approvals and exceptions are explicit
Acceptance, special handling, and open exceptions are approved by the people who should own them, not implied through email or memory.
Blocked conditions stay blocked
If something is unresolved, it remains unresolved. It does not cross into STAR carrying the appearance of completion.
What weak entry becomes
A record created to keep momentum
A new client is entered because the team needs to move. Later, tax or billing discovers that engagement coding was not fully settled, billing terms were still open, and one required document never actually made it into the record. The system accepted the client before the firm had finished accepting the conditions around it.
An exception softened into follow-up
A special case is known during intake, but the record is created first and the exception loses force. What should have remained visibly blocked becomes a chain of reminders, side messages, and partial memory.
A downstream team beginning in repair
The next team inherits an official-looking record, then spends the first part of its work finding out what still has to be corrected, confirmed, or rediscovered before anyone can trust what entered the system.
What Client Onboarding changes
Validation happens before acceptance
Client Onboarding checks whether the firm’s real setup conditions are satisfied before STAR inherits the record. The standard is not whether enough information exists to get by. It is whether the rest of the firm is ready to depend on the setup.
Unresolved conditions stop disappearing
Missing billing contacts, incomplete engagement detail, absent documents, unresolved exceptions, and unclear ownership do not disappear just because intake is moving. The product keeps those conditions visible and prevents them from becoming accepted by accident.
Downstream work starts from a stronger condition
Tax, audit, billing, client service, and operations inherit a cleaner record. Less of their day is spent reopening decisions that should have been settled before the client ever entered STAR.
Not intake collection. Accepted setup.
Not a prettier form
The problem is not that firms need a nicer way to gather information. The problem is that record creation often happens before the firm has finished deciding what it is willing to accept as real.
A strong first move when setup keeps becoming correction work
Client Onboarding is usually the right first product when downstream teams keep discovering that a client record entered the system carrying more uncertainty than anyone admitted at the start.