Software architecture evaluations systematically allows to check for software architecture fitness regarding the context and business. There are always some challenges and issues that the reviewers need to consider for successful architecture reviews. In the context of a software system development by an external company for a Chilean R&D and engineering institution, we decided to carry out an architecture review. Due to that architecture reviews were not considered in their initial planning, DCAR was chosen because the authors claim it to be actionable and quick to run. In this article we present the lessons learned and benefits we observed such as recording decisions’ rationale discussion, emergence of technological issues and rethinking of some previously made architectural decisions. Lastly, we conclude that the impact in the project planning can be minimized if some activities are carried out in an offline fashion.