Workflow Automation & SLA Tracking The routine follow-ups nobody has time to do.
A no-code rules engine that reacts to what happens in the practice, and service targets per job type that warn you before a deadline slips rather than after.
Automation, without writing anything
A rule is three parts: what happened, whether it matters, and what to do about it. No scripting, and every firing is written to the log.
Triggers
Rules react to job, task and date events as they occur in the practice — not on a nightly sweep you have to trust.
Conditions
A rule fires only when its conditions match, so "notify the partner" can mean this client, this job type, this threshold.
Reassign
Move work to a different owner automatically when the situation calls for it.
Change status
Advance or flag a job without someone remembering to do it manually.
Notify
Tell the right person, through the channels they have not opted out of.
Create task
Raise the follow-up work the event implies, assigned and dated, rather than hoping it gets noticed.
Service targets that account for waiting
An SLA that counts time you spent blocked is a number nobody trusts. This one pauses.
Per-job-type targets
Different work deserves different promises. Targets are configured per job type rather than one firm-wide number.
The clock pauses
SLA time is measured only while a job is actively worked, pausing while it is blocked by an unresolved dependency.
Early warning
A job approaching its target triggers a warning, so the intervention happens before the breach rather than after.
Breach and escalation
On breach the job is flagged and escalated up a configured chain of recipients, levels and timing.
How it behaves under pressure
Automation earns trust by being predictable at the edges, not just in the happy path.
Every automation firing is logged, so automated changes are as traceable as manual ones.
SLA time is measured only while the job is actively worked, and pauses while a prerequisite is unresolved.
Secondary actions such as search indexing and some notifications are best-effort: if one fails, the primary business action still succeeds.
If the permission service is unavailable, access is denied rather than granted.
Notifications honour recipient category preferences, while security and system messages are always delivered.
Notification delivery retries up to three times with increasing delays before giving up.
Frequently asked questions
What can an automation rule actually do?
Do we have to use the automation rules you ship?
Does the SLA clock run while we are waiting on the client?
What happens when a job approaches its target?
Explore the platform
- Jobs & WorkflowsTemplated engagements with stage gates, task assignment, recurrence and dependencies
- Time & BillingTime capture, approval, WIP ledger, invoicing, quotes and financial periods
- Client PortalSecure per-client access to jobs, documents, invoices, quotes and messaging
- Document ManagementCentral store, versioning, document requests, malware scanning and text extraction
- Capacity PlanningAvailability, workload forecasting, utilization thresholds and load balancing across staff
- Reporting & AnalyticsWIP, aged receivables, realization, profitability and utilization reporting
- Security & Access ControlRole permissions, per-user data scopes, visibility rules and an immutable audit log
- Solo & Small FirmsReplace the folder-and-spreadsheet stack without a six-month implementation
- Growing FirmsStandardised workflows, approval gates, SLA targets and per-team data scopes
- Multi-Entity FirmsPer-entity branding, invoice numbering, tax defaults and job codes under one firm
- Switching PlatformsStaged CSV import with review at each step, including CCH iFirm exports
See Praxio on your own engagements.
Book a walkthrough and we'll configure it around the way your firm actually works — your engagement types, your review steps, your billing model.