Use what the job needs
Identify the information required and the systems that will receive it.
Data & control
Clear information.
Clear responsibility.
Useful systems make it clear what information they use, who can access it and where a person makes the decision.
Document workflow
A supplier email arrives with an updated order attached.
Illustrative workflow
Order details prepared for approval
- Source
- Email and attachment
- Check
- Compare with existing record
- Next step
- Person approves the update
Human review before action
Fictional examples. Explore the tabs to see different applications.
Designed into the work
Agree the boundaries early.
Give access deliberately
Define roles, permissions and allowed actions around the people doing the work.
Make review visible
Route uncertain results and important changes to the person responsible.
AI in the process
An answer should have somewhere to come from.
- Approved knowledge sources and clear access rules
- Evaluation against relevant business examples
- A clear path for missing or uncertain information
- Human approval for agreed actions
- Monitoring and updates scoped to the system
The details belong to your project.
Hosting, providers, retention, data access and responsibilities are documented for the actual system. They vary with the work and the information involved.
Contacting Rykai
Your enquiry reaches a person.
You send the outline
The form asks for contact details and a short project description.
We record and deliver it
The server validates the enquiry, records it and attempts email delivery.
Ricki reviews and replies
A human reads the request and works out the next questions.
Read the privacy noticeStart a conversation
Let’s make it work better.
Tell us what happens today and what you would like to improve. We’ll help you find a sensible starting point.