To get a Fairfax County Proffer Matrix, use the County’s Proffer Matrix FAQ route for public copies of a submitted Matrix: email the Proffer Coordination Team at LDSProffers@FairfaxCounty.gov. Identify the rezoning or other action number if known, the project or plan name, the approximate submission period, and the condition or document you are trying to match. Ask for the dated Matrix version, not an informal assurance that every condition is complete. No request or response was made for this guide.
A submitted Matrix is a way to follow separate obligations through different stages. The Land Development Services (LDS) proffer page describes County tracking of proffers and related development conditions; it distinguishes monetary rezoning obligations from other condition types. A payment record may answer one monetary condition while leaving a construction, plan, or nonmonetary condition open. The page’s old anticipated module-launch language does not establish present public online coverage, a historical start date, or an all-conditions-complete flag.
Read one condition at a time
Start with the approved action or condition wording actually in your file, then compare it with the same numbered row in the submitted Matrix. The County’s blank example Matrix separates condition text, trigger, applicant response and evidence references from staff confirmation and reviewer fields. Its dated examples are examples, not findings about a real development.
For each condition, make a short ledger with four entries:
- Condition and trigger: copy the number and the event that makes the obligation relevant, such as a named plan, construction stage, or other milestone stated in that condition. Keep the exact approved wording beside the paraphrase you use for notes.
- Submitted account: record what the applicant says was done, the Matrix version and date, and any plan, sheet, receipt, deed-book/page, or supporting-document reference actually provided. An applicant narrative is a claim to check, not a County finding.
- Dated evidence: locate the cited document and verify that it concerns this condition, phase, and property. A receipt addresses a payment; it does not document installation of a separate improvement.
- County review: read the staff “Met” or reviewer entry separately from the applicant’s response. A blank, conditional, or disputed row calls for the missing evidence or clarification; it does not automatically mean the trigger has occurred or that the condition failed.
The County’s Matrix FAQ describes staff review of condition wording, triggers, plan treatment, timing, and responsible agencies. It also distinguishes applicant/internal sharing from a public copy request. Do not assume a working public Smartsheet view or infer a County conclusion from a screenshot that omits the version and reviewer column. For an interpretation of the obligation itself, the FAQ directs readers to the Department of Planning and Development’s Zoning Evaluation Division; that is a different question from obtaining an LDS-held submitted copy.
A fictional three-condition mismatch
Imagine a fictional file for “Cedar Landing.” Row A concerns a payment at a specified plan stage and includes a dated receipt. Row B concerns an access improvement after construction and cites a drawing, but its installation evidence is not in the folder. Row C calls for a later planting document, and the submitted Matrix says the trigger has not yet occurred. A cover note saying “proffers paid” may be accurate for A and still answer neither B nor C.
The next step is not to label the project fully compliant or noncompliant. Ask for the Matrix version tied to the relevant stage, the drawing and field record named for B, and the later submission or staff review for C if its trigger has occurred. If the County’s reviewer column differs from the applicant’s account, preserve both dates and request clarification for that exact row. This example is entirely invented; it does not interpret an actual Fairfax condition.
Request the missing record, then separate outcomes
Use the Proffer Coordination Team route above for the submitted Matrix. If a named underlying LDS file is unavailable online, the LDS public-records page gives a separate records-request route. Specify the condition number, action or plan ID, document type, and approximate date rather than asking the agency to certify a project’s entire legal status. Availability and retention vary by record class; no proffer-specific online era, copy delivery time, or survival guarantee was established here.
The Fairfax permit records guide helps locate a separate permit or older LDS file. A permit result, paid receipt, submitted Matrix, and County-reviewed condition are different evidence. The building permit records guide explains why a permit or inspection should not stand in for every other required document. This County route is not assumed to govern an independent city’s or town’s conditions.
Last checked October 6, 2026 (2026-10-06 UTC).