01
Built for general contractors and specialty trades
Run bids, jobs, RFIs, and field reporting.

What teams are solving
Field teams entering data twice, once on paper, once in software
Subcontractor and vendor onboarding done over email
Pay apps and lien waivers in spreadsheets
One record. Every workflow.
02
Daily logs
03
RFIs & submittals
04
Punch lists
05
Pay apps
What you can improve
Current project, budget, commitment, and change context in one place
Clear ownership for approvals, field issues, and closeout work
Consistent reporting across projects without rebuilding every spreadsheet
Works with your stack
Project and field systems
Connect schedules, field observations, and project records to shared operating data.
02Accounting and ERP
Keep financial systems authoritative while operational work stays current.
03Communication
Bring alerts, approvals, and follow-up into the channels teams already use.
04Documents and files
Connect source documents to the records, decisions, and workflows they support.
A few common questions
Can we start with one project?
Yes. A representative project is often the best way to validate records, permissions, and reporting before standardizing across the portfolio.
How does Path handle project-specific workflows?
Teams can share a common operating model while extending forms, approvals, and dashboards for the needs of a project or business unit.
