GCs operating across state lines face a patchwork of pay application rules. The G702/G703 forms are standardized. The laws, customs, and expectations around those forms are not. What works in Georgia does not always work in Massachusetts. What is mandatory in California is optional in Tennessee.

This guide maps the state-level variations that affect how GCs process, certify, and manage G702/G703 pay applications.

State Prompt Payment Act Variations That Affect G702 Processing

Prompt payment acts create enforceable timelines for construction payment. Every state has one. The details vary significantly, and those details directly affect how fast you must process a G702 once it hits your desk.

The clock starts differently by state. In some states, the prompt payment clock starts when the owner receives a proper pay application. In others, it starts when the architect certifies payment. In still others, it starts when the GC receives payment from the owner (for GC-to-sub payments).

This distinction matters because architect certification can take 7-14 days. A state where the clock starts at receipt of the pay application gives the GC less total processing time than a state where the clock starts at certification.

Penalty rates are not uniform. Penalty interest for late payment ranges from 1% per month (12% annually) to 2% per month (24% annually). Some states peg the rate to the prime rate plus a statutory premium. Others set a flat rate. A few states allow the prevailing party in a prompt payment dispute to recover attorney fees, which can exceed the interest penalty.

Region	Fastest Payment States	Payment Window	Penalty Rate
Southeast	Georgia, Florida	15-25 business days	1% per month
Northeast	Massachusetts, Connecticut	30 days	1.5% per month
Midwest	Ohio, Michigan	30 days	1-1.5% per month
West	California, Oregon	30 days	2% per month
Southwest	Texas, Arizona	35 days	1.5% per month

Pay-when-paid vs. pay-if-paid. These contract clauses interact with prompt payment acts differently by state. Most states prohibit pay-if-paid clauses (the sub gets paid only if the owner pays the GC) on public projects. Some states have extended that prohibition to private projects. Pay-when-paid clauses (the sub gets paid within a reasonable time after the owner pays the GC) are generally enforceable but subject to state-specific reasonableness standards.

A GC using a pay-if-paid clause in a state that prohibits it is violating state law. The clause is unenforceable, and the GC owes payment within the statutory timeline regardless.

States Requiring AIA Forms on Public Projects

No state mandates the AIA G702/G703 by statute. But many state and local agencies specify AIA documents in their standard contract language, effectively requiring them on publicly funded work.

How the requirement works: The project manual or contract general conditions reference AIA Document G702 as the required pay application form. This is a contractual requirement, not a legal mandate. But on a public project, the contract terms are non-negotiable.

States and agencies that commonly specify AIA forms:

California: CalTrans and many local municipalities use AIA-based contracts that reference G702/G703.
New York: State agencies frequently specify AIA documents. NYC DDC projects use modified AIA forms.
Illinois: CDB (Capital Development Board) projects require AIA-format pay applications.
Massachusetts: DCAMM projects specify AIA contract documents including G702/G703.
Florida: DOT projects use state-specific forms, but many local government projects specify AIA.
Texas: TFC (Texas Facilities Commission) projects frequently reference AIA documents.

Alternatives on public projects: When the contract does not specify AIA forms, public agencies often have their own standard pay application forms. Federal projects use SF 1443. State DOT projects typically use state-specific forms. The data fields overlap significantly with the G702/G703, but the formats differ.

GCs working on multiple public projects should maintain the ability to produce both AIA-format and agency-specific pay applications. The underlying data is the same. Only the form layout changes.

Regional Retainage Customs

State law sets the retainage ceiling. Regional custom sets the retainage floor. In many markets, the actual retainage rate is lower than the statutory maximum because competitive pressure drives GCs and owners to offer more favorable retainage terms.

Northeast customs: Retainage in New York, New Jersey, and Connecticut markets typically runs at 10% through 50% completion, then reduces to 5%. Union labor agreements in some trades include retainage provisions that interact with the contract retainage schedule. The reduction at 50% completion is contractual, not automatic; GCs must actively process the reduction.

Southeast customs: Florida and Georgia markets have trended toward 5% flat retainage throughout the project. This reflects both statutory caps and competitive pressure from subs who prefer predictable cash flow. Retainage release at substantial completion of the sub's scope (not project completion) is standard practice.

Midwest customs: Ohio and Michigan markets retain the traditional 10% to 5% reduction structure. Prevailing wage projects add complexity because retainage calculations interact with certified payroll reporting. Some public agencies require retainage to be held in an interest-bearing escrow account.

West Coast customs: California's 5% statutory cap on public projects has pushed private project retainage toward 5% as well. Washington and Oregon follow similar patterns. Retainage release is often negotiated at substantial completion rather than final completion, giving subs access to retained funds months earlier.

Southwest customs: Texas retainage practices are in transition. Recent legislative changes have tightened retainage requirements, and the market is moving from 10% to 5% on both public and private work. Arizona follows a similar trend.

