The AI-GRS designation recognizes specialists in general review and reporting, so prepare it as a second, distinct skill layered on top of your valuation knowledge rather than as another valuation course. The habit to build from week one: when you read a sample appraisal, stop asking 'what would I value this property at?' and start asking 'does the reasoning here support the conclusion the appraiser reached?' That single reorientation drives every scenario below, from scope decisions to ethics questions.
Why review work is a different skill from appraising the same property
AI-GRS preparation means learning to critique another appraiser's development and reporting under USPAP, using valuation knowledge as raw material rather than as the deliverable itself.
The Appraisal Institute positions designation education as building on a career of valuation work, and its review credential targets professionals who evaluate general, non-residential assignments. Treat your existing skills in income capitalization, sales comparison, and cost analysis as the toolkit, not the exam. Your new task is diagnosing whether an appraiser applied that toolkit competently, disclosed limits honestly, and reconciled evidence to a supported conclusion.
Completeness, credibility, correctness: three tests candidates blur together
A reviewer judges whether the work is complete and whether its conclusions are credible; whether the reviewer personally agrees is a separate, optional judgment that must never silently substitute for the first two.
Completeness asks whether the appraiser addressed the elements required for the assignment type and the scope stated: intended use and users, property rights, effective date, and the approaches actually used. Credibility asks whether the methods and data support the conclusion reached. Correctness, in the reviewer's sense, asks whether the reviewer's own analysis would land at the same number, and a professional review can report a different opinion only when the assignment calls for it and the reviewer does the supporting work.
Deciding the scope of your review before opening the file
Review assignments vary in depth: a desk review without inspection differs fundamentally from a field review, and a critique-only review differs from one that includes your own value opinion.
USPAP's review standards for development and reporting require the reviewer to define scope for the review itself, and reviewers who skip this step produce conclusions their own work cannot support. A desk review based on the report's contents can support findings about internal consistency and documentation. Verifying comparable sales, inspecting the subject, or checking market conditions requires additional work that must be disclosed as part of the review's scope. Study each sample assignment by asking first: what work level does this engagement describe, and does the reviewer's stated scope match what the findings actually require?
Worked scenario 1: the desk review with an unsupported rent conclusion
A reviewer spots weak support behind a market rent conclusion and must choose between rewriting the analysis and documenting the specific defect.
Scenario: you review a self-contained narrative appraisal of a 40,000-square-foot suburban office building. The appraiser concluded market rent of $24.00 per square foot in the income approach, but the report presents only one lease abstract, describes 'current market conditions' without citing sources, and contains no rent comparison grid. A plausible mistake is to pull your own rent data, run a new comparison analysis, and state that market rent should be $21.50, effectively re-appraising the property inside a review report. That decision matters because it changes your assignment from review to a second appraisal, triggering development and reporting obligations you may not have agreed to or priced, and it buries the actual finding.
- The better decision: record a credibility finding - the market rent conclusion is not supported by data disclosed in the report, so its credibility cannot be assessed from the review file.
- State what would resolve the defect: disclosure of the rent comparables, their sources, and the reasoning applied, or an expanded scope in which the reviewer verifies market rent.
- Note the downstream effect: the income approach conclusion inherits the weakness, so findings should trace from the rent conclusion through capitalization to the value opinion rather than stopping at the first gap.
- Check your own report afterward: does every finding describe the work done at this review level, and would the original appraiser understand exactly what to fix and why?
Worked scenario 2: the client who wants the review conclusion softened
When a client pressures a reviewer to change findings, the professional response is to hold the analysis and, if needed, decline or withdraw, not to shade conclusions.
Scenario: your desk review finds that a narrative appraisal reconciled three approach indications toward a sale figure that the report's own market analysis contradicts, and your credibility finding says the reconciliation is not supported. The client, who needs the file for a lending decision, asks you to revise the finding to 'minor formatting issues' so the loan can close. The plausible mistake is editing the finding's language to soften it while keeping your analysis unchanged, reasoning that the substance survived. This matters because a review report's value lies in the correspondence between analysis and stated conclusions; a softened conclusion that no longer matches the analysis compromises the review, and independence questions of exactly this kind are what appraisal ethics standards and complaint processes examine.
Desk review versus field review versus review with an own-value opinion
Each review configuration supports different findings; matching the configuration to the client's intended use is the core planning decision.
Use this table to organize your study of review types and to test yourself on any sample assignment: identify the configuration, then predict which findings the reviewer could and could not legitimately deliver. Where your prediction and the table disagree, investigate the gap, since that gap is usually an undisclosed scope assumption.
| Configuration | What the reviewer does | Findings this can support | Findings it cannot support |
|---|---|---|---|
| Desk review, critique only | Analyzes the report's contents against its stated scope and review standards | Completeness, internal consistency, disclosure adequacy, credibility of reasoning as documented | Accuracy of data not verified, property condition, conclusions about market facts outside the report |
| Field review | Adds inspection or external verification within disclosed scope | Everything above plus data accuracy checks and condition observations within the disclosed work | An independent value opinion, unless the reviewer performs the development work of an appraisal |
| Review with own value opinion | Reviewer completes appraisal-level development and reports both findings and an opinion | Everything above plus a separate value conclusion under the reporting standard that applies | Conclusions from shortcuts, e.g., an own opinion built on unverified data copied from the reviewed report |
A two-week drill cycle and a self-check rubric for review judgment
Work in short cycles: read a sample report, draft review findings, then score them against a rubric that penalizes findings unsupported by your review scope.
Practical exercise: take any publicly available sample narrative appraisal or one of your old files, and in 45 minutes produce three artifacts - a one-sentence statement of the review scope you would propose, a list of up to five findings, and a note under each finding identifying the review-level work supporting it. Expected observations when you first try this: your findings will read like appraiser preferences ('would have used more comparables'), several will lack any scope support note, and you will have at least one finding that is actually a second-appraisal opinion in disguise. Those are the exact defects to eliminate in the next cycle.
- Rubric: a finding scores 2 only if it (a) states a specific defect or strength, (b) cites the part of the report it concerns, (c) names the review-level work supporting it, and (d) does not assert an unrequested own opinion. A milestone target in later cycles is an average near 2.0 across five findings; treat this as a learning benchmark, not a score prediction.
- Adaptable preparation sequence: days 1-3, re-read USPAP's review development and reporting standards against your own past files; days 4-7, run the drill on three sample reports with the rubric; week 2, add a scope-variation pass, redoing one report at desk-review level and then field-review level to see which findings change.
- Readiness checks: you can state the difference between completeness and credibility without notes; you can list which findings a critique-only desk review can support; you can draft an ethics response to client pressure in under five minutes; and every finding you write cites its supporting review work.
If the exam tests scenario judgment, your scenario habits are the preparation
Treat case-style questions as the same drill compressed: identify the review scope, the defect, and the permissible finding before looking at the answer options.
Exam-style scenarios reward the same sequence you practice in the exercise: first fix the assignment's configuration (desk or field, critique-only or with an own opinion), then classify each candidate finding as completeness, credibility, or correctness territory, then choose the answer that matches the scope and the disclosed work. Candidates who read scenarios as valuation problems, by instinctively re-solving for value, will generate attractive but scope-inconsistent answers; the discipline of the three-layer separation is what converts valuation knowledge into review answers.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.