What starts in JRI
Choose the legal or secretarial service, describe the event or question, set priority and attach the documents already available. The request is then a visible work item rather than an unstructured email.
Expert-led legal and secretarial support
Legal and secretarial work with a clear request trail
Use JRI to turn a company-secretarial or legal requirement into a structured support request with the relevant business context, documents, priority and updates kept in one place.
JRI working model
JRI makes the request actionable; professionals perform the specialist work.
JRI structures the request and keeps the work visible; professional review and any external filing are handled through the appropriate scope and confirmation.
- StartService request
- Keep visibleContext · files · status
- EscalateProfessional scope
JRI does not represent that an authority filing, professional review or approval has happened until the ticket and supporting record show that outcome.
How the work moves
The workspace keeps the request and result clear; specialist scope, external timelines and confirmations are handled explicitly.
1. Create a clear request
Select the relevant service, add the business context, set priority and attach the material needed to begin.
Context first
2. Scope and professional handoff
JRI keeps the request, documents and updates together while the right specialist reviews the defined scope.
Ticket-led
3. Follow the required process
Any filing, signature, payment or authority outcome follows its relevant external process and confirmation requirements.
Depends on the applicable process
4. Keep the outcome attached
Documents, messages and the resulting status remain connected to the original business context.
Traceable
What the service request covers
Clear scope before work begins—no fabricated automation or implied authority action.
Event-based requests
Start from the specific change, resolution, register question or filing need—not from a generic contact form.
Document-ready handoff
Attach the records and supporting documents that let a professional assess the real requirement.
Professional review
Secretarial and legal work is scoped and performed by the relevant professional rather than implied as automatic software output.
Visible status
Follow the request, messages and resulting documents alongside the original business context.
Why this route is useful
A service should leave the business with context, not another opaque handoff.
- A legal issue begins with the company context and material that explain it.
- Professional work can be tracked through a named service request rather than an opaque handoff.
- The request can preserve documents, updates and the final record in the same operating system.
- Authority and governance outcomes remain explicit rather than being claimed by a generic status card.
Scope and working model
What JRI keeps in the product, and what still needs professional action.
What the professional scope covers
Company-secretarial and legal work—such as reviewing an event, preparing the required records or supporting an applicable filing—requires the right professional scope. The exact deliverable and external timeline are confirmed from the facts of the request.
What is not automatic
JRI does not claim that a ROC filing, resolution, register update or authority acceptance has occurred merely because a request exists. The ticket, documents and relevant external confirmation must show the completed outcome.
Start with the actual business context.
Open the right JRI workspace or create a ticket with the relevant records and documents. The next action, professional scope and external confirmation remain visible.