CDBG application errors: how to save Somerset projects

The SFY27 competitive round closed on Monday, July 6, 2026, at 2:00 p.m. sharp. Once that deadline passed, the submission window was closed; a late email, an incomplete upload, or a package that could not be opened was not something an applicant could repair at the last minute. For Somerset County, a non-entitlement jurisdiction that received $350,000 in FY2026 for a housing rehabilitation program anticipated to assist roughly 20 properties, technical errors are not harmless clerical defects. They can delay work on substandard housing, public facilities, and other rural community development priorities for an entire funding cycle.

This is not merely a paperwork problem. It is a load-bearing infrastructure problem. Grant money intended for housing repairs, drainage improvements, and community facilities can become unavailable when an application fails technical review or loses points because its supporting documents do not line up. The same risk applies to any local proposal under community block grants in Maryland: a sound project can be weakened by a submission file, a budget formula, a procurement assumption, or an income-benefit calculation that was never properly checked.

The lesson from the SFY27 round is not that applicants should produce more paperwork. It is that they need to produce a defensible record. Every document should answer a reviewer’s basic questions: Is the project eligible? Is the site ready? Is the budget credible? Will the county be able to procure and administer the work? And can the applicant prove that the project serves the people the CDBG program is designed to reach?

Navigating the SFY27 Submission Timeline and Technical Requirements

The July 6, 2026, deadline was not negotiable. The practical work, however, had to begin well before that date. A county that waited until the final week to combine exhibits, confirm signatures, test file permissions, and reconcile the budget was not really preparing an application. It was gambling that no document would fail at the point when there was no longer time to fix it.

The SFY27 submission instructions called for a defined submission format, including a consolidated PDF and the required exhibits in the requested order. Where a cloud-storage link was used, the recipient needed to be able to view and download the file without requesting access, creating an account, or navigating a permissions wall. A link that worked for the person who created it could still fail for a state reviewer using a different account or device.

That distinction matters. “The file is somewhere in the cloud” is not the same as delivering an accessible application. A reviewer should not have to reconstruct the submission from several attachments, guess which version is final, or email the applicant to unlock a folder. A technical failure at this stage can prevent the proposal from receiving the substantive consideration its project merits.

For future rounds, the safest approach is to treat the deadline as the end of a controlled process rather than as the moment the process begins. A submission manager should be able to account for:

• The current fiscal-year application form and every required exhibit
• A final PDF that opens on a device not used to create it
• Correct bookmarks, page numbers, and exhibit labels
• Signatures from the authorized officials and participating entities
• A working delivery method tested by someone outside the drafting team
• A retained copy of the exact file that was submitted
• Confirmation that the state received the package through the designated channel

The last item is easy to overlook. Sending an email does not necessarily prove that the intended file was attached, that the attachment was readable, or that a link was accessible. A responsible submission record includes the sent message, the final attachment or archive, the delivery confirmation, and an internal note identifying who completed the final review.

This is where small jurisdictions can lose ground. Staff members handling grants often wear several hats, and the person who assembles the application may also manage housing programs, public works, finance, or the county’s general administration. That makes a repeatable internal review more valuable than heroic last-minute effort. The application should be checked by someone who did not prepare each section, because a fresh reader is more likely to notice a missing exhibit, an inconsistent project name, or a budget total that changes from one page to the next.

Do not carry forward a form by habit

The SFY26 Program Policies and Procedures manual was published on August 7, 2025, and the FY2026 awards for the Lower Shore region were announced on January 23, 2026. Those dates illustrate a basic point: each funding cycle has its own documents, instructions, and review context. A prior-year file can be useful as a reference for narrative history or local background. It should not automatically become the new application.

Using an outdated template does not, by itself, establish that a proposal will be rejected. It does create a technical risk. The form may contain changed certifications, revised questions, updated exhibit requirements, or fields that no longer correspond to the state’s scoring process. A reviewer may be forced to seek clarification, or the applicant may omit information that the current form was designed to collect.

The better practice is simple: begin with the current application package, then move forward only the information that remains accurate. Recheck every carried-over number, date, map, contact, and description. “Same project as last year” is not a reason to assume the supporting file is still current.

Establishing Site Control and Environmental Readiness Standards

Site control is one of the first places where a promising project can appear less ready than it really is. Local officials may have a willing property owner, a public commitment from a partner, or a letter expressing interest in selling. Those facts can support the project narrative, but they are not the same as documented control of the site.

For acquisition, rehabilitation, or new construction, the application needs evidence that the applicant can legally carry out the proposed activity. Depending on the project structure, that may mean a current deed showing fee simple ownership, a long-term lease with an appropriate purchase option, or a contract of sale. The precise document must fit the project. A document that demonstrates control of one parcel does not necessarily establish control of adjacent property, access rights, easements, or the full service area described in the application.

