For development teams
Every permit and condition, with an owner
Blue Orchid reads municipal letters, contractor bids and lender checklists, connects each open item to the project, and drafts the next response when asked for a person to send
What it handles
What the project team stops reconstructing.
- 01
Track outstanding approvals
See which approvals, permits and municipal requests are open, who owns each response and what was submitted.
- 02
Compare contractor bids
Line bids up on scope, exclusions, allowances and assumptions, with the page behind each difference.
- 03
Connect change orders to scope
Tie each change-order request to the original scope and the correspondence that led to it.
- 04
Prepare draw packets
Gather the evidence for the next draw request against your lender's checklist and list what's missing.
One workflow, start to finish
How a city comment letter gets answered.
Follow one comment letter from the planning department to a response plan with owners.
Blue Orchid reads the approved email and the city's letter. The original stays linked.
Ask the deal file
Questions project teams ask it.
Which approvals, permits and city responses are still open on this project?
Which approval conditions still need a follow-up?
What did the city ask for, who owns the reply and what did we submit?
Which milestones are waiting on the same approval?
What's blocked right now, and what would clear it?
Sources
Where the answers come from.
Each source is set up with your team, and you choose what it reads.
Approvals
What waits for a person.
- Submissions and replies to the city or utilities
- Messages to contractors and consultants
- Change orders and anything that moves the budget
- Schedule changes you ask for, before others see them
FAQs
What teams ask before starting.
Explore the work
Other teams on the same deal file.
Bring one deal your team keeps chasing.
We'll set it up there with your team, then walk you through each answer and approval.