← Tenderely BPM
INDUSTRY SOLUTION
Process management and software for architecture practices.
In an architecture practice the work itself is creative; everything around it repeats. Which revision round are we on, what is awaiting approval, was that change inside the contract. Tenderely BPM turns that repetition into a flow, without code.
What does an architecture practice repeat?
01
Project stages
Concept, developed design, construction drawings. Each stage has its own deliverable and sign-off; skip one and the next stage's work is wasted.
02
Revision rounds
Clients ask for changes every round. If the round number and what changed are not written down, scope creeps quietly.
03
Permits and authority paperwork
Planning, fire, utilities — each authority wants different documents on a different timetable, and one gap holds the file.
04
Coordinating consultants
Structural, mechanical and electrical packages come from different teams and wait on each other.
05
Stage payments
Payment usually follows the stage; if completion is not recorded, the invoice becomes a negotiation.
06
Site visit notes
A defect seen on site that is not photographed into the record gets discussed again on the next visit.
Where does this break down today?
Nobody counts the revisions
With no answer to "which round is this?", the limit in the contract cannot be enforced and extra work is done for free.
Approvals stay verbal
Sign-off happens in a meeting and never reaches paper, so the next round opens with "I never approved that".
Paperwork status is unclear
What went to which authority and what is still pending lives in somebody's personal notes.
Stage completion is disputed
When the invoice is due, no record showing the stage finished means the payment slips.
What changes with Tenderely BPM
01
Revision rounds count themselves
Each round is a step on the record, so the count and the changes accumulate on their own and the contractual limit becomes enforceable.
02
Approval is written and dated
Sign-off reaches the client inside the flow; the next stage does not open until it is given, and the agreement is recorded.
03
Paperwork on one screen
What went where, what is pending and what is about to expire sit on a dashboard.
04
Site notes from a phone
The same form runs in the iOS and Android apps, so photos and location attach straight to the record.
05
Payments follow the stage
Because completion is recorded, the stage payment is the next step in the flow rather than an argument.
FAQ
Can we cap revision rounds per the contract?
+
Yes. Because each revision is a step on the record, the count accumulates by itself. You can raise a warning when your limit is reached, or make approval of extra work a step in the flow.
Can clients approve inside the system?
+
Yes. The approval step goes to the client, who connects as a linked external user and sees only their own project and the step awaiting them. The next stage does not open until approval is given.
Can we include structural and MEP consultants?
+
Yes. External teams can be added as linked users who see only their own steps, or they can deliver through a public form link. Unit- and role-level permissions decide who sees what.