The application should identify the parcel consistently across the deed, map, environmental documents, budget, and narrative. A difference in street address, tax account number, legal description, or project name may be explainable, but it creates avoidable friction. Reviewers should not have to determine whether two differently labeled parcels are actually the same property.

Environmental readiness is a related but separate question. For projects involving acquisition, rehabilitation, or new construction, the Phase I Environmental Site Assessment must be current enough to support the application and the applicable environmental review process. In the draft SFY27 materials, an ESA older than 180 days at the time of application was treated as a readiness problem. An assessment that was acceptable in January could therefore be stale by a July submission.

That does not mean an old report has no value. It means the applicant should determine whether it must be refreshed, supplemented, or replaced before relying on it. Changes at the property, new information about historic uses, or a gap between the assessment and the proposed scope can all affect the analysis. The environmental file should also match the property actually being proposed. A clean report for one building does not cure a missing assessment for another building added later to the project.

A Phase I ESA past the applicable review window is not a minor paperwork lapse. It is a readiness document that may need to be refreshed before the application can carry its full weight.

The same discipline applies to lead-based paint concerns, asbestos, floodplain questions, historic properties, and other conditions that may affect rehabilitation or construction. These issues do not necessarily make a project ineligible. They do affect schedule, scope, and cost. An applicant that identifies them early can build a reasonable response into the work plan. An applicant that discovers them after award may be forced to choose between delaying construction, reducing the scope, or finding local funds to cover an unplanned obligation.

Site control and environmental readiness should therefore be reviewed together. A county may control the building but lack a necessary easement. It may have a signed purchase contract but no current assessment. It may have completed an assessment for the original scope but later add another structure. The application is ready only when the legal, physical, and environmental descriptions all refer to the same project.

Budget Integrity: Avoiding Common Calculation and Prevailing Wage Pitfalls

The budget templates distributed by DHCD are working tools, not decorative forms. Their formulas and cross-checks are intended to connect line items, sources, uses, and totals. When an applicant types over a formula with a hard number, copies a value without checking its source, or changes one section without updating another, the budget stops explaining how the project works.

A reviewer does not need to see a complicated spreadsheet. The reviewer does need to see a budget that can be followed. The total project cost should reconcile with the activity description. The requested CDBG amount should match the funding narrative. Local funds, other grants, owner contributions, or program income should be identified consistently. Administrative, engineering, acquisition, construction, relocation, and other costs should not appear in one part of the application and disappear in another.

Before submission, the finance and program teams should test the budget through several basic questions:

1. Does every major activity in the narrative have a corresponding budget line?

2. Does every significant budget line appear in the scope or work plan?

3. Do the sources equal the uses without unexplained rounding?

4. Are quantities, units, and per-unit assumptions visible enough to be checked?

5. Have formulas been preserved in the current state template?

6. Are contingencies and professional services treated consistently with program rules?

7. Does the schedule give the county enough time to procure and complete the work?

The point is not to make the spreadsheet look sophisticated. It is to prevent a reviewer, auditor, or county administrator from asking six months later how a number was produced.

Prevailing wage belongs in the estimate

Prevailing wage is the second major budget trap. Public facilities and improvement projects that fall within Davis-Bacon coverage generally require the applicable federal wage requirements to be reflected in the project’s labor assumptions. The issue is not limited to the final contract. If the application uses ordinary residential labor rates for work that will later be subject to federal wage requirements, the estimate may be understated before procurement even begins.

Not every rehabilitation activity or smaller scope is treated identically. Coverage depends on the project, the contract, the funding, and the applicable statutory and program rules. That is precisely why an applicant should not decide coverage by intuition. “It is only a small repair” is not a wage determination. “The contractor usually pays this rate” is not a compliance analysis.

The estimate should identify the labor assumptions used, confirm whether Davis-Bacon or another prevailing-wage requirement applies, and preserve room for related compliance costs. Depending on the project, those costs may include wage determinations, labor standards administration, certified payroll review, worker interviews, contractor reporting, and staff time. A bid that appears inexpensive because it excludes those obligations is not necessarily a good bid; it may simply be incomplete.

A budget that ignores applicable Davis-Bacon requirements does not save money. It moves the cost problem to the point where the county has fewer options.

For Somerset County’s FY2026 housing rehabilitation program, the $350,000 allocation was anticipated to cover roughly 20 properties, or approximately $17,500 per property before administrative overhead. That average is useful as a planning reference, but it is not a safe per-household promise. Actual costs can vary with the condition of each property, the required repairs, lead-paint abatement, material prices, accessibility work, contractor overhead, and the way administrative expenses are allocated.

