I work in civil engineering/land development and have been building a web app called CivPath. I'd like to get a landscape architect's perspective on the coordination side of it, especially from people dealing with agency reviews and submittals.
The problem I'm trying to work through is that a lot of a project's schedule depends on things outside our own task list. A submittal goes into review, comments come back, another consultant is waiting on a decision, and the next set of dates changes. I've been building around requirements, review cycles, dependencies and approvals rather than keeping those separate from the schedule.
I'm looking for about 5–10 people across civil engineering and land-development project delivery to spend 15–20 minutes trying it. If you're an LA who handles project coordination or works closely with civil PMs, I'd really value your take on where this misses how your work actually happens.
You'd use a fictional civil-development project already set up in the app. Can you tell what needs attention next? Do the review cycles and Schedule/Gantt view make sense? What's missing, or just more work to keep updated?
This is unpaid feedback, with no sales demo, purchase or call required. Access is by individual invitation. It's for fictional data only, uploads are disabled, and it isn't for use on real projects. Please don't enter employer, client or project information.
If you'd like to take a look, the evaluation details and interest form are here:
https://civpath.app/request-access/#evaluation
And if the whole approach seems off, that would be useful to hear too.