Construction project control
Fieldstone keeps drawings, questions, review records, and potential cost on one connected decision trail.
Interactive no-backend prototypeWorking prototype
Every control below changes local browser state. Use the navigation inside the product, complete the sample workflow, and reset it whenever you want to replay the story.
Use the reset control inside the application to return to the seed scenario.Loading prototype… / Cargando prototipo…
Starting point
The modeled contractor reviewed plans in a PDF tool, tracked RFIs in a spreadsheet, routed submittals through email, and reconciled potential changes in a weekly workbook.
The same ceiling conflict appeared under several names. Field teams kept screenshots because confirming the current sheet took too long, while review context crossed language and tool boundaries.
Customer ask
Every RFI and submittal should retain its sheet, location, specification, owner, field-need date, and revision history.
Potential change exposure should appear when the field question begins, while accounting and durable document storage remain explicit production integrations.
What we designed
The drawing desk exposes current and superseded sheets, keyboard-accessible issue markers, linked review records, and a single selected context rail.
Approving a response or changing forecast treatment updates the same prototype state, making the relationship visible without simulating a document server.
Scene by scene
A deadline runway follows field need, linked work, and potential cost—not inbox age.
Teams could count open records without seeing which decision blocked the field.
Select a linked deadline or RFI to move directly into its project context.
Revision, layer, issue, location, and review state live on the same sheet.
A screenshot removed revision status and separated the question from its room.
Change layers and zoom, then open the selected ceiling-conflict RFI.
Question, evidence, responsible reviewer, due date, and possible impact stay together.
A response could arrive without the field context needed to apply it safely.
Approve the sample response, request revision, or return to its drawing marker.
Potential cost retains its source question, drawing, trade, and forecast decision.
Field decisions surfaced in the cost report after their context was already cold.
Toggle the selected potential change in forecast and inspect the exact total.
What the concept connects
All project names, drawings, amounts, and records are illustrative. This prototype does not store documents, notify teams, authorize cost, or replace project controls.
Next application
Production traceabilityBring the people, records, exceptions, existing tools, and decisions. We will help define the smallest complete application worth building.
Discuss your applicationThe branch duct conflicts with the 9'-0" ACT ceiling and headwall support. Confirm whether the duct should reroute above the corridor or the room ceiling elevation should change.
Maintain the 9'-0" ceiling. Reroute the branch duct 18 inches east above the corridor and coordinate the diffuser neck with M-321.