Interactive demo · synthetic data

Approvals playground — a rules-driven workflow in three minutes

Create a purchase request, change the budget and the threshold, act as the employee, the department manager or finance, and read why each decision was allowed or blocked. No account, no server; everything stays in your browser.

1Configure the request

Request amount (EGP) Available budget (EGP) Finance review above (EGP) Requester

Purchase purpose

2Act as a team member

Acting role Reason (required for reject / return)

Start a request to run the rules.

3Decision & route

—

WF-01	A requester cannot approve their own request.
WF-02	The amount must not exceed the available budget.
WF-03	Finance approval is required above the threshold; a manager's own request always goes to finance.
WF-04	Only the role of the current stage can act; reject and return need a reason.

4Audit trail

Event	Actor	Explanation

What this does and does not prove. A working browser-side rule engine with editable inputs, role guards, state transitions and an audit trail, with repeatable checks. It is not a customer system, not a backend, and not evidence of past client results. The two engines in the lab — docrecon and docflow — are the serious ones; this page is the warm-up.

Have an approval process that lives in e-mail today?

Tell us the steps, the roles and the system the decision has to land in. You will hear back from the owner within two working days.

hello@dalteno.com WhatsApp