Put your organisation's knowledge to work

Why a wiki is hard to search

Ask anyone who has used a wiki for a few years. The answer is in there somewhere, under a title someone picked in 2019, next to three older versions that disagree with it.

Certant reads those pages instead of listing them. You ask the question and get the answer with the page it came from, and it tells you when an older document says something different.

It reads SharePoint, Confluence and your shared drives together, so it doesn't matter where a document was filed.

Turn a question into a table

Ask for the liability cap in each of two hundred contracts and you get a table back, with a row for each contract and the page the figure came from. Search works on meaning, so it finds the clause whatever the author called it.

Every member, contract, site and policy also gets a page of its own, written from everything that mentions it.

It tells you where documents disagree

Certant flags policies that contradict each other and shows you the two passages side by side. It does the same for procedures that have been replaced and guidance that was saved more than once.

It also keeps a list of the questions it couldn't answer, which shows you what your documents are missing.

It watches what comes in

You don't have to upload everything by hand. Certant takes file drops, scheduled exports, data sent through the API and forwarded email, and it checks each delivery and keeps it on file.

You can set a watch on anything in it, such as a contract coming up for renewal or a new document that contradicts a policy. When it trips, the person responsible is told and sent the clause.

First drafts from your own record

Certant drafts tender responses, grant applications, submissions and board papers from what your organisation has already said and decided.

Each paragraph shows the source it was drawn from, so whoever reviews it can check each claim against the original.

It remembers how things were decided

Decisions and exceptions are kept with the reasons for them and the documents they relied on, so you can ask how something was handled last time.

That still works after the person who made the decision has retired.

What an agent gets from the knowledgebase

Access to your systems lets an agent act. What it reads in your knowledgebase is how it decides whether to, and the example below shows the page behind each step.

Knows who is who. The supplier in your accounts, the party to the contract and the member record are the same organisation, and the agent treats them as one. An agent without that matches on the name.

Calculates figures. Numbers are read from the table they sit in and worked out from there. The AI doesn't write them.

Follows your rules. Delegations, limits and escalation paths come from your own policies. An agent without them only knows what somebody thought to put in its instructions.

Uses the right version. It applies the rule that was in force on the date in question and tells you which one that was.

Remembers decisions. Past decisions and corrections stay in the knowledgebase, so you don't have to make the same correction again for the next agent.

Stops when it doesn't know. If the knowledge isn't there, the agent hands the job to a person and says what was missing.

What people build with it

A research corpus you can ask. A water authority indexes its whole library of research. "What do we know about PFAS in NSW?" comes back as one answer across many papers, each with its citation.

Two rule sets, side by side. A bank loads the new prudential standard beside its existing policies. The model surfaces every clause that changed and every gap, with the page each came from.

HR answers without the queue. An association loads every benefits, leave and procedure document. Employees answer their own questions, with a link to the exact policy section.

Ask Certant to build it

The AI FDE sits in a drawer on every screen. Describe the knowledgebase you want in plain English and it builds it, then waits for your approval before anything goes live.