Beta

Who holds what, at any moment.

Racia keeps your organisation's RACI matrix: who is responsible, who approves, who is consulted and who is informed, for every activity. It turns it into tasks, approvals and notifications, and your applications query it through an API.

Sign in by e-mail, no password. In English, French and German.

ActivityManagementFinanceAccountantHR
FinanceARI
AccountingIAR
PaymentsAR
HiringACR
Every cell reads at a given date, with the chain of delegations that explains it.

A RACI in a spreadsheet is out of date as soon as it is written

It names people

When someone changes position or leaves, the spreadsheet keeps naming them, and nobody notices.

It has gaps

An activity with no approver is discovered on the day one is needed, usually at the worst possible time.

It does nothing

When it is time to act, you still have to find the spreadsheet, the right row, the right person, then write to them.

How it works

  1. Complete from the start

    On creation, the root position holds every letter on the root activity. Nothing is ever without someone responsible.

  2. Split from the top down

    Activities and positions are subdivided the way your organisation is: Finance, then Accounting and Payments; Management, then the heads of each area.

  3. Delegate or keep

    Each holder delegates a letter on an activity to a position, for a period. Doing nothing means keeping it.

  4. Never a gap

    A revocation cascades, and the impact screen shows who takes over what before you confirm. Every mandatory letter always has a holder.

What Racia does

Positions, not people

Delegations target positions. An appointment leaves the matrix untouched: the new person inherits the position's hats.

The matrix at any date

A delegation is never edited, only closed. Who was responsible six months ago can be recomputed exactly.

Tasks, approvals, opinions

An event from your applications becomes a task for R, an approval for A, a request for an opinion for C and a notice for I.

Reminders and escalation

With no answer in time, a reminder goes out, then the request moves up the delegation chain, skipping vacant positions.

Everything by e-mail

Approve, reject, give an opinion, delegate: one link is enough, no account needed. A sensitive approval also asks for a code.

A complete log

Every act is written to a log that nothing alters: who did what, when, and through which channel.

For your applications

Your invoicing, purchasing or intranet no longer have to hard-code who approves what: they ask Racia, or report an event and collect the decision.

  • REST API described in OpenAPI, API keys per organisation
  • Signed webhooks, with replay
  • Every question can be asked at a date
# Who holds each letter on this activity?
GET /v1/organizations/{org}/activities/{activity}/holders

# An invoice to approve: Racia takes care of it.
POST /v1/organizations/{org}/events
{ "activityId": "…", "title": "Invoice 2026-114, CHF 48,000" }

Frequently asked questions

Do I need an account to answer a request?

No. Every task, approval or request for an opinion arrives by e-mail with its action links. You only sign in to manage the matrix.

What happens when someone changes position?

You appoint the new person to the position, and that is all: delegations target the position. A vacant position stays responsible; requests go to the first occupied position above it.

Can I find out who was responsible at a past date?

Yes. The matrix can be recomputed at any date, and the history shows every delegation, its period, its author and how it ended.

Where is the data?

In Switzerland. The website sets no cookies; the application uses only one, for the session. Details are on the Privacy page.

Start with your own organisation

An e-mail address, the organisation's name and your position: the matrix is ready, all that is left is to split and delegate.

Try Racia