My to-do today
Assigned to the current position, due today or overdue.


One shared workspace for clients, work, resources and firm-controlled finance
Keep existing client details, contacts and services together. Missing information is highlighted in red for Partners and Managers to update. Existing-client status is separate from file completeness and new-engagement approvals.
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.
Capture and qualify an enquiry before it becomes an opportunity. A signed Engagement Letter, verified KYC and acceptance controls are still required before the opportunity becomes an active engagement.
A qualified lead becomes an Opportunity at proposal stage. Contract renewal starts a separate controlled cycle and never overwrites a signed Engagement Letter. This browser prototype records document references, not document files.
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.
| Audit file / area | Source population | Reconciliation | Samples | Exceptions / adjustments | Gate |
|---|
| Audit file / account | Description | Debit | Credit | Audit area mapping | Action |
|---|
| Client / period | File and TB | Planning / workpapers | Completion / attachments | Closure 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.
Manage client and staff interactions in one controlled history. Formal communications inherit the engagement’s locked handling firm and can receive an opaque QR reference.
Open items with a past follow-up date are highlighted. Production reminders must run through authenticated activities or approved channels.
| Date / channel | Subject, details and communication QR | Linked lead, client and service | Staff / follow-up | Status | Action |
|---|
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.
| Invoice / tax period | Lead and contact | Total / received | Due / status | Client communication |
|---|
| Engagement | Agreed Fee | Hours | Actual Cost | Total Billed | Unbilled WIP | Cost / Fee | Budget Variance | Action |
|---|
| Staff ID | Position | Cost Rate | Billable Rate | Effective | End |
|---|
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.
| Staff ID | Engagement / leave | Dates | Allocation / days | Status | Action |
|---|
| Staff ID | Credential | Status | CPD Hours | Expiry |
|---|
| Engagement | Reviewee | Technical | Punctuality | Working Papers | Average |
|---|
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.
| Staff / date | Exception | Variance | Reason | Status | Action |
|---|
| Staff | Week | Attendance | Client work | Gap |
|---|
| Staff | Date | Location | Clock in / out | Hours | Status | Review |
|---|
| Staff | Client / engagement | Check in / out | GPS | Supervisor sign-off |
|---|
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.
| Document | Category | Version | Uploaded | Lock | Actions |
|---|
| Timestamp | Document | Action | Actor ID |
|---|
Handle client queries, staff system support and engagement blockers through a tracked ticket, position-based routing, SLA control, comments and knowledge-base articles.
| Article | Category | Audience | Views |
|---|
Start from work that needs attention. The shared workspace combines authorised work across the practice while every engagement, invoice, payment, document and communication retains its locked Handling Firm.
Start with today’s priorities, follow work already in motion and prepare for the next seven days.
Assigned to the current position, due today or overdue.
Items blocked, awaiting evidence or in review.
Your open tasks due in the next seven days.
Operational context across the selected handling firm view.
| Due | Task | Client / project | Firm | Status |
|---|
| Sector | Agreed Fee | Actual Cost | Cost / Fee | Flag |
|---|
| Branch | Paid revenue |
|---|
| Sector | Engagements | Paid revenue |
|---|
| Service line | Fee baseline | Actual cost | Margin |
|---|
| Lead source | Leads | Converted | Conversion |
|---|
| Branch | Open / Hot | Active | Conversion |
|---|
| Control | Engagement / document | Detail | Status |
|---|
| Alert | Related record | Recipient position | Status |
|---|
These controlled terms are the only selectable service tags. They keep pipeline, service delivery and cross-selling reports consistent across the firm.
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.
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.
Cold, Warm and Hot are priority signals, not compliance stages. Warm and Hot leads require an owner, next activity and due date. A qualified lead becomes an Opportunity when its proposal is sent; the opportunity retains the selected firm, routing and fee forecast.
An opportunity 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. Billing milestones are scheduled at activation, not issued merely because an opportunity is won.
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.
Firm is the legal owner, Branch is the delivery office, Service Line is Audit, Tax, Accounting or Advisory, and the Specialist Team is the work queue. New leads route from Firm → Branch → Service Line → Specialist Team. A changed firm requires a new lead and engagement.
Annual audits and recurring retainers alert the assigned owner 60 and 30 days before expiry. Starting a renewal creates a separate opportunity, refreshes KYC and conflict controls, and requires a new signed EL. The prior signed EL remains locked.
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 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.
Review potential duplicates, incomplete profiles, client notes and engagement-letter references before each quarterly pipeline and quality-control review.
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.