Provide practice and legal-entity ownership, verified client contacts, consultant and supplier identity mappings, approved availability, billing and rate policies, finance-approved recognition methods, currency/tax inputs, subcontractor limits and CRM/accounting connections.
Implementation
Prepare delivery ownership, rate policy and independent financial review.
Implementation phases
Phase 1 · Team and ERP.ai
Agree the operating model
Confirm practices, project ownership, billing models, rate sources, approval thresholds and external party access.
| Field | Type | Required | Definition / allowed values |
|---|---|---|---|
| RequestNumber | text | Yes | — |
| Project | reference | Yes | → Projects |
| RequestedBy | reference | Yes | → Consultants |
| Role | reference | Yes | → Roles |
| RequiredSkills | text | No | Tags against SkillsLibrary |
| StartDate | date | Yes | — |
| EndDate | date | Yes | — |
| AllocationPercent | number | Yes | — |
| Status | select | Yes | Open, Proposed, Filled, Cancelled |
| ProposedConsultant | reference | No | → Consultants |
| Urgency | select | Yes | Normal, Urgent, Critical |
Phase 2 · Team and ERP.ai
Load the baseline
Import active engagements and approved staffing, time and financial balances with canonical references.
Phase 3 · Team and ERP.ai
Test complete flows
Run an engagement through scoped work capture, independent decisions, invoice preparation and finance acknowledgment, including failure cases.
Phase 4 · Team and ERP.ai
Activate the team
Review role-specific views and reports, then enable approved integrations and invite the planned user group.
| Role | Screens |
|---|---|
| Services Leader / COO | 8 |
| Practice Lead | 12 |
| Project Manager | 11 |
| Resource Manager | 4 |
| Consultant | 1 |
| Subcontractor | 0 |
| Client | 2 |
| Accounts | 2 |
Role permissionsRoles and permissions →
Freeze accepted time, expense and billing source values. Material scope and policy changes invalidate affected approvals. Apply reviewed adjustments or reversals with source linkage instead of overwriting accepted history. Recheck capacity, financial reconciliation and external-access cases before wider rollout.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.