Files and documents
Organise authorised information and highlight missing items.
Kreluna Office is being designed to help coordinate repetitive, document-heavy work while leaving specialist or legally regulated advice, review and responsibility with the appropriate professionals.
Kreluna is in active development. Early access, feature availability and integration coverage are confirmed individually for each request.
Organise authorised information and highlight missing items.
Prepare tasks and reminders for review before action.
Make assignments, roles and approvals visible to managers and staff.
Kreluna Office can prepare tasks, organise documents and surface priorities or missing information. Configuration begins with the firm’s real process and the software it actually uses.
Calculations, regulatory interpretation and client-facing actions require review by the appropriate professional. Kreluna supports preparation and coordination rather than replacing specialist judgment.
No. Calculations, regulated interpretation and client actions require review by the appropriate specialist.
A recurring document process with clear owners, such as information intake, priority checks or draft communication.
Use restricted access, the minimum necessary data and agreed procedures before any real information is introduced.
Every project starts with a defined objective, authorised information and a clear review process. Capabilities are enabled progressively and important actions remain subject to approval.
Kreluna is not presented as a payroll engine or employee-decision system. These examples cover intake, completeness and coordination before professional payroll processing.
Collect messages and attachments, associate employer and period, and flag missing information for review.
Prepare checklists, tasks and reminders while calculations and statutory work remain in official systems and professional control.
Classify client questions and prepare drafts from approved content, escalating situation-specific requests.
Make status, owner and priority visible without assessing employee performance or making employment decisions.
The first use case should avoid special-category data where unnecessary and clearly separate organisational support, professional processing and employer decisions.
Describe the problem, who performs the work today and which observable result should improve.
Identify sources, permissions, manual hand-offs, unusual cases and points where a person must decide.
Run the pilot on authorised sample data against acceptance criteria agreed before the test.
Compare the workflow with its baseline, then extend, revise or stop it on evidence rather than enthusiasm.
Health, union or assessment information requires particular care. AI used for recruitment, management or employment decisions may fall under specific rules and is not included by implication.
Completeness and timeliness fit better than raw throughput. The final output remains under the firm’s and system’s control.
Requests reaching processing with agreed fields and documents available.
Additional communication caused by missing or inconsistent information.
Work spent classifying, checking and assigning incoming items.
Cases correctly stopped and escalated rather than handled automatically.
No. This page describes workflow support; payroll calculations and statutory work remain in authorised systems and professional control.
No. An administrative project excludes employment decisions. Such uses need a separate assessment and may be regulated as high risk.
The first control is not to use it unless necessary. Where required, purpose, access, security, retention and legal basis need competent assessment.
The AI Act and GDPR can apply together: duties and safeguards depend on the organisation’s role, the data and the system’s actual use. Assessment therefore comes before configuration.
These sources help frame the work; they do not replace legal, privacy or security advice for a specific situation.