ASFMRA AAC common mistakes
ASFMRA AAC · Understand the traps and how to avoid them.
Presenting a recommendation (e.g., 'lease the ground to a solar developer') before establishing the client's objectives, constraints, and decision criteria in the engagement scope.
Candidates come from production agriculture or appraisal backgrounds where the 'answer' is the deliverable, so they jump to conclusions and treat scoping as paperwork rather than the foundation of the consulting relationship.
What to do instead
Draft a one-page engagement summary first that states the client's decision, the options under consideration, constraints (capital, family goals, timelines), and the deliverable format; do not begin analysis until the client confirms it in writing.
Building a financial projection with a single point-estimate (one price, one yield, one interest rate) and no sensitivity or break-even analysis.
Spreadsheet habits and time pressure lead candidates to present the 'most likely' scenario as if it were the only scenario, which fails the consulting standard of informing a decision under uncertainty.
What to do instead
For every projection, include a base case plus at least a low/high sensitivity table on the two or three variables that most move the result, and report the break-even value for the key decision variable (e.g., the price at which the investment fails).
Confusing an appraisal assignment with a consulting assignment - delivering a value opinion when the client asked for a feasibility study, an operational review, or a strategic recommendation.
Many candidates are trained as appraisers and default to valuation methodology, standards, and report structure even when the question calls for analysis and advice rather than an opinion of value.
What to do instead
Before writing, classify the assignment: is the deliverable an opinion of value, a set of recommendations, or a feasibility conclusion? Use the corresponding standards and report structure, and state explicitly in the report what type of assignment it is and what it does not include.
Skipping or superficially documenting the discovery/data-gathering plan - no stated data sources, no verification of client-provided figures, no interview notes.
Candidates assume the client's numbers are correct and that more analysis is better than more verification, so the evidence base is thin and undocumented.
What to do instead
Include a data plan in the report: list each source, how it was verified (e.g., lender statements, FSA records, tax returns), and note any figure accepted on the client's representation. Flag unverified assumptions in a clearly labeled assumptions section.
Failing to reconcile the consulting analysis to the operation's actual financial statements and cash flow, producing recommendations the business cannot fund.
Candidates build models in isolation from working capital, debt service, and family living draws, so a technically profitable recommendation is operationally infeasible.
What to do instead
Before finalizing recommendations, test each against the operation's cash flow: show the funding requirement, timing, and source, and confirm debt-service coverage and working capital remain adequate under the base and low cases.
Delivering a report with no clear scope limitations, assumptions, or reliance statement, and no statement of the consultant's independence.
Candidates treat these sections as boilerplate and cut them under time pressure, not realizing they define the boundaries of professional responsibility and are graded as substantive content.
What to do instead
Use a standard report skeleton that includes scope, limitations, key assumptions, sources and reliance, and independence/disclosure language, and complete each section with assignment-specific content rather than generic text.
Accepting an engagement or a compensation arrangement where the consultant has a contingent interest in the outcome (e.g., a commission or success fee tied to a land sale or loan approval) without disclosure or withdrawal.
Candidates focus on the technical work and overlook conflicts of interest, or rationalize that a success fee 'aligns incentives' without recognizing it compromises objectivity.
What to do instead
Screen every engagement for conflicts at intake: identify any financial interest in the recommended outcome, disclose it in writing, and decline or restructure contingent compensation that would impair objectivity. Document the screen in the engagement file.
Using client confidential information - financials, family disputes, expansion plans - in a way that leaks beyond the engagement, such as sharing comparative data or discussing the client's situation in a professional or community setting.
Agricultural consulting is a small, interconnected community, and candidates underestimate how identifiable 'anonymized' details are and how quickly information travels.
What to do instead
Adopt a written confidentiality protocol: aggregate or disguise any data used for comparison, obtain written consent before contacting third parties about the client, and treat all client information as confidential unless release is authorized or legally required.
Submitting elective education that is not pre-approved by the committee or cannot be tied to consulting practice, then discovering the hours do not count.
Candidates accumulate continuing-education hours reactively and assume any agriculture-related course qualifies, without checking the approval list or the consulting relevance requirement.
What to do instead
Before registering for any elective, confirm it is on the committee-approved list or submit a pre-approval request with a written justification of how it applies to consulting practice; keep approval confirmations with the education log.
Submitting a work-product report that is technically sound but unprofessional as a document - missing executive summary, no table of contents, inconsistent figures, no client-ready formatting, or identifying details that breach confidentiality.
Candidates treat the work-product submission as a technical exercise and submit working drafts or internal versions rather than the polished client deliverable.
What to do instead
Submit the final client-issued version and review it against a report checklist: executive summary, clear recommendations, consistent and labeled tables, professional formatting, and redaction of confidential client identifiers where required.