Before an AI processor touches a file, your operations lead and LOS admin need two answers: what can it access, and what can it change?
With Loandock, your LOS stays the system of record. The processing work happens there, in the system your team already uses.
Access your admin controls
Your admin issues access, assigns the role and can revoke it. The role should cover the work you agreed to run and nothing beyond it.
Agree on the workflow before adding access. The first product demonstration uses a demo file, so your team does not need to send borrower documents.
The changes to a file
Loandock reads open underwriting conditions and the document list. It requests missing documents, checks what comes back, files accepted documents against the conditions they answer, and marks those conditions fulfilled.
Clara can update loan milestones according to the workflow agreed during onboarding, using the access your team provisions. Your team sets when those updates should happen. Credit decisions, pricing and business rules remain under your team's control. The LOS integration page sets out the read and write scope together.
A record of the work
Each action is logged with the time, actor and affected loan file. Borrower communications are recorded too. Your team can inspect completed work or trace an exception from that history.
When Loandock cannot settle an item, it stops and puts the item on your processor’s list.
Does Clara run on our processors' computers?
Clara runs on Loandock-managed servers. Your team does not need a separate local computer for each loan. During onboarding, we agree which systems Clara will use and the access needed for the work.
Data handling
The security page covers hosting, access controls, retention and incident response. Loandock’s information security policy and supporting documentation are available on request.
Bring your workflow and access questions to the walkthrough. You do not need to prepare a file.


