Asana vs Monday.com for Architecture Firms

Early design work moves fast and visually, with a client reviewing several concept directions before narrowing to one. Monday.com's board can attach image files directly to items, letting a principal build a visual review board a client can scroll through, with a status showing which direction is still live and which has been dropped. Asana's task attachments work similarly, with comments threading client feedback against the specific concept image it responds to, which matters when a client says option two but there have been three rounds of revisions to option two already.

Once structural and MEP consultants join, the project needs everyone working off the same milestone dates without every consultant needing full access to the architect's internal design files. A shared coordination project, scoped to cross-discipline deadlines and open coordination items, works in either tool as a layer above each firm's own internal work. The dependency this phase actually needs is structural: MEP routing decisions often can't finalize until structural framing is set, and Asana's task dependencies can enforce that ordering directly, blocking a downstream coordination task until the upstream one clears.

A permit submittal date is one of the harder deadlines in this whole sequence, since a missed submittal window can push an entire project's timeline by a full review cycle at the jurisdiction. Monday.com's timeline view is useful here specifically because it shows every drawing set's completion status against one shared date everyone can see without opening individual tasks. Track each drawing sheet's revision status explicitly, in progress, internal review, client-approved, submitted, rather than treating the whole set as one task, since a partial revision on one sheet shouldn't block visibility into the other sheets that are already done.

Once the building is underway, the work becomes reactive: RFIs from the contractor with contractual response windows, and submittal reviews on materials and shop drawings. Both tools can track this as a dedicated board with a due date calculated from your response window and a status showing reviewed, needs consultant input, or answered. The volume here can spike unpredictably depending on how complex the build is, so whichever tool you use, build the RFI due-date automation before construction starts, not after the first missed response window makes it obvious you needed it.

A mid-sized firm typically has projects in several different phases running simultaneously, one in schematic design, two in construction documents, one in construction administration, all needing different people's attention at different intensities. Architectural staff tend to stay with a firm for a while once established; broader tenure data runs around 46.8 months¹, long enough that whoever set up a project's phase structure a year ago is often still the one relying on it, which makes consistency across projects, not just cleverness on any single one, the thing worth optimizing for.

None of the phase tracking matters until a commission is actually won, and for many firms that means a competitive selection process, sometimes an RFP, sometimes an interview-based shortlist, that can run for months before a contract is signed. A new client relationship in B2B services generally takes around 91 days on average from first conversation to signature², a reasonable planning reference for how long a firm's business development effort should expect to carry a promising lead before it converts. Once won, moving that project directly into the firm's standard phase template preserves the momentum instead of losing early weeks to rebuilding structure from scratch.

The costliest mistake isn't picking Asana over Monday.com or the reverse, it's building an ad hoc structure for the first project and then discovering, three projects later, that nothing's consistent enough to compare workload or status across the firm's active roster. Build the phase template deliberately before the second project, not the fifth, so every project manager inherits the same structure rather than improvising their own, which is what eventually makes firm-wide capacity and status visibility possible instead of requiring someone to manually reconcile several different ad hoc systems.

Build one consistent structure for every project with these steps:

• Organize each project around the same phases: schematic design, design development, construction documents and construction administration.
• Track each drawing sheet individually, with a status such as in progress, internal review, client-approved or submitted, rather than one task for the whole set.
• Attach each revision as its own clearly labeled file version, so an approved sheet is never overwritten by a later, unapproved change.
• Add an automation that flags any sheet still in review as the permit submittal date approaches.
• Give structural and MEP consultants guest access to a shared coordination project, not your firm's internal design project.