A date is not a decision
Deadlines are important, but the company still needs to confirm applicability, prepare evidence, understand ownership and distinguish review from completion.
Back to playbooks
Chapter IV · Optimise · compliance and operating rhythm
How to optimise the recurring work that keeps the company dependable.
A practical guide for the operating stage after setup and early sales: identify what applies, assign ownership, attach evidence, inspect exceptions and bring in specialists for work that needs professional judgment or an external filing.
Stage map
From the next decision to a visible hand-off.
01
Map what applies
02
Assign the work
03
Attach evidence
04
Review and confirm
What to do at this stage
The work before the next outcome.
This playbook separates preparation from the decision made by an expert, authority, customer or counterparty. It is a practical operating guide, not legal, tax, financial or regulatory advice.
- 01
Map the operating facts before the obligations
Do this: Keep the entity, industry, location, activity, team, products, banking and other relevant company facts current before treating any calendar as complete.
Compliance applicability depends on the real business. A generic list of dates cannot reliably tell a company what applies.
Good to know: A compliance item can be recurring, one-time, pending review or inapplicable; those are different states, not one reminder type.
- 02
Give every active item an owner and a next action
Do this: Use the Compliance workspace to organise recurring and one-time work, calendar or list views, ownership, dates and visible review states.
A deadline is more useful when the company can see the evidence needed, the person responsible and what remains before the next confirmed state.
Good to know: A system reminder does not eliminate the need to confirm applicability, facts, deadlines or professional scope for the company.
- 03
Keep operating evidence close to the item
Do this: Attach or reference the supporting records that explain the company activity, transactions, documents, people or prior actions relevant to the work.
Evidence lets the founder, internal team or specialist understand why an item exists and what has been done without starting from a vague status update.
Good to know: Evidence attached to a workspace is a record for review; it does not itself confirm filing, compliance or approval.
- 04
Escalate specialist work with context
Do this: When legal, payroll, HR, tax, registration or specialist review is needed, create a support request that includes the issue, priority, documents and relevant compliance record.
Experts can make a stronger assessment when the question and source material arrive together, and the company can follow the delivery trail.
Good to know: Expert scope, authority submissions and third-party outcomes remain separate from the internal status shown in a workspace.
At this stage
With and without a connected JRI workspace.
The point is not that a founder cannot use spreadsheets, email, advisers or other products. The difference is whether the relevant company context and hand-off trail remain connected to the work.
Without a shared JRI workspace
Distributed- A calendar reminder can be separated from the business facts, evidence, owner and professional conversation needed to resolve the item.
- Recurring tasks can be copied forward without a clear record of what changed, what was reviewed or what remains outstanding.
- HR, payroll, legal and tax questions are often raised as disconnected tickets with little relationship to the underlying company record.
With JRI.AI
Connected- Compliance provides recurring, one-time, calendar, list, kanban, data-centre and AI-workspace views around active obligations and their records.
- The business workspace and Console hold company and operational context that can make a compliance question more inspectable.
- Structured Support keeps an expert request, service context, priority, documents, messages, assignment and delivery status together.
| Dimension | Without JRI | With JRI.AI |
|---|---|---|
| Applicability | A broad reminder list may not explain whether the item applies to this entity, activity, location or period. | Compliance is designed around applicability, recurring or one-time work and visible company-specific context. |
| Ownership | The team sees a due date but cannot see who is preparing, reviewing or waiting for information. | The workspace supports ownership and status views so the next action can be inspected rather than inferred. |
| Evidence | Documents and explanations are scattered across folders and inboxes, detached from the obligation they support. | Compliance and business records create a place to keep the item, evidence and review trail in context. |
| Professional support | A specialist receives a generic question and has to request the underlying records before work can begin. | Support is a structured delivery path with service context, priority, documents, messages, assignment and status. |
Actual product surfaces
Where this work lives in JRI.
These links point to the relevant public product page. They describe the purpose of each workspace rather than implying a workflow that the user app does not provide.
Native workspace
Compliance Management
A native workspace for recurring and one-time items, calendar, list and kanban views, evidence, owner and review states.
Open surfaceOperating context
Console
Operating records such as invoices, expenses, banking, purchases and reporting give business questions a practical source trail.
Open surfaceExpert-led
HR and payroll support
The public HR page explains the expert-led route for employment, payroll and labour work without presenting it as an automatic platform filing.
Open surfaceSupport trail
Expert On-Demand
Create a context-rich support ticket when the work needs a specialist to review the evidence and scope the next action.
Open surfaceGood to know
Facts that make the next decision clearer.
Recurring does not mean identical
A recurring item may carry a different period, owner, evidence set or exception. The operating record should show that difference.
HR and payroll are scoped work
Employment and payroll obligations depend on the workforce, locations and facts. Expert support should be requested with the relevant context rather than assumed as automatic.
Questions at this stage
The questions worth resolving before you move on.
Does the Compliance workspace file statutory forms automatically?
No. It is a native operating workspace for applicability, dates, ownership, evidence and review. A filing or authority outcome remains a separate external process.
Can I use it for recurring and one-time work?
Yes. The Compliance module includes both recurring and one-time views, alongside calendar, list, kanban and data-centre views.
How should I raise a payroll or HR issue?
Use a structured support request with the business facts, priority, documents and the specific question. The appropriate professional scope can then be confirmed for the engagement.
What does a completed status mean?
Interpret a status in the context of the underlying item and evidence. A workspace status should not be treated as an authority approval, external filing receipt or professional opinion unless the relevant record confirms it.
Next playbook