What Actually Happens When You Deal With West Mall Seven
West Mall Seven is a coordinating body that emerged from the mixed-use development project in the western district around 2018. It handles vendor oversight, permit enforcement, and dispute resolution across seven associated commercial properties. Most people encounter it when they're trying to get approvals for tenant improvements, signage changes, or common area maintenance. It is not glamorous work, and the process is not streamlined. Here is the straightforward part: there are seven designated stakeholders, each representing a different property or department within the consortium. They meet biweekly, usually on Tuesday afternoons, and decisions require a majority vote unless it is a budget override, which needs unanimous consent. That structure sounds simple enough on paper. In practice it means a single stubborn property manager can stall your entire application for three weeks while they sit on it. I spent about fourteen months working with them on a renovation project. What I learned is that the paperwork queue is completely separate from the actual decision-making. Your submittal goes into one system, gets logged, and then disappears into a holding pattern while someone manually routes it to the right person. I stopped tracking when things were submitted and started tracking when I actually got a response. The average wait time from submission to first acknowledgment is about twelve business days. From acknowledgment to approval or denial, another eight to ten days.
How to Actually Get Things Approved
Submit everything through the electronic portal, not by email. I learned this the hard way. Early on I sent a supplemental document directly to a committee member's inbox, assumed it would get filed properly. It did not. It sat in an unread pile until I called six weeks later and found out it had never made it into the official record. After that incident I made sure every single attachment went through the portal, even when a contact told me verbally that email was fine. Email is fine until it is not fine, and then you have no paper trail. Use the standardized form package. They have a set of templates for different project types: tenant improvement, signage, structural alteration, facade modification, exterior lighting, HVAC rooftop work, and common area remodeling. Pick the right one and fill it out completely. Incomplete forms get returned within forty-eight hours, and that clock resets when you resubmit. A fully complete form that meets their requirements typically gets acknowledged and moves into review within two weeks. Include a site plan with dimensions, a materials schedule, and a compliance matrix. The compliance matrix is the part most people skip. It is a simple table where you list each relevant code section or covenant requirement and note how your proposal satisfies it. They receive hundreds of applications a year and very few people include this. Having it upfront saves them from making a request for additional information, which is the single biggest delay factor I encountered.
Edge Cases and Workarounds
There is a scenario that comes up occasionally and is not documented anywhere in their materials. If a project crosses property lines between two or more of the seven member buildings, the standard submission process breaks down. Each property's representative will claim jurisdiction over their portion and then wait for the others to act first. This is what I called a boundary overlap, and it cost me roughly five weeks on one project because I submitted a single application without flagging the cross-property element. The workaround is to file parallel submissions, one per affected property, but reference each other in the subject line and include a cover memo explaining the overlap. Label it as a coordinated application. This forces each representative to see that the other submissions exist and triggers the internal coordination step that normally gets skipped. It added about two extra days to the initial filing process but cut the total resolution time by nearly three weeks compared to waiting for the back-and-forth that happens when nobody takes ownership. Another thing that catches people off guard: the biweekly meeting schedule is not fixed to a calendar month. They rotate based on which properties have the highest volume of pending applications. Some months there are extra sessions. Other months the regular meetings get canceled due to holidays or staff absences. I kept a running log of meeting dates over a twelve-month period and found that roughly one in five scheduled meetings was either canceled or moved. If your timeline is tight, build in a buffer for this.
Get the Full Details
When It Falls Apart
The system works reasonably well for routine applications. It breaks down in two specific situations. First, when multiple properties are involved in a dispute about responsibility for shared infrastructure, like a common parking structure or a shared HVAC system. The voting process cannot resolve a conflict where two members have opposing interests. These cases tend to linger indefinitely unless external mediation is initiated, which is rare and usually requires legal involvement. Second, the unanimous consent requirement for budget overrides is a bottleneck that is rarely discussed. If any single member disagrees with a spending allocation, the entire budget cycle stalls. I watched a $400,000 common area upgrade get frozen for eleven months because one property owner refused to sign off on a contractor selection. The workaround in these situations is to restructure the proposal into smaller line items that fall below the override threshold, but this requires advance knowledge of the financial limits, which are not publicly posted. The cutoff appears to be around $75,000 per line item, but that number has shifted slightly over the years. If you are dealing with a dispute-heavy project or something that might trigger a budget override, the faster route is often to go outside the standard process entirely and negotiate directly with each property owner before filing anything. It is slower on the front end, maybe two or three weeks of meetings, but it prevents the application from getting stuck in committee limbo for months.
The portal itself can be frustrating to navigate. The search function for past approvals is essentially nonexistent, so if you need to reference a previous similar project for justification, you are mostly on your own. I ended up emailing three different former committee members and asking for copies of old approval letters. Most of them obliged, but there is no guarantee of cooperation, and some members do not respond at all. For straightforward projects this group is manageable if you respect the process and prepare thoroughly. For anything that crosses property lines or involves significant spending, you need a different strategy from the start. The rules are not complicated. The execution is what slows people down.