A sound housing rehabilitation budget should distinguish between the average program allocation and the actual cost of a particular unit. If several properties require unusually extensive work, the county may need a ranking system, a maximum assistance policy, a contingency approach, or a process for revising the work scope. The application should explain that logic rather than presenting a clean average that conceals uneven property conditions.

Watch for ineligible activities and hidden obligations

A budget can also fail because it includes costs that do not belong in the proposed CDBG activity. Political activities, religious purposes, or work that does not advance an applicable Maryland CDBG national objective cannot be made eligible simply by placing the expense under a different heading. The project description, budget, and national-objective argument must describe the same eligible purpose.

Hidden obligations create a similar problem. A public facility project may require design work, permits, environmental mitigation, relocation assistance, accessibility improvements, or long-term operating commitments. A housing program may need inspections, income certifications, contractor oversight, and closeout documentation. Leaving those items out does not eliminate them. It leaves the county to absorb them later or forces a reduction in the promised scope.

Adhering to State Procurement Mandates Over Local Policies

A local procurement policy may be perfectly workable for ordinary county spending and still be insufficient for a CDBG-funded contract. CDBG awards carry federal requirements through the state program, and the Maryland CDBG Financial and Procurement Manual governs the procurement and recordkeeping process for those funds.

The governing question is not, “How does Somerset County usually buy this service?” It is, “Which procurement method and documentation does the CDBG program require for this purchase?” That question should be answered before the county advertises, solicits quotes, selects a vendor, or allows work to begin.

Full and open competition is central. A local preference for a familiar contractor, an informal practice of collecting a few quotes, or a purchasing threshold copied from the county ordinance may not satisfy the CDBG standard. Geographic preferences can be especially problematic. The desire to keep public dollars in the local economy is understandable, but it cannot override the applicable competition requirements.

The procurement file should show the decision, not merely the result. Depending on the purchase and procurement method, that record may include:

• The scope of work and specifications provided to prospective bidders
• The method used to solicit competition
• Public advertisements or written solicitations
• A list of firms contacted or responding
• Questions, addenda, and communications issued during the process
• Bids or proposals received by the deadline
• The evaluation or price analysis supporting the selection
• Conflict-of-interest and debarment-related certifications
• MBE and other required reporting
• The executed contract, insurance, bonds, and applicable labor standards
• A written explanation for any rejection, negotiation, or noncompetitive action

The exact record depends on the procurement, but the principle is consistent: an auditor should be able to understand what happened without relying on the memory of a county employee who may no longer be in the position.

This is where the phrase “the county has always done it this way” becomes dangerous. CDBG money is not simply local money with an additional funding source attached. It is federal pass-through funding administered through a state program. The state manual, the award conditions, and the applicable federal requirements control the grant-funded transaction.

Procurement planning should also account for the project schedule. A county that waits for the award before defining its specifications may lose months preparing a solicitation. A county that advertises before the environmental or site-control work is sufficiently advanced may create a contract it cannot responsibly authorize. A county that chooses the lowest apparent price without confirming labor standards, insurance, capacity, and scope may inherit a dispute that consumes the savings.

The best procurement file is built as the project is built. It is not reconstructed during closeout.

Meeting National Objectives: Proving Low- and Moderate-Income Benefit

A CDBG application must establish a national objective. For many Somerset County proposals, that means demonstrating a benefit to low- and moderate-income persons. The argument cannot rest on a general statement that the county is rural, that housing costs are rising, or that the facility is used by the public. The application must connect the proposed activity to an eligible beneficiary population or service area and support that connection with current documentation.

Two thresholds in the draft program framework require particular care:

• A 51% minimum LMI benefit may apply when a project is qualified under the LMI national objective on a per-project basis.
• A 70% cumulative LMI benefit is measured across the grantee’s overall CDBG program over a three-year period.

These standards operate differently. The 51% figure concerns the project’s own eligibility and beneficiary calculation. The 70% figure concerns the broader program portfolio over time. A single project should not be described as failing threshold review merely because the grantee’s cumulative three-year percentage is not yet at the program target. But the cumulative standard still matters: a pattern of awards that does not produce the required overall benefit can affect the grantee’s program standing and future competitiveness.

That distinction should appear in the application’s internal review. Program staff should know which calculation proves this project’s national objective and which records are needed for the county’s broader program reporting. Treating the two percentages as interchangeable creates confusion and can lead to the wrong evidence being submitted.

Build the LMI case around the actual service area

