PCL

Practice Client Lifecycle CRM

Clients, services, quality controls and engagement follow-up

Local CRM foundation

Client onboarding

Record the legal client, principal contact and opportunity in one controlled intake. Primary Sector and Branch Location are mandatory to support regional and sector reporting.

1. Client profile

Company-level details

2. Primary contact

Individual-level details

3. Services and opportunity

Select controlled service terms only
Choose a Primary Sector to view its recommended standard service tags.

Saved client records

This first module stores records in this browser only. Link the same field model to your secured CRM database and document repository before operational use.

Lead-to-Engagement gatekeeper

Capture the enquiry separately, then advance it only when the required KYC, conflict, approval and signed Engagement Letter controls are present. An active engagement is created only at activation.

1. Lead capture and sector tagging

Admin, Manager or Engagement Partner
Select a sector to assess Potential PIE status.

2. Scoping, KYC and conflict check

Required before proposal preparation

3. Proposal and fee setting

Partner approval is mandatory for PIE and any configured threshold
Enter hours and rate to calculate the proposed fee.

4. Engagement Letter, setup and resources

Required before activation or WIP setup as indicated
Add resource details after activation. The system checks assistant capacity across records in the same planned week.

Lead and engagement Kanban

Advance only when the next stage’s gate is satisfied

This browser prototype records document references, not document files. In production, link references to a secured repository and enforce each gate using authenticated server-side permissions.

ICPAK-aligned audit workspace

Create a controlled annual audit file after statutory-audit activation. The audit file now follows a general-audit sequence: source population control, TB / GL reconciliation, provisional-to-final sample clearance, evidence testing, exception disposition and completion review. This workspace prepares a governed hand-off to ICPAK; it does not claim a direct ICPAK system connection.

0Audit files
0Planning gates complete
0Balanced trial balances
0Ready for Partner closure

1. Annual audit file

Statutory Audit engagements only
Archive is restricted to the Engagement Partner and is blocked until planning, a balanced and mapped TB, controlled and reconciled populations, finalised samples, resolved or reported exceptions, completion evidence and PIE/EQR controls are cleared.

2. Planning and control

Required before fieldwork

3. Trial balance intake and mapping

One balancing TB per audit file; preserve account numbers for roll-forward mapping
Import needs account number, description, current-year debit and current-year credit columns. The total must balance before it can support the audit file.

4. Lead schedules and audit programmes

Document work, observations and conclusion by audit area

5. Completion, reporting and review

Partner review is the report-issue gate

6. Audit-file attachment register

Physical files remain in the Document Vault

7. Fieldwork control and evidence gates

Control the source population before final samples or substantive testing

Controlled source population

Report parameters and control total are mandatory for final selection

Population control and reconciliation

Clear the source against the TB / GL before testing

Sample register and finalisation gate

Provisional selections cannot become final before population clearance

Exceptions, adjustments and unadjusted errors

Track disposition and reporting effect to completion

Fieldwork finalisation gates

Final sampling is enabled only after controlled source and reconciliation clearance
Audit file / areaSource populationReconciliationSamplesExceptions / adjustmentsGate

Trial balance mapping

Map each account to an audit area before financial-reporting/export use
Audit file / accountDescriptionDebitCreditAudit area mappingAction

Audit file register and closure status

Client / periodFile and TBPlanning / workpapersCompletion / attachmentsClosure status

This prototype records references and workflow evidence locally. Production must enforce authenticated role checks, immutable audit trails, file locks and data retention on the server, then generate the ICPAK package through approved export procedures.

Centralized communication hub

One controlled history of communications across leads, engagements, primary client contacts, tax invoices and QR activity. Follow-ups create a position-routed reminder; attachments are recorded as private vault references.

0Open communications
0Follow-ups due or overdue
0Logged today
0QR events

Log communication

Staff or system event

Find communications

Search across all linked records

Open items with a past follow-up date are highlighted. The production scheduler must deliver reminders through authenticated activities or approved channels.

All communications

QR values remain opaque; client details are shown only from the CRM link.
Date / channelSubject and detailsLinked lead, client and serviceStaff / follow-upStatusAction

Timesheets and WIP

Record daily work against active engagement tasks, approve it once, then track actual cost, budget variance, billing and profitability. Approved entries are locked; corrections use a separate reversal entry.

Staff rate history

Finance management only

My weekly timesheet

Draft or submit for Manager approval

Engagement financial baseline

Fee changes remain separate from the Engagement Letter record

Tax invoice and QR communication

Tax projects only, linked to the originating lead and primary client contact

Payment reconciliation

Match a receipt to the invoice payment reference

Team approvals

Approval locks hours and work dates
Staff / engagementHoursDescriptionStatusAction

Tax invoice register and communication

The QR stores only an opaque invoice token. Lead and contact data remain in the controlled CRM record.
Invoice / tax periodLead and contactTotal / receivedDue / statusQR and communication

Current WIP and profitability

EngagementAgreed FeeHoursActual CostTotal BilledUnbilled WIPCost / FeeBudget VarianceAction

Staff rate history

Rates are selected by staff ID and time-entry date, never hardcoded
Staff IDPositionCost RateBillable RateEffectiveEnd

HR and staffing

Maintain professional credentials, CPD, leave, assignment capacity, structured reviews and intern induction without building payroll. Busy-season leave and roster conflicts are escalated before they affect engagement delivery.

