Source material
Start with the record
A review decision should point back to the spec, drawing, file, comment, or PDF page that shaped it. We design around source material because project memory is too fragile for formal approvals.
About ConstructFlow
Built for the firms
Built for the firms
running the work.
ConstructFlow provides the operational reliability and source-backed intelligence required for high-stakes construction document review.
Our mission
Why ConstructFlow exists
Keeping the review record accountable, source-backed, and under the people responsible for the work.
ConstructFlow exists to bring accountability and structure to complex construction review workflows. We track every decision, comment, and approval across dispersed teams, ensuring the formal project record remains source-backed, audit-ready, and firmly under human control.
A decade of document integrity
Stable review workflows since 2015
Built on construction administration practice, not chasing trends in the broader software market.
ConstructFlow began in 2015. We have spent ten years refining the rules that govern construction document review. Our platform provides a stable foundation for projects that span years and involve large reviewer groups. We prioritize continuity and technical maturity over chasing trends.
The review record problem
What we saw before we built ConstructFlow
The gap between what construction teams need and the tools they had.
- Submittal and RFI decisions were living in too many places at once: inbox threads, marked-up PDFs, meeting notes, and log exports. When a question returned weeks later, finding the source of the answer could take longer than making the call.
- Comments were moving without enough context. A reviewer note, the file version behind it, and the approval condition attached to it could be split apart by one forwarded email or one renamed attachment.
- Teams were expected to reconstruct project history with tools built for passing messages, not preserving records. Ownership, timing, and the reason behind a status change were too easy to blur.
How we build
Product philosophy
The principles that shape every review workflow decision in ConstructFlow.
Human judgment
Keep the expert in charge
ConstructFlow can organize review history and surface risk, but approvals stay with the project team. The system gives reviewers context, timing, and ownership before a status moves.
Clean handoffs
Make the next step clear
Submittals and RFIs cross firms, disciplines, and time zones. Each handoff should show what changed, who acted, and what still needs attention.
The evidence-first mandate
A citation carries more weight than a summary
Why we point to the source instead of generating answers from memory.
We believe a citation is more valuable than a summary. Our AI features focus on locating the primary record within thousands of pages of Submittals and RFIs. Instead of generating answers from memory, we link every suggestion directly to a specific comment, file, or PDF page. This approach preserves the integrity of the project record. It gives reviewers the specific context they need to make informed decisions without searching through folder structures.
The human-led review standard
Project experts remain the final authority
Our tools surface risks and draft language. Approval stays with your team.
Project experts remain the final authority on every decision. Our tools identify risks and draft responses based on the existing record, but they do not make autonomous approvals. We design our AI to assist the human reviewer instead of replacing them. This standard protects the professional judgment required for complex construction administration. Your team maintains full control over every outgoing response and final status change.
Architecture of discipline
Built for workflows where missing information has financial consequences
Operational reliability for formal document control on Submittals and RFIs.
Submittals and RFIs are high-stakes workflows where missing information has financial consequences. We built ConstructFlow with the discipline required for formal document control. Our system enforces review routing, preserves audit trails, and automates re-submittal cycles with precision. We focus on operational reliability so that project engineers and managers can trust the state of their logs at any moment.
What we stand for
Values that guide the team
Operational principles that shape how we work with customers and what we put into the product.
Clear records
Every comment, file, approval, and status change should be easy to trace without asking who remembers what happened.
Practical control
We favor controls that help teams work correctly under pressure, not rules that slow the job without improving the record.
Human authority
The software can organize evidence and reduce noise, but the project expert owns the final call.
Steady handoffs
A workflow is only useful if the next reviewer can see what changed, why it changed, and what needs action.
Long memory
Construction projects outlast inboxes, file names, and staffing changes, so the review history has to stay readable over time.
Leadership
Leadership guiding ConstructFlow
The leaders responsible for product direction, technical architecture, and practical workflow decisions for teams managing complex construction records.
Victor Perez
Founder & CTO
Andrew Rosploch
Principal Solutions Architect
Lee Lee
Principal Systems Architect
Ready for a clearer record
Bring your review record under control.
Start with the Submittals, RFIs, reviewer comments, and final PDFs your team already depends on, then keep every decision tied to the source.