# Behkish Advisory: Client onboarding checklist

Editable working checklist · October 17, 2026

Provider: Kshathra Technologies Inc., operating as Behkish Advisory

Contact: behkish.nz@outlook.com

**Client / project:** [Name]

**Engagement / reference:** [Name and reference]

**Sponsor / technical owner:** [Roles and contact details]

**Service period / time zones:** [Dates and time zones]

This checklist coordinates an approved engagement. It does not replace the finalized proposal or agreement. Keep passwords, access tokens, private keys, patient records, and customer datasets out of this document.

## 1. Commercial readiness

- [ ] Correct client and provider legal names are recorded.
- [ ] Written scope and applicable engagement documents are finalized and approved.
- [ ] Deliverables, exclusions, assumptions, success criteria, and review allowance are understood.
- [ ] Fee is confirmed in USD; taxes and third-party charges are identified.
- [ ] Initial invoice is issued and the applicable payment step is complete.
- [ ] Named client decision-maker and change approver are confirmed.
- [ ] Cancellation/rescheduling and schedule-change expectations are recorded.

**Pricing:** Hourly consulting is $200 USD per hour, with a one-hour minimum for paid sessions and approved additional work recorded in 15-minute increments. Custom scope and fees are agreed in writing. The free 30-minute initial meeting is separate from paid work.

**Payment arrangements:** Record the agreed invoice schedule and any required initial payment. No automatic payment is created by this checklist.

## 2. Kickoff and ownership

- [ ] Kickoff date, duration, participants, and time zones are confirmed.
- [ ] Business objective and decision to be made are restated in plain language.
- [ ] Product stage, users, operating context, and relevant deadline are understood.
- [ ] Client sponsor, technical owner, reviewer, and backup contact are identified.
- [ ] Communication channel and meeting cadence are agreed.
- [ ] Request priority and scheduling expectations are recorded; no unagreed on-call obligation is implied.
- [ ] Decision log, action list, and shared deliverable location are established.

### Kickoff agenda

1. Desired outcome and evidence of completion.
2. System and information boundaries.
3. Known risks, constraints, and dependencies.
4. Inputs, access, and stakeholder availability.
5. Milestones, review dates, and change approval.
6. Actions, owners, and next checkpoint.

## 3. Information handling and access

- [ ] Client confirms authority to provide the materials and access.
- [ ] Confidentiality and permitted-use expectations are agreed before sensitive sharing.
- [ ] Data categories and restricted materials are identified at a high level.
- [ ] Approved sharing channel is documented.
- [ ] Access is individually attributable, least-privilege, and time-bounded.
- [ ] Read-only or non-production access is used where sufficient.
- [ ] No credentials are sent in the inquiry form or included in the report.
- [ ] Use of external AI or other third-party services for client material is explicitly agreed before use.
- [ ] Retention, return, and deletion expectations are documented.
- [ ] Access-removal owner and target date are recorded.

**Approved access / sharing approach:** [Describe without secrets]

**Restricted material / processing constraints:** [Describe]

## 4. Assessment inputs, where applicable

Record the agreed application and environment, repositories and documents to sample, interviews, written deliverables, and readout. Set limits for this engagement instead of assuming a standard package.

- [ ] Architecture sketch and component inventory supplied.
- [ ] Main user journeys and information flows described.
- [ ] Identity, tenant, and authorization model explained.
- [ ] Relevant repositories and sampling boundaries agreed.
- [ ] Deployment, logging, backup, and provider configuration described.
- [ ] Existing known issues and prior relevant reviews supplied.
- [ ] Stakeholder interviews scheduled.
- [ ] Input-complete date recorded.
- [ ] Delivery date reflects the agreed scope, complete inputs, and availability.
- [ ] Review window and included clarification or correction allowance are agreed.

## 5. Custom work readiness

- [ ] Implementation milestone has specific acceptance criteria.
- [ ] Included capacity and testing approach are recorded.
- [ ] Repository ownership, branching/review process, and deployment responsibility are agreed.
- [ ] Rollback and environment restrictions are understood before changes.
- [ ] Production access or changes have explicit authorization when applicable.
- [ ] Documentation and handoff audience are identified.
- [ ] Support/maintenance after delivery is explicitly included or excluded.
- [ ] Any ongoing capacity, scheduling, reporting, and renewal terms are agreed in writing.
- [ ] A process exists to flag remaining capacity before it is exhausted.
- [ ] No extra hours begin without written approval.

## 6. Delivery and review

- [ ] Evidence and assumptions are separated in deliverables.
- [ ] Findings identify priority, rationale, owner, and suggested acceptance check.
- [ ] Scope gaps and unavailable evidence are documented.
- [ ] Review meeting and feedback deadline are scheduled.
- [ ] Client feedback is consolidated through the named reviewer.
- [ ] Any expanded scope follows written change control.
- [ ] Final invoice follows the agreed delivery/payment milestone.

## 7. Closeout

- [ ] Final deliverables and version references are handed over.
- [ ] Open decisions and residual risks are recorded.
- [ ] Implementation ownership and next actions are assigned.
- [ ] Access is removed or explicitly extended for an agreed reason.
- [ ] Material return/deletion actions follow the agreed policy.
- [ ] Final billing and any approved extra hours are reconciled.
- [ ] Ongoing support or the next engagement is agreed separately.
- [ ] Permission is obtained before any public case study, logo use, or testimonial.

## Working action log

| Action | Owner | Due date | Status / evidence |
| --- | --- | --- | --- |
| [Action] | [Owner] | [Date] | [Status] |
