Fiscal Sponsorship Project Intake and Agreement Form

This form is used to evaluate whether a project fits your fiscal sponsorship program and to document the basics needed for onboarding. It captures the project summary, leadership contacts, budget, funding sources, and the sponsorship model so reviewers can make an informed approval decision. It also creates a clear record of what the sponsor is agreeing to support.

A project should submit this form before any funds are received or spent through the fiscal sponsor. That timing helps the sponsor review mission alignment, confirm the correct sponsorship structure, and identify any restricted-funds handling needs early. It is also useful before public launch if the project will use the sponsor’s name or tax status.

The project lead usually completes the form, with input from the authorized signer and any finance or operations contact if needed. The fiscal sponsor contact may use it during review, but the project team should provide the core facts and supporting documents. If the project has multiple leaders, the form should identify who is responsible for day-to-day communication.

The form includes sponsorship model selection because the sponsor needs to know how much operational control it will retain and how the project will be administered. Model A and Model C imply different relationships, so the form asks for an operational control acknowledgment and project independence level to document that distinction. If your organization uses different terminology, you can rename those fields while keeping the same decision points.

Use it for every new project intake and again whenever a sponsored project changes scope, leadership, budget, or funding restrictions in a material way. It can also serve as a renewal or re-approval record if your program reviews projects on a recurring cycle. For active projects, a lighter update form may be easier than re-running the full intake.

Attach the documents your sponsor needs to evaluate the project, such as a project plan, budget, incorporation or registration notes, grant letters, or other support for restricted funds. The exact list should reflect your internal review process and any legal or finance requirements. Keep the upload list focused so the form does not collect unnecessary PII or duplicate records.

It creates an audit trail of the project’s scope, contacts, budget, and approval request, which helps the sponsor show how decisions were made. The consent and submission notice fields also support transparent collection of PII. If you handle public-facing project names or donor-restricted funds, the form helps document those choices in one place.

Yes. You can tailor the sponsorship model options, add conditional logic for restricted funds, or rename fields to match your internal policy language. Many sponsors also add approval routing, document requirements, or a field for legal review notes. The key is to preserve the core intake data needed to assess fit and document the agreement.