What we’re building
One record, from the deck to a decision.
A fictional Parkview example. Each step below opens the Renakin app on the same problem in its sample project: Slab S-23, Floor 23, Area 3, blocked, rebar short.
Try it once-
Capture
Alex taps the area, the state and, if he has one, a photo. His name and the time travel with it.
Try capture in the app -
Locate
The record opens at its floor and area on the building, not in a chat thread.
Try locate in the app -
Evidence
The original photo and every response photo stay separate, each with who and when.
Try evidence in the app -
Assign
Sam names Chris as owner; Chris routes the work to Pat. Routing does not clear the blocker.
Try assign in the app -
Materials
Jamie records the supplier’s dated promise and its source; Taylor records what arrived. A promise is not a receipt.
Try materials in the app -
Drawings
Lee records a new drawing reference. Pat acknowledges it, and work answered on an older one cannot be accepted.
Try drawings in the app -
Respond
Pat answers from the foreman’s own screen with a new photo and a note. No photo, no review.
Try respond in the app -
Review
Jordan reviews it independently: accept, or rework with a reason. Not a permit to pour.
Try review in the app -
Share
Chris publishes a separate, curated update. Emma sees that, never the internal record.
Try share in the app -
Activity
Every step keeps who, when, what and why. Added to, never overwritten.
Try activity in the app
The film above is an illustration. The app is a working prototype: its sample project is fictional, what you add stays in this browser, sign-in codes show on screen and nothing syncs. It gives no construction approval.