Identify Issues In Tax Exemption Application

---
name: identify-issues-in-tax-exemption-application
task_id: tax/identify-issues-in-tax-exemption-application
description: Reviewing a nonprofit tax exemption application package requires identifying issues that may cause denial, delay, or a request for additional information; prioritizing those that should be corrected before filing; and providing concrete, procedural next steps rather than only noting potential problems.
activates_for: [planner, solver, checker]
---

# Skill: Identify Issues in Nonprofit Tax Exemption Application

## 1. Subject-matter triage

- Use this skill for issue-spotting in a draft exemption package, supporting governance materials, financial exhibits, and narrative statements.
- Treat the package as a filing-readiness review, not a merits opinion: the goal is to find what could trigger rejection, deferral, or follow-up.
- If the package covers multiple entities, periods, or project tracks, separate them before analysis and review each on its own terms.

## 2. Failure modes the skill is correcting

- Identifying governance concerns in general terms without tying them to the applicable exemption standard and the corrective step needed before filing.
- Missing structural deficiencies in formation documents that can prevent approval, especially where the entity’s governing documents do not include required exempt-purpose and asset-dedication language.
- Treating arithmetic or internal-consistency errors in the application as minor without checking whether they affect the agency’s review of the organization’s finances or operations.
- Failing to identify mismatches between stated obligations and projected revenues that may trigger follow-up questions about sustainability.
- Flagging issues without stating how serious they are, why they matter, and what must happen next.
- Collapsing distinct issues, documents, or periods into one generic concern instead of isolating each filing risk.

## 3. Legal frameworks / domain conventions that apply

- **Formation document requirements for exemption:** The governing documents should contain the provisions commonly required for exempt status, including appropriate purpose and asset-dedication language. If those provisions are missing or inconsistent with exemption requirements, flag the issue as a filing blocker and describe the amendment or restatement process needed before submission.
- **Private inurement and private benefit:** The organization should not allow net earnings or other assets to benefit private individuals or insiders beyond fair market value or otherwise permissible compensation. When compensation, expense reimbursement, related-party dealings, or other arrangements create a private-benefit concern, analyze the transaction structure, the approval process, and the evidence supporting fair value.
- **Board and insider compensation:** Compensation for services in a non-governance capacity may be permissible, but compensation tied to governance activity or lacking a clear market basis requires close review. Examine the role performed, the approval process, contemporaneous documentation, and comparability evidence.
- **Conflicts of interest controls:** Where insiders or board members have financial relationships with the organization, review whether the conflicts policy requires disclosure, recusal, and independent approval. A policy that exists only on paper should be tested against actual practice and supporting records.
- **Performance-based incentives:** Incentive arrangements should be reviewed for whether they create pressure to prioritize volume or revenue over mission alignment. Analyze whether the metric is consistent with the organization’s stated purpose and whether safeguards exist to prevent misuse.
- **Related-party transactions and market support:** If a vendor, contractor, lender, or other counterparty is related to an insider, review whether the transaction was negotiated at arm’s length and whether the organization has support for the price and terms, such as market comparisons, bids, or other independent evidence.
- **Financial projections and sustainability:** Review the application’s projected income, expenses, and obligations for internal consistency and realism. If the assumptions do not reconcile or appear understated or overstated without explanation, identify the specific mismatch and the additional support or revision needed.
- **Governance policies commonly requested in exemption applications:** Review whether the organization has adopted core governance policies commonly expected in exemption review, such as conflicts, whistleblower, and document retention policies, and whether the application accurately describes their status.
- **Controlling authority:** Tie each legal conclusion to the governing exemption rule or source the package invokes, and avoid unsupported conclusions that do not identify the standard being applied.

## 4. Analytical scaffolds

Use an issue-by-issue memorandum format.

At the outset, define a uniform severity scale:
- Critical: likely filing blocker or likely to trigger denial absent correction.
- High: likely to trigger a request for additional information or substantial delay.
- Medium: material issue that should be corrected before filing if practicable.
- Low: completeness or hygiene issue that should still be cleaned up.

For each issue, state:
- severity;
- the specific document or section where the issue appears;
- the governing rule, policy, or exemption principle implicated;
- the factual mismatch, omission, or inconsistency;
- the corrective step needed before filing or the follow-up needed after filing;
- the filing consequence if left unresolved.

Priority framework:
- **Critical / High:** formation defects, missing or contradictory exemption language, unresolved private-benefit risk, undisclosed related-party economics, or materially unsupported projections.
- **Medium:** incomplete policy adoption, weak documentation of approvals, ambiguous narratives, or inconsistencies that invite questions but may be curable with supplementation.
- **Low:** drafting cleanup, cross-reference fixes, labeling issues, and minor description mismatches that do not themselves threaten approval.

For application sections that admit multiple parties, projects, periods, or assumptions:
- identify each item separately before analyzing it;
- do not combine distinct relationships, transactions, or line items into one composite issue;
- if only one item is truly in scope, say so and explain why.

For financial review:
- compare the narrative, budget, projections, and schedules against one another;
- check whether revenue, expense, staffing, and cash assumptions are internally consistent;
- isolate any unsupported or contradictory line item and explain the specific consequence for review of feasibility, sustainability, or organizational purpose.

For governance and related-party review:
- test the policy text against the facts described in the package;
- distinguish a policy that exists from a policy that is actually implemented;
- note any missing approval trail, recusal, comparability support, or independent review.

For formation-document review:
- compare the stated purpose and dissolution language against the exemption standard;
- identify whether the language is missing, incomplete, or inconsistent across the charter, bylaws, and narrative;
- specify whether the remedy is amendment, restatement, board approval, member approval, or other formal action before filing.

For candor and completeness:
- treat omissions, half-statements, and internally inconsistent descriptions as filing risks even when no single provision is facially defective;
- where the source materials appear to rely on a contingency, state the contingency plainly and note how it should be disclosed.

## 5. Vertical / structural / temporal relationships

- Track how the governing documents, application narrative, financial exhibits, and policy suite fit together; a fix in one document may require conforming edits in the others.
- Treat pre-filing defects differently from post-filing follow-up items: if the issue affects eligibility, authorization, or disclosed operations, it should be escalated before submission.
- If the package describes future projects, approvals, or milestones, mark whether the representation is conditional, planned, or already secured, and flag any dependency that is not yet satisfied.
- When multiple documents speak to the same subject, identify the controlling version and call out contradictions across the record.

## 6. Output structure conventions

- Write a memorandum organized by severity tier, then by issue.
- Give each issue a short heading and a concise explanation.
- For each issue, include the controlling authority or governing principle by name, the specific correction needed, and the practical filing consequence.
- Close each issue with a concrete next step tied to filing timing.
- Include a dedicated financial-projection review section that isolates inconsistencies, unsupported assumptions, and reconciliation problems.
- End with a Recommended Actions block that lists imperative actions, the responsible role, and the timing relative to filing or the relevant regulatory milestone.
- Use plain language, but keep legal conclusions anchored to the governing standard rather than to intuition alone.