Every item out, every return, one traceable ledger.
Whether the item is a library book, a power tool, a piece of test equipment or a product sample, the lending cycle is the same: someone takes it, a date is agreed for its return, and without a system to watch that date, the item quietly disappears into someone's office. Tenderely BPM gives every loan a structured record — who has it, when it is due, how long it has been overdue — so the follow-up happens automatically instead of depending on someone's memory.
What does a lending process repeat?
01
Recording the hand-out
Who takes the item, which item it is, and when they took it. Without a structured record, the only evidence of a loan is a sticky note or a verbal agreement.
02
Setting the due date
When the item should come back is agreed at hand-out but rarely written anywhere official. The borrower forgets; the lender only notices weeks later.
03
Sending reminders
A reminder the day before the due date prevents most late returns. Without automation, sending reminders means someone sitting down and checking a list every morning.
04
Tracking overdue items
Once a due date passes, the loan needs escalation: a first notice, a second, then a formal follow-up. Each tier requires a different action and a different tone.
05
Recording the return
Closing the loan when the item comes back, noting its condition and confirming that the record is settled. An unreturned return is as bad as a lost item.
06
Seeing the full picture
How many items are currently out, which are overdue, who holds what — this is the question that lending managers ask daily and can rarely answer quickly.
Where does this break down today?
The ledger is a spreadsheet nobody maintains
Rows get added at hand-out but returns go unrecorded. After a few weeks the spreadsheet is a list of items that might be out, might be back, and is trusted by nobody.
Reminders depend on a person
Someone has to check the due dates each day and contact borrowers individually. On a busy day this is skipped, and the overdue pile grows silently.
Escalation is inconsistent
One borrower gets a phone call, another is ignored. Because escalation steps are not defined anywhere, the outcome depends on who is covering that day.
There is no live view of stock on loan
How many of a given item are currently out, and when they are expected back, is information that requires searching several records or asking around — it is never just visible.
What changes with Tenderely BPM
01
Every loan is a structured record
Borrower, item, hand-out date and due date are captured in defined fields. The record is searchable and reportable from the moment the loan is opened.
02
Reminders send themselves
Set an SLA on the due date and Tenderely sends the reminder automatically — before the deadline and again if the return does not arrive. No morning checklist required.
03
Overdue tiers move through a defined flow
Conditional steps in the approval flow handle the first notice, the second notice and the formal escalation without anyone having to decide what comes next.
04
Borrowers can self-serve from outside
A public form lets a borrower submit a loan request or confirm a return without needing an account. The response lands on the same record and closes the loop.
05
Who has what is always visible
Items currently on loan, due dates approaching and overdue tiers all sit on a dashboard. The answer to any stock question is there without opening individual records.
06
The full history is auditable
Every hand-out, return, reminder sent and escalation step is logged on the record. When a borrower disputes a date or a condition, the audit history settles it.
FAQ
Can we track different types of items — books, tools and equipment — in the same system?
+
Yes. The same lending record structure works for any category of item. You can add a category field and configure different due-date rules or escalation tiers per category, all without code.
Can the overdue escalation steps be configured to match our own policy?
+
Yes. Conditional branching in the flow defines which step fires after how many days overdue, who is notified at each tier and what action is required. The policy lives inside the flow rather than in a document that people have to remember.
Can borrowers who are not staff members receive reminders or submit returns?
+
Yes. Public forms are accessible to anyone with the link, so an external borrower can confirm a return or submit a renewal request without needing an account. Their response updates the record directly.
How do we know the condition of an item when it comes back?
+
The return step in the flow can include a condition field, a notes section and an option to attach photos. Whatever is recorded at return stays on the loan record alongside the original hand-out details.
Is there a ready-made setup we can start from?
+
Yes. The Lending and Returns package installs with forms, a workflow and a dashboard already in place. You adjust the item categories, due-date rules and escalation tiers to match your operation and publish — the package is a starting point, not a constraint.