YH
01 Homeowner
Never sees a workflow engine. Just: "Kitchen tiles require your approval, +JOD 320, no schedule impact. Approve / Ask a question."
Dashboard
Personal experiment
Home renovation without the WhatsApp chaos.
Can I model complexity?
What the homeowner actually sees. No dashboard, no jargon.
A renovation project runs through a chain of people who all have different responsibilities, approvals, documents, and dependencies: homeowner, architect or designer, contractor, subcontractors, suppliers, inspector. Right now that chain runs on WhatsApp threads, and a single discovery (say, a contractor finding unexpected plumbing behind a planned kitchen wall) turns into 27 messages instead of one clean decision: issue raised, contractor adds photos and a proposed change, architect reviews, homeowner sees the cost and time impact, homeowner approves, contractor proceeds, work is verified, change is closed.
Everyone in this application
Build an approval flow (add steps, set single or multi-reviewer rules), then run the sample application through it and see how the decision moves, stalls, or gets rejected. This is the same engine RENDR would run: swap "Legal" and "Brand" for "Architect" and "Structural," and the model is identical.
No steps yet. Add an approval step to build your workflow.
Never sees a workflow engine. Just: "Kitchen tiles require your approval, +JOD 320, no schedule impact. Approve / Ask a question."
See the steps that matter to them: review queue, structural sign-off, change requests, all tied to one shared record.
Suppliers, inspectors, and subcontractors plug into the same chain at exactly the step that needs them, no more.
RENDR is a personal experiment built to exercise one specific ability: modeling multi-party complexity into workflows, roles, states, and exceptions that hold up under real messiness. It sits alongside, not inside, Issa Nijmeh's professional portfolio.