Relations Hub

Introduction

Assure routing to and involvement of cross-functional legal responsibilities with no active action required from legal agents or end user.

Special legal experts, regardless if expert in local laws and regulations or for special topics like export control, assaults or corruption, should be involved into legal requests or matters, whenever needed without agents have to know by heart who is the correct (group of) person to address the topic.

The problem we keep seeing?

Especially in companies with complex structures, worldwide engagements and highly integrated processes people struggle with identifying all  responsible persons - especially the cross-functional ones - that have to be involved.

• requesting users have to know whom to root the request to
• Swivel agents have to figure out which expert group to involve
• Legal agents manually involve several expert groups based on personal knowledge
• Legal managers have to filter their area of responsibility for reporting reasons

What is the Relations Hub?

An additional layer for responsibility documentation, independent from organisational user data and assignment and/or workflow logics.

It allows a relation between a person or group with whatever attribute to define the responsibility. This can be leveraged for automated routing or reporting insights  along the attributes defined.

We map groups with attributes and that's it. Available as a (restricted) self-service and with built-in group management.  

This mapping (relation) can be used for any related action, from automatically filtered reporting to automated assignment to ACL adjustments.

Why not just…

… build a Separation Concept or adapt ACLs?

Because it's not flexible. Whenever the organisation changes, the whole concept or ACL setting has to be re-adjusted. This is a huge cost factor. The Relations Hub is (once implemented) a self-service.

Add on, used vice versa the Relations Hub keeps track of attributes not covered (mapped).

Proof (anonymised)

• No more manual swivel of requests
• Complex individual structure for legal organisation kept
• Final requirement to finish transformation from e-mail handled requests to full automated request routing

Outcomes you can expect

The Relations Hub can be extend to whatever cross-functional role exists from Information Security Officer to First Aid Contact. It can be leveraged for automated routing, and/or allows automated filter settings (either for insights or restrictions), and/or keeps people involved who have to be informed.

No more whitespots for audit relevant responsibility coverage.

Implementation approach

Discover (Weeks 1–2)

Define your roles and the leading attribute to define their area of responsibility.

Build (Weeks 3–5)

Configure settings, build self-service and create knowledge.

‍Pilot (Weeks 6–7)

Run with one process sector, user group, request form

‍Launch (Weeks 8–10)

Extend scope and/or on-board step by step more processes/views/persona groups

Limitations?

Any complex role structure - from legal responsibility to information security to health services, up to 3 hierarchies within a role cluster is possible.

What you get with RYNEX

• An implemented solution from easy to maintain cross-functional responsibility documentation and involvement, with integrated coverage control.
• Senior consultants focused on outcome over output.
• A delivery rhythm that gets you to value in weeks, not quarters.

Our upfront fixed price Readiness Check assures, that your environment is in a good shape for this out-of-the-box (ootb) implementation.