Use case · Legal and compliance
Know which law each piece of work rests on.
Kaiku is a task tracker and a wiki that knows which legal acts your issues and policies cite. A register of requirements, the act read at the article, a policy approved as an edition and marked read — so that you can show what was reviewed, approved and brought to people, and when.
One requirement, from end to end
Recorded inside the product, on a company made up for the camera; the acts are real and read from their official publisher. No sound — the film is read.
The film follows one requirement of an invented company: the row in the register, the article it cites, the act opened on that article, everything else that rests on the same act, and the policy approved and read. The acts in it are real, read from their official publisher.
This is a tracker that knows which norms your work rests on. It is not a legal information service: it does not select legislation for you, does not comment on it, and gives no legal advice.
A register of requirements
In the board menu, Ready-made project… brings a requirements register in one action: a type called Requirement, ten columns — the norm, the obligation in your own words, the jurisdiction, the owner, how it is met, the evidence, whether it is met, the last review and the next — and a workflow of four states: not assessed, being met, confirmed, under review.
It reads as a table: a row per requirement, grouped by state or by whether it is met, edited in the cell, and taken out as one .xlsx with your columns in your order. It brings only what the project lacks, by name, so it can be taken into a project that already holds work.
A citation becomes a reference
A project switches legal references on in its board menu, under Legal acts…. From then on, an act named in an issue, a comment or a wiki page is a reference: marked where it was written, and listed in a block under the text with the article it cites.
- An address on a listed official site — pasted as it is, or as a link.
- A citation with a number of its own — a statutory instrument, a section of a named Act, a CELEX number — with the article written beside it.
- By hand, where the text names the act in words: add it under the issue or the page, with the place.
Nothing in your text is rewritten. A reference you remove stays removed, and one you put by hand stays through later edits for as long as its words stand.
The act, read where you work
A reference opens the act’s card: its title and publisher, the day its text is as of and the day the publisher’s site last confirmed it, the text opened at the place cited, a search inside it, and the original one press away.
Above the text is who refers to it: every issue and page of yours that cites this act, grouped by article. What you may not read is counted and never named. A project’s own list — every act it cites, with how many issues and pages rest on each and how many of those are still open — is one screen, in the same menu.
The texts come from official publishers on a list — the United Kingdom’s, Germany’s and Switzerland’s among them — and only from them. A site that will not answer a program leaves the reference with its address and no text, and the card says so.
Approved as an edition, then marked read
Approval on a wiki page records who approved which version, and when. The record is written once. An edit after it does not un-approve anything quietly: the earlier edition stays the one in force, and the page says so — on the screen, in its history and in the file you export.
Reading makes a page required reading for a person, a whole project or a team role. Each of them is told, and marks the edition they read; one reminder goes to those who have not; the marks come out as a spreadsheet. A new approved edition is asked about again.
For the reviewer and the auditor
- A selection of the project as one archive — by a query, an epic or a label, with the pages linked to it: every issue with its history, every page with its versions and marks, and an inventory in words on top.
- One issue or one page opened to somebody outside — a guest, by address and for a term, to read, comment or edit. The rest of the project stays shut, and the history says who opened it and that it was read.
- The activity journal of the company, read and taken as .xlsx by whoever administers it.
What comes round every year
A project keeps recurring issues — the annual review of a policy, the report to the board — filed on their day in the name of whoever set them, each linked to the one before while that is open. A due day is told ahead, at the steps the project’s lead sets: fourteen days, seven, one.
An assistant that reads the law before it answers
The legal assistant is a ready-made agent role, off until a company switches it on. Called by a mention on an issue, it reads the act on its official site and answers with the quotation and the day the text is as of — or says that it did not read. Its answer is a note for a person to check; it never writes «complies».
What it costs
References by address and by number, the block under an issue and a page, the act’s card and the project’s list of acts come with every plan and with the trial. Two things are a paid add-on, bought per project on the team plans and included during the trial: citations written in words, which a model reads and offers for a person to accept, and the list of acts as a spreadsheet.
Start with one register.
One project, your own requirements, the acts they rest on. The first month is free and needs no card.
Create a workspace