Construction Lenders and Developers Cannot Agree on Draw Package Standards, and It Is Costing Both Sides

Share

Construction lenders and developers are locked in a prolonged dispute over draw package standards, with each side blaming the other for the lack of progress. Both say they want standardized draw package formats to streamline funding requests, yet neither has moved to resolve the deadlock.

Will Mitchell, Co-Founder and CEO of Rabbet, a construction finance software platform, sees the draw package standoff play out regularly. “Lenders will say they tell developers what format they want, but the developers won’t change,” Mitchell says. “Then you talk to developers, and they say they wish lenders would just tell them what format to use so they can comply.”

The draw package standoff points to a deeper problem: there is no industry-wide agreement on what a standard draw package should look like. Without consensus, every transaction requires custom negotiation, manual workarounds, and redundant documentation. The resulting inefficiencies slow project timelines and increase administrative costs.

How Inconsistent Draw Package Formats Slow Construction Funding and Raise Costs

Draw packages, the documentation that developers submit to lenders to request construction funding disbursements, vary widely in format, structure, and content requirements across lenders. The absence of a consistent standard forces developers to customize submissions for each lender relationship. At the same time, lenders must review packages in inconsistent formats, making approval more complex and time-consuming.

Mitchell argues that format variability across lenders creates unnecessary friction in what should be a routine administrative process, and that a broadly accepted standard would allow both parties to transact more efficiently.

The problem is especially pronounced for developers working with multiple lenders on different projects. Those developers must maintain separate documentation systems for each lender relationship. Lenders, meanwhile, process draw requests from various developers using different structures. That inconsistency makes it difficult to implement standard review procedures or automate parts of the approval process.

Despite the construction finance industry’s adoption of digital tools for project management and accounting, inconsistent draw package formats remain a significant gap. Mitchell points out that the issue is not a lack of technology, since most participants have access to software that could support standardization, but rather the absence of agreement on what the standard should be.

Why the Construction Finance Industry Has Failed to Agree on a Draw Package Standard

In other industries, large players or industry associations often set de facto standards that smaller participants follow. Construction finance has not produced such a standard, despite clear efficiency gains available to both lenders and developers.

Mitchell observes that lenders believe they are communicating requirements clearly, while developers claim not to receive clear guidance. This gap suggests the problem goes beyond non-compliance. In many cases, lenders may impose requirements that are too vague or overly tailored to their internal systems, making those requirements impractical as a broader standard.

Developers may receive format guidance from lenders but find the requirements difficult to apply consistently across multiple lender relationships. Conflicts between lender requirements compound the problem. Faced with incompatible demands, developers may default to their own internal formats and hope lenders will accept those submissions, rather than maintain multiple parallel documentation systems.

The conflict between incompatible requirements has produced a stalemate in which both sides express frustration but neither has enough incentive or authority to drive industry-wide change.

How One Construction Finance Platform Is Trying to Resolve the Draw Package Standoff

Rabbet is working to resolve the draw package standoff directly. “We’re working on a project to help lenders and developers agree on a format for transferring draw packages,” Mitchell says. The firm’s approach is to build a common format within its platform that both lenders and developers can adopt.

If the common format gains traction within Rabbet’s platform, it could serve as a proof of concept for broader adoption and establish a de facto standard that other software providers and market participants follow.

Mitchell says standardizing draw package formats aligns with Rabbet’s broader goal of helping industry participants transact more efficiently and use data more effectively. Standardized formats would also allow for better data aggregation, benchmarking, and analysis across projects, benefits that extend beyond administrative streamlining.

Rabbet serves both lenders and developers, giving the platform direct visibility into each side’s requirements. According to Mitchell, the platform has “about the same amount of users on both sides of the ecosystem,” which may give Rabbet enough influence to drive adoption of a common standard among its existing users.

Whether Rabbet’s common format initiative can expand beyond its existing customers to become an industry-wide standard remains uncertain. Mitchell acknowledges that broader adoption will require buy-in beyond what any single software platform can deliver, even as he sees standardizing drawing package formats as a significant opportunity for the industry.

Why the Draw Package Problem Persists Despite the Technology to Fix It

For now, inconsistent draw package formats continue to generate costly delays in construction finance. Both lenders and developers lose time and money to redundant paperwork and formatting disputes, even though the technology to resolve them exists.

The ongoing lack of consensus, rather than any technical barrier, remains the main reason the construction finance industry still lacks a standard draw package format. Until industry participants agree on a shared approach, each new project will face the same administrative hurdles, adding time and cost that standardization could eliminate.

Standardization could deliver significant efficiency gains for lenders and developers alike, but without collective action from the industry, the draw package standoff will continue to slow construction finance and add avoidable cost to every project.

Rudi Davis
Rudi Davis
Rudi Davis is Co-founder of KeyCrew and Head of Content at KeyCrew Journal, where he leads data-driven research initiatives and oversees the editorial team's analysis of real estate industry trends. His expertise in combining analytical insights with compelling narratives transforms complex market data into actionable intelligence for industry stakeholders. With over a decade in content marketing and communications, Rudi has built and exited two content marketing startups while developing innovative approaches to PR and media strategy. His agency leadership experience includes growing team size from 10 to 65 members and expanding client relationships nearly threefold, while pioneering new integrations of AI-driven media strategies with traditional communications methodology. Rudi resides in Bath, England, where he lives aboard a converted Dutch barge and runs cross-country through the English countryside.

Read more

Explore More