the problem

Changes get lost between versions.

Reallocations and extensions are often negotiated by email and phone, leaving the current state of an agreement unclear to everyone except the person who handled it.

No single current version

Staff cannot say with certainty what the agreement now permits.

Justification is undocumented

The reasoning for a reallocation is not retained for later audit.

Approvals are informal

Verbal or email approval leaves nothing defensible in the record.

the process

How it runs in Tsen’awt.

A change request is a tracked instrument against the original agreement.

Request raised as a record

The proposed change, amount and rationale are captured in a structured form.

Internal approval routed

Finance, the programme department and leadership approve in sequence.

Funder correspondence retained

Submissions and responses are filed against the agreement.

Amendment recorded

The approved change is attached to the agreement without overwriting its history.

what it uses

The parts involved.

This process is built from parts of the platform working together.

Forms

Capturing the request, amount and justification consistently.

Files

Holding the agreement and its amendment history.

Automated Workflows

Routing internal approvals in the required order.

Nation Record

Retaining the amended agreement as institutional record.

outcome

What it changes.

The current state of every agreement is knowable.

One authoritative version

Staff can see what the agreement currently permits.

Defensible changes

Justification and approvals are on record for audit.

Cleaner reporting

Reporting reflects the amended agreement automatically.

next step

Bring this into your Nation.

We start with an assessment of how your departments already work, then bring that work into the environment one area at a time.