The mission of the Art Grantsmanship Academy is operational, not ornamental; when planning, award, and reporting cycles are linked; when systems are documented; and when compliance is built in—not patched on at the ticket window. Writing the grant proposal is last. Readiness of the organization comes first. This course is four modules. The course provides a method: arrive with a program, leave with a grant strategy the reviewer can follow from platform to destination.

A policy is the rule that governs a work system so Tuesday does not depend on memory. It sits on a named system, has an owner, a review cycle, and a metric. It is not a hallway document and not a paragraph written for a RFP or a NOFO. This course uses the template : title, version, effective date, system served, owner, metrics, resources, revision log. Members complete one policy for one existing system. A library of unowned policies is not infrastructure.

A procedure is the set of steps staff follow so a policy is not a hallway document. It names who acts, when they act, what record they leave, and what happens when the step fails. A new hire should be able to use it on Tuesday without asking the founder. This session writes one procedure that sits on one policy, then puts the whole chain on a single page: system → policy → procedure → owner → metric. If any link is missing, the organization does not yet have infrastructure. It has a paragraph.

A work system that cannot be measured cannot be funded honestly. This session names the metric that tells if the system works, then places it in the budgetary cycle: plan, approve, spend, read variance, reallocate. A partial award is part of that cycle—what continues, what stops, who decides. Integration is one line of sight: a mission phrase or pillar → the system → the owner → the metric → a budget decision. If that line is broken, the organization has separate documents, not infrastructure.

Compliance belongs in the systems that already run the house—document retention, conflict of interest, gift acknowledgment, effort, procurement, HR—not in a folder assembled after the notice of award. This session names which systems carry those duties, then draws the line between an afterthought and a condition of fundability. If the practice exists only in a proposal paragraph, it does not exist. A reviewer can tell.

This capstone ties the academy together. Mission, vision, and pillars name the organization. Work systems, policies, and procedures make that purpose runnable. Operations, assessment, and budget must link. Compliance is ordinary practice, not a folder after award. Map one live opportunity across that whole chain. Two or more required systems absent: do not claim infrastructure. Build, partner, or reduce. Bring a redacted map to Setting the Table or Office Hours. Writing last.

Eight courses. One house. Introduction names the error: funders buy a table already set. Mission, vision, and pillars name the purpose. Work systems, policies, and procedures make it runnable. Operations, assessment, and budget must link. Compliance is ordinary practice. The capstone maps a live opportunity across that chain. Two systems absent: do not claim infrastructure. Managing and reporting an award come after owners exist. No award promised. Set the table. Then write.