The problem
One sheet. Many versions.
Assignments, revisions and status updates become fragmented between the office and the field.
Product 01 · A RENCRA product
SiteFlow
From spreadsheet
to field execution.
A working MVP for piping-spool registers, crew planning and traceable installation progress.
Working MVP · Under developmentRequest a pilot
The problem isn’t
another missing column.
Large registers tell you what exists. Field teams also need to know what to work on, what was reported and what QC has actually confirmed.
The product
A shared workflow.
Import a register, plan work and collect field events without directly overwriting official status.
The record
Evidence stays attached.
Old and new values, actors, reasons and timestamps keep the progress history understandable.
The workflow / Try it
Reported in the field.
Confirmed by QC.
An interactive illustration using one synthetic spool. It is not a live SiteFlow connection and does not save or submit real work.
Demo data · DEMO-SPOOL-001
Engineer / Plan
Set the next priority.
Assign a crew, priority and erection target. Planning stays separate from the official installation status.
- Official status
- Ready
- Assignment
- Unassigned
- Field request
- None
Start with the engineer, then explore Field and QC.
Example event history
- Example register loaded. Official status: Ready.
Built for different
places of work.
Office planning and phone or tablet reporting need different interfaces. SiteFlow keeps the record connected.
Engineer
Plan with the whole register.
- Excel/CSV mapping, validation and change preview
- Searchable lists and column filters
- Foreman and crew assignments
- Priorities, instructions and due dates
- Crew management and progress overview
Field
Report the work, simply.
- Assigned work and area browsing
- Large controls for phone and tablet
- Bulk installation reports
- Optional installation comments
- Spool-linked messages to engineering
QC
Confirm what is official.
- Review pending field requests
- Approve or reject with a reason
- Separate final acceptance
- Version and engineering-hold checks
- Decisions traced in audit history
Offline / Data
Keep working.
Keep the record.
Saved data and a local outbox
After an initial online load, downloaded registers remain accessible. Events queue on the device and retry when the server is reachable. Conflicts stay visible; official status changes only after server acknowledgement.
What offline does not mean
Closed-app background sync depends on browser and operating-system support. The local MVP is not yet a shared multi-device production deployment. Clearing browser storage removes unsynced events.
Revisions and exports
Stable IDs retain spool history through detail and number changes. Excel/CSV exports include current records, history, requests, local queue and crews. An audit export is not a complete backup/restore mechanism.
Working software.
An honest starting point.
SiteFlow is a local functional prototype using fictional sample records. It has not been verified as commercially deployed.
Available in the MVP
Register import/export, planning, due dates, field reporting, QC review, final acceptance, crew management, revision history and an offline outbox.
Before a production pilot
Validate site-specific workflow gates and data mappings. Add real identities, permissions, HTTPS hosting, backup/restore, production-scale storage and testing on target devices. The current demo roles are mocked.
Help shape the
field pilot.
Tell us about the register, the people using it and the approval workflow. We can discuss whether a scoped SiteFlow pilot makes sense.