Key Takeaways
- Verify professional licensure, local project history, and in-house technical capability before engaging any engineering consultant.
- Confirm the firm’s physical presence and operational history in Southern Utah, not merely a satellite office.
- Review completed projects on comparable terrain with similar soil and drainage conditions to avoid design failures.
- Assess in-house capabilities across all needed disciplines to prevent subcontracting delays and coordination gaps.
What defines your project's engineering needs?
What engineering disciplines does a typical development project require?
How should a project manager handle overlapping engineering requirements?
How do you verify local expertise and licensing?
What licenses should an engineering firm hold in Southern Utah?
How does local experience affect project outcomes?
- Request current professional engineering licenses for all disciplines required on the project scope.
- Confirm the firm's physical presence and operational history in Southern Utah, not merely a satellite office.
- Review completed projects on comparable terrain with similar soil and drainage conditions.
- Evaluate the firm's working relationships with local regulatory agencies and municipalities.
- Assess in-house technical capabilities across all needed disciplines to avoid subcontracting delays.
What red flags indicate insufficient local expertise?
What questions should you ask a prospective firm?
What specific engineering disciplines does the firm practice in-house?
How does the firm handle field coordination when conditions change?
Can the firm identify problems beyond the initial scope?
How do you evaluate past project performance?
What project types should a portfolio include?
How do technical capabilities factor into performance evaluation?
What common mistakes should you avoid?
Why is a vague project scope dangerous?
- Skipping the definition of the precise engineering discipline required
- Hiring based on availability rather than documented expertise
- Neglecting to verify the firm's cost-estimating methodology
- Accepting proposals that lack software-specific deliverables


