On premium residential projects, the architect typically conducts periodic site visits during construction to confirm that the work is matching the construction documents. The frequency of these visits varies from weekly to monthly; the value of each visit depends partly on what is available to inspect when the architect arrives.
We structure our documentation to maximize the value of every site visit.
What we provide before each scheduled visit
A pre-visit summary, sent 48 hours before the visit:
- Current project status
- Specific items completed since the last visit
- Items the architect should review at this visit
- Any decisions pending the architect's input
- The agenda for the visit
The pre-visit summary lets the architect arrive prepared — they have already reviewed the photographs of the recent work and have specific questions ready.
During the visit
The project lead from our team is on site during the architect's visit. The visit typically includes:
- A safe roof inspection (the architect on a hard surface, viewing from a safe vantage; or via drone if roof access is impractical)
- Review of in-progress flashings and transitions
- Review of any field decisions made since the last visit
- Discussion of upcoming phases
- Punch-list items if applicable
The visit is structured but not formal. The architect's time is finite; the visit should be productive, not theatrical.
After the visit
A written summary within 24 hours:
- Topics discussed
- Architect's decisions or directions
- Items to be addressed before the next visit
- Any documentation requested by the architect
The summary is the record of the visit. It goes to the architect, the GC, and the owner.
What the architect cares about
In our experience, architects on these projects focus on three things:
1. Compliance with the architectural intent
Does the installation read as the architectural drawings intended? This is the most subjective category and the most consequential for the final result. The architect's eye on the in-progress work is the only way to catch deviations early.
2. Material quality
Is the field material being installed actually the material specified? Are the flashings the correct material and gauge? Are the attachment patterns matching the specification?
3. Detail execution
How clean are the cuts? How crisp are the seams? How accurate are the bevels at hips and valleys? This is craftsmanship; it cannot be quantified, but it can be observed.
What we will not do during a site visit
Defend a poor installation
If the work is below standard, we say so and propose a remedy. We do not minimize the issue or attribute it to factors outside our control.
Argue with the architect about design
The architect's design intent is final. If we disagree about a detail, we propose alternatives or accept the architect's call. We do not relitigate at the site visit.
Promise a schedule we cannot meet
If the schedule has slipped or is at risk, we communicate honestly. Inflating a date that we cannot hit destroys the relationship.
What goes well
The architects we have worked with multiple times typically describe four things that make our process work:
- Visible commitment to the design intent. They can see in the field that we are building toward the drawings.
- Documented decisions. Every conversation produces a written summary; nothing relies on memory.
- Reasonable accommodations during construction. Architects make small adjustments during construction; we accommodate without resistance.
- Honest communication about risk. When something could go wrong, we tell them before it does.
These four behaviors are the foundation of architect-roofer working relationships that produce great work. We have built the practice around them.
A note on contracted services
Most of our work is subcontracted under a general contractor's prime. In these cases, the architect's site visits are coordinated through the GC, not directly with us. Our documentation goes to the GC, who shares with the architect.
When we work directly with an owner (no GC), we coordinate visits with the architect directly. The process is the same; the channel is different.
Filed under