Trigger
W
S
N
V
F
D
A request changes, a supplier response is recorded or a review date arrives. Configured events and schedules start the case. Nobody has to prompt it.
Trusted by ambitious companies
Fill prepares the next step, carries out supported actions and brings exceptions to the right person. Your team keeps control of who you engage, what you commit and what happens outside policy. Clear permissions. Visible actions. Human approval where required.
Trusted by ambitious companies
A request changes, a response arrives or a review becomes due. Fill uses the relevant records and configured rules to carry out supported work, then either completes the step or asks for the decision it needs.
A request changes, a supplier response is recorded or a review date arrives. Configured events and schedules start the case. Nobody has to prompt it.
The workflow identifies the relevant records and the policy that applies. If the framework is missing or expired, the state is Review required, not a confident guess.
Prepare or carry out the permitted step: draft, send, compare, flag. Arithmetic is deterministic. AI helps summarise, it does not improvise the total.
The case reaches the authorised person with the evidence and the impact. Approve the exception, request a revised rate or return it for clarification. Nothing binding happens without them.
The proposal reviewed, the decision maker, the decision, the time and the resulting action stay on the record. A queued email is not a delivered one; a prepared contract is not a signed one.
Reading information, preparing an action and committing the organisation are different permissions, set by the access and approval rules agreed for your programme. A supplier message is data, never an instruction.
Ask Fill
Use a question to understand a request, an assignment or a programme view. Follow the answer back to the records it came from, then take the next permitted action.
Illustrative data. Every answer names the rows it was computed from.
Model Context Protocol
Where supported, connect an approved assistant to the same records and permissions. The access point can change. The authority and the action record do not.
Available to the assistant
Illustrative. Scope follows the role the person already has in Fill.
Add Fill to an MCP-compatible client. Sign-in runs through the SSO you already use, so nobody gains access they did not already have.
Rates, contracts, engagement status and supplier history become answerable without opening another tab — and every answer still names the rows it came from.
An assistant can look at anything the person can. Changing an engagement still goes through Fill’s approval flow and lands in the same audit log.
