Find the exact commitment
Start with the final approval, development agreement or adopted conditions. Distinguish a general statement of intent from a specific obligation. Record the required action, responsible party, location, triggering event and deadline only where the document actually provides them.
A benefit mentioned in a presentation may be revised or absent from the adopted terms. Keep the source version and date with the claim. When the relevant final document has not been reviewed, describe the statement as proposed rather than treating it as an enforceable completed commitment.
Sources: Wilmette: development approval materials, October 22, 2024
Match each condition to its own evidence
Build one row per commitment. Link its source and add a separate column for implementation evidence: a payment record, accepted work, recorded easement, issued permit or other relevant document. A later project milestone is not automatically evidence that every condition was satisfied.
The Optima finding shows why offsite public benefits can require records beyond the condominium site itself. The responsible agency, project geography and timing may differ across commitments. Link the evidence explicitly rather than assuming all work belongs to one completed phase.
Use an honest unresolved status
When delivery cannot be verified in the reviewed collection, use ‘completion not verified in these sources.’ That is different from saying a developer failed to comply or that no completion record exists. Name the next document needed and the agency likely to hold it.
A later update should say which row changed, which new source supports the change and whether it confirms full or partial delivery. This creates a durable public timeline that can be cited and corrected without turning missing evidence into an accusation.