Procurement · Legal · Finance حالة استخدام
Tendering, from need to signed contract
A tender passes seven stages, many teams and many documents before anyone signs a contract.
Each decision must stand up to a challenge from a bidder or an auditor.
Here is how agents prepare the work while a workflow and people stay in control.
- For
- heads of procurement, tender boards, legal counsel, CFOs and enterprise architects.
- In the demo
- Supplier qualification and onboarding run in the Falak demo today. The other six stages are design.
On this page
01The process today
A tender is slow because each stage waits for documents, answers and sign-offs.
A unit needs a service, for example maintenance for three sites. Procurement plans the tender. Legal checks the documents. Bidders ask questions. A committee scores the bids, and the approval authority awards the contract.
- Initiate and plan. Requesting unit, procurement.
- Supplier management. Procurement, risk, legal. Runs in the demo today.
- Prepare tender. Procurement, legal. Waits for legal review.
- Engage bidders. Procurement. Waits for answers to bidders.
- Evaluate. The committee. Waits for committee time.
- Award. The approval authority.
- Contract and handover. Legal, the contract owner.
Every answer must reach all bidders in the same words. If a bidder challenges the result, you must show who decided what, on which evidence.
What to do next: count the days at each stage of your last three tenders.
02Where agents fit
A workflow runs the tender. One agent prepares each step. Code checks. People decide.
Many designs for tendering put an AI orchestrator in charge of seven agents that call each other. Falak uses a different design:
- The workflow is code, not AI. It knows the stages, the approvers and what to do when a step fails. It does not drift.
- Each agent gets one task and returns one proposal. No agent calls another agent or sees the whole tender.
- Agents read in parallel. Writes happen one at a time, once, after approval.
Only the row marked demo runs on Falak today. The other rows are design.
| Stage | Agent prepares | Code checks | Person decides |
|---|---|---|---|
| Plan | A scoped need | Budget, procedure by value | Procurement lead |
| Suppliers (demo) | Evidence, duplicates, screening | Duplicates, screening, the ERP write | Procurement. A specialist on a screening match |
| Prepare | Draft documents, a checklist | Clauses, weights, dates | Legal and the owner |
| Engage | Draft answers | Same answer to all bidders | Procurement, every message |
| Evaluate | Each bid against the criteria | Completeness, score sums | The committee scores. Never the agent |
| Award | A recommendation | Authority, separation of duties | The approval authority |
| Contract | A contract draft | Contract matches the award | Legal, the contract owner |
Each action has an autonomy class. It says how far the agent can go without a person. In a tender, agents stay at A0 and A1, and every decision is A3 or A4:
- A0 reads only.
- A1 prepares, does not act.
- A2 acts within set limits, and the action can be undone.
- A3 waits for a person to approve.
- A4 is for people only. The agent hands the case over.
03One request, end to end
One tender runs as one workflow, from the need to the signed contract.
A facilities team needs maintenance for three sites. One workflow run takes it through all seven stages:
- Plan. The procurement lead approves the scope.
- Suppliers. New bidders go through the onboarding demo.
- Prepare. Code checks that the weights add up to 100. Legal approves the pack.
- Engage. Procurement approves each answer. All bidders get the same text.
- Evaluate. The agent fills one sheet per bid. The committee scores and signs.
- Award. The approval authority approves the exact recommendation.
- Contract. Code checks it against the award. Legal approves, and Falak closes the task.
- Workflow gives the agent one task.
- Agent returns a recommendation with evidence.
- Code checks the authority and the duties.
- Approval authority approves the exact text.
- Workflow checks that nothing changed.
- ERP records the award once.
- Workflow reads it back. Stage 07 starts.
The guards against failure run in the demo today, on supplier onboarding:
| Case | What Falak does | In the demo |
|---|---|---|
| A bid hides an instruction | Treats the bid as data. Denies the message and logs it | Live, as Helios |
| A score changes after sign-off | Refuses to continue. The committee signs again | Live, as the changed bank account |
| An auditor asks why | Shows every action, score and denial in a chained log | Live, in the Audit tab |
What to do next: list each decision in your last tender, and who made it.
04Controls that make it safe
Every message to a bidder and every score is a decision. Falak sets who makes it before the agent runs.
Falak writes every action and its result to an action record (the ledger).
| Action | Class | Who approves | If it fails |
|---|---|---|---|
| Read a bid | A0 | Nobody | Nothing to undo |
| Draft a document | A1 | The owner, before use | Nobody uses the draft |
| Send a clarification | A3 | Procurement. Never with another bidder's prices | Falak sends nothing |
| Record a score | A4 | People only | A later change voids the sign-off |
| Recommend the award | A1 | Nobody. It goes to the authority | Nothing changes |
| Issue the award | A3. A4 for high values | The approval authority | A changed text voids it |
| Create the contract | A3 | Legal, on the exact draft | One key, never a second contract |
Each approval binds to the exact action. The kill switch stops an agent at once. The audit log is a chain, so a changed entry shows.
What to do next: write this table for your tender rules before anyone builds.
05Build it on Falak
A tendering pack holds what is specific to tenders. The platform supplies the rest.
A pack holds agent definitions, prompts, tools, a rule set, schemas, demo data and eval cases. Eval cases are tests that run before each release. A tendering pack needs five agents, not seven. Stage 02 uses the procurement pack. Stages 05 and 06 share one evaluation agent.
| Part | Procurement pack, today | Tendering pack, design |
|---|---|---|
| Agent definitions | 1 | 5 |
| Tools | 6 | One per system action |
| Eval cases | 16 | From your past tenders |
We counted the procurement pack on 25 October 2026. The platform supplies intake, the durable workflow, approvals, the tool gateway, the action record, audit, search and the kill switch.
What to do next: list your documents, systems and approvers for each stage.
06What to measure
Measure each stage and each correction from the first tender.
These are measures to track, not results that we report.
- Cycle time from need to contract, and days per stage.
- Clarification turnaround, and addenda after publication.
- Evaluator hours per bid, and score corrections after sign-off.
- Tender challenges, and the share of tenders with a complete audit trail.
Falak keeps a timeline of each task, so cycle time and days per stage come from its own records.
What to do next: take a baseline for three of these numbers now.
07Expand from here
After the award, the same parts run the contract and the next tender.
These are design, except procure-to-pay, where two stages run in the demo today.
| Next process | It reuses | It adds |
|---|---|---|
| Contract changes | The contract agent, approvals | Change rules |
| Supplier reviews | Supplier record, score sheets | A review schedule |
| Framework call-offs | The tender pack, approvals | Call-off rules |
| Procure-to-pay | Supplier record, the award | Orders and invoices |
What to do next: choose the process that starts right after your awards.