I.
Purpose & Scope
This document establishes a working framework for automating the annual Continuing Education (CE) credit review, approval, and communication process for holders of the Accredited Trust and Fiduciary Advisor (ATFA) certification — a program administered by Campbell University and the Trust Education Foundation, widely regarded as a gold standard designation for fiduciary professionals in the trust and wealth management industry.
The intent is to reduce manual burden on the ATFA Director, ensure consistent and defensible review decisions, and scale as the ATFA certificate holder base grows. A central component of this system is the ATFA Review Engine — a purpose-trained process system handling data intake, program research, preliminary recommendations, communications, and database management on behalf of the Director and CE Review Committee.
Note: This is a living document. Sections marked TBD represent open decisions to be resolved by the Director and/or Committee before full implementation.
II.
Governing Principles
These five statements govern how the CE review process operates and how automation is permitted to participate in it. They are written to be quoted directly — in a public FAQ, in the CE Review Committee charter, or in response to any question about how ATFA reaches its credit decisions. Where a specific procedure below and a principle here appear to conflict, the principle governs.
1
The Director recommends; the Committee decides.
Authority to approve or deny CE credit rests with the ATFA CE Review Committee and nowhere else. The Director compiles, annotates, and recommends. A recommendation is an input to the Committee's judgment, never a substitute for it, and the Committee may adopt, modify, or reject any recommendation without justification to the recommender. No recommendation takes effect until ratified under the procedure below.
Plain languageNobody approves their own recommendation. The person who prepares the file and the body that decides on it are deliberately kept separate, and nothing is final until the Committee has had it in front of them.
2
Automation assists; it does not adjudicate.
The ATFA Review Engine (BEN) classifies submissions, researches unknown programs, cleans data, and drafts recommendations. It does not issue approvals or denials, and no CE decision takes effect without human ratification. Where BEN matches a submission to a program the Committee has already tiered, applying that tier is execution of a decision the Committee has made, not a new one. Automation is measured on whether it makes human review faster and better informed — never on how many decisions it makes unattended.
Plain languageSoftware does the legwork. People make the call. No credit is ever granted or refused by a machine acting alone.
3
Every decision carries its evidence.
Each recommendation is accompanied by the sources it rests on, the date it was verified, and the reasoning applied. A decision that cannot be reconstructed later is not defensible, and defensibility is a requirement of the process rather than a courtesy. Records are retained so that any past decision can be re-examined against what was known at the time.
Plain languageIf we approved or denied something, we can show you why, what we looked at, and when we looked at it.
4
Unverified is not the same as unqualified.
A submission ATFA could not confirm and a submission that fails ATFA's standards are different outcomes with different remedies, and the denial reason codes preserve that distinction. Where the obstacle is missing evidence rather than insufficient merit, the certificate holder is told what is missing and invited to supply it.
Plain language“We couldn't confirm this” is not the same as “this doesn't count.” If it's the first one, we'll tell you what we need.
5
Rule once, apply consistently.
When a submission raises a question of policy rather than of fact, the Committee issues a standing ruling that governs the category, rather than resolving the individual item and leaving the question open. Rulings are recorded with the date and cycle in which they were made, and two holders presenting equivalent evidence receive equivalent outcomes.
Plain languageWe decide the general question once and then apply it the same way to everyone, instead of settling it case by case.
Decision & Ratification Procedure
How Principle 1 is operated. Adopted as the standing procedure for all CE review decisions — at standing meetings and between them alike.
1
Circulation
The Director publishes the Compiled Report to the full Committee, with the Review Engine’s evidence attached to every item. The circulation date and the membership circulated to are recorded. A Committee member must be able to dissent by reading the evidence panel — not by repeating the research.
2
Objection window — negative consent
Committee members have five business days from circulation to record an objection. No objection recorded within the window ratifies the batch. This is the default for standing review meetings and ad hoc decisions alike: the burden sits with the member to engage, and an unresponsive member does not stall the organization.
3
Standing meetings
Held at least quarterly, with additional meetings as volume or a forcing issue requires. Frequency may be reduced if quarterly review proves unnecessary. The meeting confirms the ratified batch and takes up any objected items.
4
Ad hoc decisions
Time-sensitive items may be circulated between standing meetings by email under the same negative consent rule and the same five-day window. Ad hoc ratifications are reported at the next standing meeting and entered in the same record.
5
Objected items
A recorded objection pulls the item from the batch. It does not fail — it carries to the next standing meeting for discussion and decision. The remainder of the batch ratifies normally.
6
Delegated execution
Where a submission matches a program the Committee has already tiered, the Director applies that tier without fresh ratification and reports it to the Committee in aggregate. New tier assignments, new standing policies, and any submission not covered by existing policy require Committee ratification. As the Known Programs database grows, the proportion requiring ratification falls — by design.
7
Record
Every ratification records the method, the circulation date, the objection deadline, the membership circulated to, and any objection raised. Silence counts as assent only where the opportunity to object was real and documented — these fields are that documentation, and without them “no one objected” is an assertion rather than a record.
Adopted: Draft — pending formal adoption by the CE Review Committee alongside the charter documents described in Section VII, item 3. Once adopted, this section becomes the public-facing statement of ATFA CE review governance.
III.
CE Review Pipeline — 5-Step Process
1
Submission Certificate Holder
ATFA certificate holders submit CE credits via CE App (myceapp.com) or designated intake channel. Submission captures: program name, session/course title, provider, date, hours claimed, and any supporting documentation.
2
Review Engine Preliminary Analysis BEN Review
The ATFA Review Engine ingests all submissions, classifies each program/session against the Known Industry Programs database, researches unknowns via web and social media, cleans data, and generates a color-coded recommendation report for Director review. This is the primary automation target.
3
Director Compiled Report ATFA Director
The ATFA Director reviews the Review Engine's recommendation output, may override or annotate, then finalizes the compiled report for Committee review. Tier 1 Auto-Approved items (TAI, TAF) may bypass Committee review and be ratified in bulk.
4
CE Review Committee Formal Approval ATFA Committee
The report is circulated to the full Committee for asynchronous review, opening a five-business-day objection window. Under negative consent, no objection recorded within the window ratifies the batch. Objected items are pulled and carried to the next standing meeting. Standing meetings are held at least quarterly; time-sensitive items may be ratified ad hoc under the same rule. Submissions matching an already-tiered program are executed administratively and reported in aggregate. See Section II, Decision & Ratification Procedure.
5
Review Engine — Database Update & Communications BEN Action
The Review Engine receives final Committee decisions, updates the CE database (platform TBD), and triggers outbound communications: approval/denial notices to holders, updates to internal logs, and flags for follow-up. Any newly-approved Unknown program is automatically promoted to the Known Programs database, reducing future Unknown volume with each cycle.
IV.
Program Classification Framework
The Review Engine maintains a living database of known industry programs, classified into four tiers. Classification determines the review path and agent behavior for each submission.
Tier 1 — Auto-Approved
ATFA-affiliated internal programs. Review Engine recommends approval automatically; no Committee action required beyond bulk ratification.
Examples: Trust Advisors Forum (TAF), Trust Advisors Institute (TAI)
Tier 2 — Reputable
Nationally recognized industry organizations. Review Engine matches session data against known program metadata and recommends approval when verified.
Examples: ABA, Cannon Financial Institute, FIRMA
Tier 3 — Known
Programs previously approved by ATFA in prior cycles. Review Engine matches against historical records and recommends approval. Database grows automatically each cycle.
Compiled from prior-year approvals; auto-updated after each cycle
Tier 4 — Unknown
Not in any existing database. Review Engine conducts internet + social media research to surface metadata. Upon approval, automatically promoted to Tier 3.
All new or unrecognized programs; volume decreases with each cycle
🔄 Self-Improving Feedback Loop
Every program approved from Tier 4 (Unknown) is automatically added to the Tier 3 (Known) database at the close of each review cycle. This compounding effect reduces Unknown submissions year-over-year, making each subsequent cycle faster and more automated than the last.
V.
ATFA Review Engine — Core Responsibilities
Review Engine — Functional Scope
- Data Access & Intake — Read/write access to CE platform or cloud spreadsheet; ingest new submissions on a rolling or triggered basis.
- Known Program Database — Maintain and update the tiered classification database; R&D session metadata (title, speaker, length, description, date, location) from known industry programs.
- Submission Matching & Cleanup — Compare holder submissions against known program data; flag typos, inconsistencies, and formatting errors with color-coded highlight recommendations in spreadsheet output.
- Approval Recommendations — Auto-approve Tier 1; recommend approval for verified Tier 2 & 3 matches; flag Tier 4 for research. Generate recommendation report for Director.
- Unknown Program Research — Conduct targeted web + social media sweeps (LinkedIn, YouTube, Facebook, program websites) to surface event details for unrecognized submissions. Goal: reduce Unknown volume over time by continuously expanding the Known database.
- Feedback Loop — Auto-Promotion — After each cycle, automatically promote all newly-approved Tier 4 programs into the Tier 3 Known database for future cycles.
- Database Updates — After Committee approval, update CE records with final statuses and log all decisions with rationale.
- External Communications — Submission status notifications, conditional approval requests, denial notices with standard reason codes, and end-of-year CE hour reminders to certificate holders.
- Internal Communications — Push notifications to Director on new submissions; outbound summaries to Committee; compiled reports and logs on demand.
- Conversational Query Interface — Allow Director (and eventually certificate holders via auth wall) to ask natural-language questions about CE records, statuses, program eligibility, and holder standing.
VI.
CE Submission Status Definitions
| Status | Definition | Next Action |
|---|---|---|
| Submitted | CE credit submitted by ATFA certificate holder; awaiting Review Engine processing. | Agent intake & classification |
| Under Review | Review Engine has processed; Director or Committee review in progress. | Director/Committee action |
| Pending Information | Submission flagged for missing or unclear data; holder contacted to provide additional detail. | Holder response required |
| Conditionally Approved | Recommended for approval pending minor correction or documentation from holder. | Holder correction / re-submit |
| Awaiting Approval | Director has reviewed and recommended; formal Committee approval pending. | Committee formal vote |
| Approved | Formally accepted by ATFA (Director + Committee). Credits counted toward annual requirement. | Review Engine updates database; confirmation sent to holder |
| Denied | Not eligible for CE credit. Standard denial reason code issued to certificate holder. | Review Engine sends denial notice with reason code |
Standard Denial Reason Codes (draft): (1) Does not meet ATFA program standards · (2) Duplicate submission · (3) Insufficient documentation · (4) Program/session not verifiable · (5) Outside eligible date range · (6) Erroneous or fraudulent submission
VII.
Open Questions & TBDs
⚠ Items Requiring Decision
1.
Platform / Infrastructure: CE App (myceapp.com) presents significant limitations — manual per-record approval, no known bulk import, and poor admin auth UX (requiring "login as user" for each individual record change). Recommend assessing CE App API/export capabilities with their support team before committing to deeper integration. Google Sheets or a lightweight custom app may be a more pragmatic primary system, with CE App potentially retained for holder-facing submission only.
2.
Review Engine Name: Working placeholder: "BEN." Three shortlisted candidates under consideration — final selection pending:
- 1.Batch Evaluation Navigator — clean, functional; Navigator implies guided intelligence
- 2.Bureau of Evaluation & Notation — institutional feel, as if naming a real internal department; "notation" nods to record-keeping
- 3.Benchmark Evaluation Navigator — "benchmark" carries natural resonance in a certification/accreditation context
3.
Formal Governance Docs: Formalize charter/scope documents for: (a) the ATFA Review Engine, (b) the ATFA CE Review Committee, and (c) the CE Submission Terms & Definitions glossary.
4.
CE App API Assessment: Pending response from CE App support team re: API access and bulk import/export capabilities.
5.
Holder-Facing Query Access: Long-term consideration — should ATFA certificate holders be able to query the Review Engine directly (via authenticated portal) to check their own CE standing and submission status?
VIII.
Recommended Next Steps
1
Phase 1 — Foundation: Resolve platform TBD (CE App API inquiry pending); compile existing Known Programs database from prior-year approval records; draft CE Submission Status glossary.
2
Phase 2 — BEN Engine Configuration: Build and configure the ATFA Review Engine with classification logic, program database, and recommendation engine. Pilot on a small batch of historical submissions.
3
Phase 3 — Communications Automation: Wire Review Engine to outbound email/notification workflows for holder status updates and Director/Committee push notifications.
4
Phase 4 — Full Pipeline: Run complete end-to-end CE cycle with Review Engine active at Steps 2 & 5; Director validates quality of recommendations; refine classification logic based on real-cycle feedback. Confirm feedback loop is auto-promoting Tier 4 → Tier 3.
5
Phase 5 — Conversational Interface: Enable Director-facing query interface; evaluate certificate holder-facing authenticated access behind login.