Income surveys must be current, properly administered on the prescribed form, and broad enough to describe the service area or beneficiary population identified in the application. A survey that covers only the most accessible households may not support a claim about the entire neighborhood. A survey from an earlier project may not describe the current population. A table of countywide income data may be too general if the project serves a defined area with different conditions.

Census tract data can support an area-benefit argument when the tract qualifies under the current LMI map and the project’s service area corresponds to the tract boundaries or otherwise meets the applicable methodology. A tract label placed in the narrative is not enough. The applicant should show how the facility, infrastructure, housing units, or service area relates to the qualifying geography.

The strongest applications make the geography visible:

• Identify the exact streets, parcels, blocks, or service boundaries involved.
• Explain who uses the facility or receives the improvement.
• Match maps, census information, survey results, and the narrative.
• Use current data rather than assuming that an old qualification remains unchanged.
• Explain any boundary that does not follow a census tract or standard neighborhood line.
• Preserve the underlying survey and calculation records for monitoring.

If the project serves a mixed-income area, the applicant should not hide the complexity. It should explain the method used to identify eligible beneficiaries and show why the method is reliable. A clear limitation is more credible than an inflated percentage built on assumptions a reviewer cannot reproduce.

Housing rehabilitation requires household-level discipline

For housing rehabilitation, the occupying household’s income certification is usually central to the benefit calculation. The county needs a process for verifying eligibility, documenting household composition and income, and addressing changes that occur between application, award, work authorization, and completion.

That does not mean every change automatically disqualifies a household. It does mean the program should establish when recertification is required, what documents will be accepted, who will review them, and how the decision will be recorded. A homeowner whose circumstances changed after the initial survey should not be handled through an improvised email exchange. The file should show the applicable rule and the basis for the final determination.

The same principle applies to waiting lists. A waiting list can demonstrate demand and help explain why the project matters, but it is not automatically proof that every person listed is LMI-eligible. The county should distinguish between evidence of need, evidence of eligibility, and evidence that the proposed activity will benefit the eligible population.

Need is more than a data table

Community or financial need documentation is another place where otherwise solid applications become thin. Reviewers need to understand why this project, in this service area, at this time. Raw figures can establish conditions, but they do not explain the proposed response.

A persuasive need section connects the evidence:

• Current census information describes the income and housing context.
• Local housing-condition surveys show the physical problem.
• Waiting lists or service records demonstrate demand.
• Public works or facility records explain the operational consequence.
• The project scope shows how CDBG funds address the documented need.
• The budget demonstrates that the requested amount is proportionate to the problem.

The narrative should also acknowledge what the grant will not do. If $350,000 can address roughly 20 housing units only when repairs remain within a defined scope, the application should say so. If a drainage project improves a specific area but does not resolve every countywide flooding concern, that boundary makes the proposal more credible. Reviewers are not looking for promises without limits; they are looking for a project the applicant can complete and defend.

The Application Is a Project Document

The recurring errors in Maryland CDBG applications are connected. A stale environmental assessment often points to weak project scheduling. A broken budget formula may conceal an incomplete scope. A procurement shortcut can undermine an otherwise eligible project. An unsupported LMI percentage can make a well-designed improvement impossible to fund. The application is not a series of independent forms. It is the first version of the project file.

For Somerset County and other rural jurisdictions, that perspective matters because administrative capacity is limited. The answer is not to imitate a large city’s staffing model. It is to assign ownership clearly and create a short, disciplined review period before submission:

1. Program staff confirm the eligible activity, national objective, service area, and beneficiary documentation.

2. Public works or housing staff confirm the scope, site control, environmental status, and construction schedule.

3. Finance staff test the sources and uses, formulas, labor assumptions, and required match or local contribution.

4. Procurement staff or counsel confirm the applicable state and federal purchasing requirements.

5. An independent reader opens the final file, follows the narrative from beginning to end, and records any inconsistency.

6. The authorized official reviews the final package, not an earlier working draft.

That sequence is not a guarantee of funding. It does something more useful: it reduces the number of reasons a competitive application can lose before its merits are fully considered.

The SFY27 deadline has passed, but the underlying lessons remain relevant for the next Maryland CDBG cycle. Current forms will replace old forms. New dates will replace July 6. The program’s review will still depend on whether the applicant can document control of the site, present a credible budget, follow the applicable procurement rules, and prove the project’s national objective.

Somerset County does not need a perfect application in the abstract. It needs an application whose claims can be traced to documents, whose costs can be explained, and whose promises fit the county’s ability to deliver. That is the standard that saves projects from preventable errors: every property identified, every environmental document current, every formula intact, every procurement step recorded, and every LMI claim supported by evidence rather than optimism.