0CPD hours logged this year
0Credentials expiring in 30 days
0Busy-season leave requests
0Roster conflicts prevented

Staff credentials and CPD

Credentials and CPD evidence must link to the vault in production

Leave request

15 January–30 April routes to Engagement Partner approval
Enter leave dates to assess busy-season approval and active-fieldwork impact.

Staffing roster

Checks leave and overlapping active fieldwork before allocation
The system blocks a person who has an overlapping engagement assignment or approved leave.

Engagement performance review

Manager or Supervisor feedback after an engagement

Staffing roster and leave approvals

Busy-season requests need Engagement Partner approval
Staff IDEngagement / leaveDatesAllocation / daysStatusAction

Credential compliance and CPD

Expiring credentials generate the HR compliance alert
Staff IDCredentialStatusCPD HoursExpiry

Performance reviews

Utilization follow-up is linked to approved timesheets
EngagementRevieweeTechnicalPunctualityWorking PapersAverage

Staff attendance and fieldwork

Track work location, daily attendance, site visits, attendance exceptions and the gap between time present and time booked to client work. Leave approval automatically reserves the affected days.

0Currently clocked in
—On-time rate this month
0Late / missed-punch exceptions
0Weekly timesheet gaps

My attendance

Standard hours: Monday–Friday, 08:00–17:00

Client site visit

Fieldwork verification, not a public location tracker

Attendance exceptions

Managers or Supervisors approve supported corrections
Staff / dateExceptionVarianceReasonStatusAction

Timesheet-gap queue

Compare attendance time with client work logged that week
StaffWeekAttendanceClient workGap

Attendance register

On-leave entries are created from approved leave and cannot be clocked over
StaffDateLocationClock in / outHoursStatusReview

Client site visits

Verify fieldwork presence through the assigned Supervisor
StaffClient / engagementCheck in / outGPSSupervisor sign-off

Client document vault

Register document metadata, source location, version and access trail separately from the physical file. A production document repository must use private object storage and short-lived download links.

Register a document

Metadata only in this browser prototype

Document register

View/download actions are logged
DocumentCategoryVersionUploadedLockActions

Vault access audit trail

Blocked locked-document actions remain in the log
TimestampDocumentActionActor ID

Help desk and support

Handle client queries, staff system support and engagement blockers through a tracked ticket, position-based routing, SLA control, comments and knowledge-base articles.

0Open tickets
0SLA breaches
0Resolved tickets
—Top issue category

New support ticket

Client or staff requester

Knowledge-base article

Client-visible articles must not expose internal processes

Ticket update

Use internal notes for staff-only discussion

Knowledge base

Self-service guidance
ArticleCategoryAudienceViews

Support queue

SLA deadlines and internal comments are tracked per ticket

Executive reporting and analytics

Partner-facing metrics combine WIP, approved time, billing, quality controls, overdue work, document protection and ICPAK hand-off. In production these aggregates run from the secured database.

KES 0Unbilled WIP
0Active engagements
0Potential PIE / EQR pending
0Loss / overrun alerts

Realization by sector

Cost as a percentage of agreed fee
SectorAgreed FeeActual CostCost / FeeFlag

Revenue by branch

Paid invoice value
BranchPaid revenue

Compliance and operations queue

Drill down by editing the engagement or opening its WIP record
ControlEngagement / documentDetailStatus

System alerts

The production scheduler must deduplicate and deliver mandatory alerts through the approved channels
AlertRelated recordRecipient positionStatus

Master service catalogue

These controlled terms are the only selectable service tags. They keep pipeline, service delivery and cross-selling reports consistent across the firm.

Sector tagging

Sector recommendations use the controlled names above. Where a sector brief uses a descriptive phrase such as “grant reporting”, “payroll support” or “regulatory compliance”, the related controlled service tag is selected and the detail is captured in Client Notes.

Operational workflow rules

Automations created when a client is saved are visible against that client record. These rules are ready for conversion to server-side CRM jobs and task assignments.

Lead-to-Engagement acceptance gate

A lead cannot become an active engagement until the signed Engagement Letter reference is present, KYC documents are recorded and Manager-verified, the conflict check is cleared and all required approvals are complete. Statutory Audit also requires an ICPAK reference.

PIE / ISA 220 quality control

For a PIE, Financial Services or Public Sector client, create an open task for the Engagement Partner: “Assign Independent Engagement Quality Reviewer.” An audit report cannot be signed until the assignment is complete.

Cross-selling follow-up

When Statutory Audit is selected and the audit is signed, create a day-30 Account Manager task to offer Tax Diagnostic Reviews or Cash-flow Forecasting & Financial Modeling.

Tax compliance work packs

Tax Compliance now creates only the selected VAT and eTIMS, payroll and statutory, WHT, tax-credit, income-tax, PPE, stock, instalment-tax and client-report tasks. Credits or tax prepayments remain blocked from the tax position until iTax verification and reviewer approval are recorded.

Branch routing

New leads are routed to the Branch Manager role for Nairobi, Bungoma or Kisii. “Other” is routed to the Practice Administration queue for allocation.

Quarterly data clean-up

Review potential duplicates, incomplete profiles, client notes and engagement-letter references before each quarterly pipeline and quality-control review.

Access control

Permissions are assigned to positions and profiles, never embedded against a named individual. Actual users inherit access from their assigned position and reporting line.

The current browser-local module displays the approved access model. Production deployment must enforce the same model in authenticated server-side permissions, not only in the browser interface.