CRA Community Development Activity Log

This template is for recording community development loans, qualified investments, and qualified services that may support CRA consideration. It captures the activity type, qualification basis, geography, beneficiary profile, and supporting documentation in one place. Use it as a working log for internal review, not as a substitute for your bank's CRA program files or final exam documentation.

It is typically completed by CRA officers, community development staff, lending teams, investment teams, or employees who volunteer qualified services. The submitter should be the person closest to the activity and able to describe why it qualifies. A reviewer can then validate the entry before it is added to the official audit trail.

Update it as soon as the activity occurs or when the commitment is approved, rather than waiting for month-end or exam prep. That timing reduces missing details such as dates, amounts, and supporting documents. For recurring service activities, log each distinct event or use a controlled series of entries if your policy allows it.

A qualified service entry should describe a service performed for a community development purpose, such as board service, financial education, or technical assistance. Loans and investments should be logged separately with transaction details, commitment amount, and term. If the activity does not clearly connect to a CRA-eligible purpose, document the rationale before classifying it as qualified.

Common issues include vague qualification language, missing beneficiary or geography details, and weak documentation notes. Another frequent problem is entering a transaction without explaining the community development purpose or related CRA area. This template helps prevent those gaps by prompting for the basis of qualification and the evidence behind it.

Yes. You can add conditional logic for activity type, required document types, internal approval status, or reviewer comments. Many teams also add fields for branch, product line, or exam period so the log aligns with internal reporting and downstream CRA files.

It creates a consistent record of who submitted the activity, what happened, when it happened, why it qualifies, and where the evidence lives. That structure makes it easier to trace each entry back to source documents during internal review or an exam. It also reduces reliance on email threads and informal notes that are hard to verify later.

An ad hoc tracker often misses key fields, uses inconsistent labels, and makes review and search difficult. This template standardizes the submission so every entry includes the same core information and supporting evidence. That consistency improves usability, reduces rework, and makes it easier to aggregate activity across teams.