Bundle catalog

roles bundle

Financial Analyst (FP&A)

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Financial Analyst (FP&A) role.

Use this bundle to plan and review Financial Analyst (FP&A) work with evidence, assumptions, owners, and review points made explicit. The page previews a role guide, an overview, a workflow, and a template; the intended output is FP&A decision brief. Start source review with O*NET OnLine — Summary / 13 2051.00.

Project-reviewed beta

10 Markdown files · 1,495 words · no signup · CC-BY-4.0

Professional review status

No professional domain review recorded

This bundle covers financial subject matter. It is a source-aware research aid, not professional advice, and should not be the sole basis for consequential decisions.

Review before reliance: A qualified financial professional appropriate to the question, decision, organization, and jurisdiction.

Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Is this bundle right for your task?

Who it is for

  • People performing or supporting Financial Analyst (FP&A) work, plus teams reviewing its decisions and outputs
  • Teams working in Finance, Business planning

When to use it

  • A Financial Analyst (FP&A) task needs a structured plan, evidence checklist, or review-ready output.
  • A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.

What you need to provide

  • The task objective, intended audience, working context, constraints, source material, and decision owner.
  • Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.

Tasks and expected outputs

Questions it helps answer

  • Prepare a FP&A decision brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce a review-ready recommendation with explicit verification and approval boundaries.

What it helps produce

  • FP&A decision brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Financial Analyst (FP&A) work by producing FP&A decision brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 13 2051.00, then confirm that the reference is current and applicable. Inspect Financial Analyst (FP&A) Source-Aware Guide before drafting.

Context path: bundles/roles/financial-analyst-fp-a

What the bundle includes

Frameworks

  • source-evidence matrix
  • financial planning and analysis review matrix
  • qualified-review gate

Evaluations

  • Financial Analyst (FP&A) source-awareness check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

Limitations and safe use

Do not use this for

  • Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.

Known limitations

  • Use the cited official, originator, standards, or professional sources for general financial planning and analysis context; local facts, records, values, states, and permissions require inspected evidence.
  • Task-specific work requires current evidence for entity, business units, reporting period, decision, and accounting basis; actuals, ledger extracts, reconciliations, close status, and source dates; budget, forecast, drivers, assumptions, scenarios, and model versions; KPI and variance definitions, allocations, currencies, tax, and intercompany treatment; risks, sensitivities, approvals, narrative, and disclosure context.
  • Do not infer actual result, forecast, variance cause, driver relationship, liquidity, accounting treatment, or management approval.

Safety notes

  • Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
  • Require explicit confirmation before changing budgets or forecasts, posting entries, approving spend, distributing sensitive results, or making public financial claims.
  • Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.