SP4N reads the schedules, drawings, specs, RFIs and contracts in your project records, raises candidate issues, and links each one to its supporting source. A reviewer on your team can approve, flag or reject each finding and decide the next action; findings are candidates for review, not conclusions.
Construction-specific reasoning modules combine your schedule, documents, weather context, and supplier signals to flag risks before they land.
prediction · WED rain front pushes the A-04 pour past its cure window → resequence MEP sleeves to THU to protect the critical path.
Construction-specific reasoning modules are grounded in your project record - every finding is anchored to a source document, computed from schedule math, or explicitly labeled as an assumption.
The subcontract omits through-wall flashing at head conditions required by the enclosure package - a six-figure exposure if discovered after mobilization.
Provide continuous flashing
at sill and jamb conditions.
Provide through-wall
flashing at head w/ end
dams & weeps per detail.
Coordinate w/ masonry.
…
A ranked list of what slipped, what's at risk, and exactly what to do about it - per activity, with the reason why.
Each file read reports whether it was covered in full or in part.
PDF documents, plain text files, and CSV files.
Primavera P6 XER files and native XML schedule files.
Word (DOCX), Excel (XLSX, XLSM), and PowerPoint (PPTX) files.
IFC files, including zipped IFC (.ifczip) with a single .ifc. Geometry is not interpreted.
ASCII DXF files, read as text. Geometry is not interpreted.
DWG is not read natively. Export DWG drawings to PDF or DXF first.
Illustrative workflow visuals; not project results.
Findings can link to project evidence for reviewer inspection.
Dollar and duration estimates require project-specific review.
Review the records available for each analysis run.
