Software architects should be involved in earliest system engineering activities
A software architect that can't code or refuses to has no business architecting the system. 
A software architect who doesn't show up to stand ups really shouldn't be dictating a solution to the team who have to build it. 
Ideally the software architect should be as hands on as possible with the team leads as the system is built up to the point that the architecture is proven or at least to see if the assumptions around the architecture actually hold up. 
Really strictly on teams leads to accurately communicate the architecture before it has been proven to hold up is risky.