What Is BPM? No-Code Business Process Management & Automation

BPM (Business Process Management) is the practice of defining, automating and measuring the repeating work inside a company — leave requests, purchase approvals, service tickets, collections follow-up. Tenderely BPM lets you do this without writing code: you design the form and the flow, and the engine runs the approvals, timers and notifications. Two things set this module apart — an AI agent drafts most of the design for you, and every form you publish is instantly live in the mobile app.

What does business process management actually do?

A process has two parts: the FORM where data is captured and the PATH that data follows. In Tenderely BPM you design the form field by field (text, number, date, currency, choice, file, user, reference to another record, grid/matrix input), and you build the path from start, task, approval, conditional branch, timer and end steps. When a record is created the engine runs the steps in order, assigns each one to the right person and records who did what, when.

What does the AI agent design for you?

You do not have to draw the process from scratch. You describe the work in your own words — "staff leave request, the manager approves, send a reminder if unanswered within 3 days" — and the agent first asks clarifying questions, then produces the form and the flow together. What it produces is more than boxes and arrows: field types and validation rules, conditional visibility (show a field only for a given choice), timer durations, SLAs and the text plus channel of the notification sent on breach, who each approval is assigned to, even conditional row colouring in lists and the sections of the report.

The limits of the AI — and why we state them openly

The agent is a draft generator, not a decision maker. Everything it produces passes a separate validator on the server: a reference to a non-existent form, a self-referencing condition or an invalid currency code is not silently accepted — it is dropped, and you are told which item was dropped. Steps with a wide security surface, such as the node that calls an external service, are deliberately closed to the agent; you add those by hand. Dashboard figures are not produced by the AI either — they are computed deterministically on the server, and the agent only interprets them. In short: the agent drafts, you and the engine's rules decide.

Publish once — live on mobile at the same moment

There is no separate "build the mobile app" step. The moment you publish a form in the web designer, that same form appears in the mobile app with the same field rules and the same process steps. Field teams fill records on their phones, attach photos and location, and advance approval steps from mobile; the office sees the same record on the web. Designer screens stay on the web, while the working side (filling, advancing, viewing records, grid entry) runs on both platforms. Change a field and you do not need to ship a new app store version — the change applies immediately.

Approvals, branching, timers and SLAs

Processes are not limited to a single line: with conditional branching an amount above a threshold can go to a second approval while smaller amounts go straight through. Parallel branching lets you request several approvals at once. A timer step holds the flow for a duration or until a date field. Define an SLA and a warning notification is sent on breach. Notifications go out through in-app, email, SMS and mobile push channels.

Records, reports and dashboards

Captured data does not stay locked in the form. You browse records in list or calendar views and move them in and out in bulk with Excel/CSV. Analytics dashboards summarise the state with count, sum, pie, bar, table and funnel cards, and each user sees only the data they are entitled to. The report designer produces PDF reports bound to a form, including related records. The bulk operation engine updates hundreds of records at once, starts processes or completes steps.

Multi-branch and enterprise use

You can build a unit (branch/region) hierarchy and scope record visibility by unit, while management can see a consolidated cross-unit report on one screen. On forms marked as sensitive, who read, exported or reported each record is written to an access log. Many-to-many relationships, rollups from linked records, period locking and period rollover are part of the engine as well.

Do not start from zero: ready-made packages and modules

You do not have to face an empty screen. Industry packages stand up a whole line of business in one install — forms, processes, reports and dashboards arrive wired together, for education, clinics, hotels, logistics, manufacturing and more. Horizontal modules are industry independent (Human Resources, Quality Management, Purchasing, Occupational Health & Safety, Assets, Contract Management, Vehicle Fleet) and attach to your existing forms through role matching. Everything installed stays editable; a package is a starting point, not a lock-in.

What kind of work is it good for?

Any repeating work that several people touch and that needs a record: leave and expense approvals, purchase requests, quotation and contract flows, service and fault tickets, field inspections and checklists, student or patient records, maintenance plans, collections follow-up. Work scattered across spreadsheets and chat messages becomes both traceable and measurable once it lives in a single flow.

Frequently Asked Questions