Impact on the G703: The retainage column on the G703 must reflect the contractual retainage rate, any state-mandated caps, and any negotiated rate reductions at completion milestones. A single G703 may have line items at different retainage rates if some items have reached the reduction threshold and others have not.

State Certification Requirements

The G702 certification is a formal statement that payment is due. On private projects, the certification follows the contract terms and standard AIA language. On public projects, states layer additional certification requirements.

Sworn statement requirements: California, Florida, Illinois, Michigan, and Ohio require a sworn statement from the GC certifying that all subs and suppliers have been paid from prior draws. This statement supplements the G702 and must be submitted with each pay application. Failure to include the sworn statement can delay payment processing.

Sub payment certification: Several states require the GC to certify specific change order and sub payment information with each draw:

California: The GC must provide a conditional waiver and release upon progress payment per Civil Code Section 8132.
Florida: The GC must provide a partial release of lien with each application for payment.
New York: On Wicks Law projects, each prime contractor certifies independently rather than through a single GC.

Architect certification variations: The architect's role in certifying the G702 varies by state and project type. On some public projects, the state agency's construction manager certifies payment instead of (or in addition to) the architect. This adds a review layer that extends the payment processing timeline.

Electronic Submission and Digital Signature Rules

The shift from paper G702/G703 to digital submission is accelerating, but state rules on electronic signatures and digital records vary.

UETA adoption: 49 states have adopted the Uniform Electronic Transactions Act (New York adopted its own Electronic Signatures and Records Act instead). Under UETA, electronic signatures on G702 forms carry the same legal weight as wet ink signatures. This removes the legal barrier to digital pay app processing.

State-specific electronic requirements:

Virginia: State agencies must accept electronic pay applications when the contractor offers digital submission.
California: Recent legislation requires state agencies to accept and process electronic pay applications within the same timelines as paper.
Colorado: Electronic submission is permitted on all public projects. The state maintains a digital portal for pay application processing on state-funded work.
Georgia: GSFIC (Georgia State Financing and Investment Commission) projects support electronic submission through an online portal.

Practical considerations: Even in states that permit electronic submission, the owner, architect, or agency may have specific technical requirements: file format (PDF/A for archival), digital signature certificates (from specific providers), metadata requirements, or portal-specific upload procedures.

Building a Multi-State Process

GCs operating in three or more states need a scalable approach to state-specific G702/G703 compliance.

Step 1: Build a state compliance matrix covering prompt payment deadlines, retainage caps, certification requirements, and documentation mandates for every state where you hold a license.

Step 2: Set your base process to the most restrictive state in your portfolio. Process pay apps within the shortest deadline. Hold retainage at the lowest cap. Include all certification documentation. This approach eliminates the risk of accidentally applying the wrong state's rules to a project.

Step 3: Train project teams on state-specific deviations. The base process covers 90% of requirements. The remaining 10% is state-specific language, forms, or documentation. A 30-minute orientation for each project covering the applicable state requirements prevents compliance failures.

Step 4: Audit your process annually. State prompt payment acts and retainage laws change frequently. At least 8 states modified their construction payment laws between 2023 and 2025. An annual review of your compliance matrix keeps your process current.

Frequently Asked Questions

Can a sub file a prompt payment claim even if the pay app had errors? It depends on the state. Most states require a "proper" pay application to start the prompt payment clock. A G702/G703 with material errors may not qualify as proper, meaning the clock does not start until a corrected submission is received. However, the GC must notify the sub of the deficiency promptly, typically within 7-14 days.

Do retainage caps apply to change order work? Yes. State retainage caps apply to the total contract value, including approved change orders. You cannot hold 10% retainage on change order line items when the state caps retainage at 5% on the base contract.

What if my state has no prompt payment act for private projects? A few states have limited or no private project prompt payment statutes. In those states, payment timelines are governed entirely by the contract. Include clear payment terms in your subcontracts and enforce them consistently.

Can an owner require a longer payment period than the state allows? No. Prompt payment acts are statutory minimums that cannot be waived by contract. A contract requiring 60-day payment in a state with a 30-day statute is unenforceable beyond 30 days. The sub can demand payment at day 30 regardless of the contract language.

How do I handle a project that spans two states? Apply the more restrictive state's requirements. If the project is physically located in one state, that state's laws govern. For projects spanning a state line (pipeline, highway), consult legal counsel on which state's prompt payment and retainage laws apply to each project segment.

Are there federal prompt payment requirements that override state laws? The federal Prompt Payment Act applies to direct federal contracts, not to state-funded or private projects. Federal projects governed by FAR have their own payment timelines (14 days for progress payments) that exist independently of state law. On federally funded but state-administered projects (like FHWA highway projects), both federal and state requirements may apply, and the more restrictive governs.

Multi-state compliance does not have to be complicated. SubcontractorAudit tracks state-specific retainage rules, prompt payment deadlines, and documentation requirements across your entire project portfolio. Explore pay app audit.