update template and COTR wording

Author: eteq

finance/proposal-calls/cycle4/cycle4.md

@@ -3,11 +3,12 @@
 
 # Changes relative to the previous cycle
 
+The primary changes for this Cycle relative to Cycle 3 are a single funding source (NASA), and the addition of the COTR role (see below).
+
 TBD ...
 * COTR wording needs proofreading
 * Dates need updating
 * Budget amount
-* Template needs updating
 
 
 # Funding goals
@@ -77,7 +78,7 @@ Once a proposal is accepted, the finance committee will assign a committee membe
 The following general steps follow whan an FR is selected:
 
 1. The FR is assigned a final budget and funding source, and the PR is merged.
-2. A new tracking issue is created for the FR (by the finance committee member contact), which includes identifying the COTR.
+2. A new tracking issue is created for the FR (by the finance committee member contact), which includes the budget, PoP, and identifies the assigned COTR.
 3. Work updates are given in the tracking issue, although out-of-band clarifications/conversations with the finance committee contact or COTR are welcome. It is the responsibility of the COTR to ensure these updates happen (although they don't necessarily need to be done by the COTR themselves).
 4. As work is completed, the funded personnel or their institutional representative submit invoices via OpenCollective (exact details of this will be clarified for each issue as details vary from person-to-institution).
 5. The issue is closed when the FR's work is completed, the budget is exhausted, or the period of performance expires.

finance/proposal-calls/cycle4/template.md

@@ -0,0 +1,27 @@
+### Title
+
+### Project Team
+Describe who is expected to work on the project. If work will be undertaken by an open hire instead of (or in addition to) other project members, please indicate that here.
+
+### Project Description
+How does this benefit Astropy packages / users / community / ...? Short summary.
+
+### Project / Work
+Details here as needed for Astropy community members to understand what is planned.
+
+### Approximate Budget
+Currency: US $
+The approximate budget should be specified in USD. However, we are open to spending funds worldwide. Budgets should be converted to USD using a plausible exchange rate.
+
+Include overheads, fringe, etc. if money is paid as sub-grant (note that the Moore grant caps overhead at 15%).
+
+- Travel:
+- Conference Registrations:
+- Salary / contractor fees etc. (give sum here, details about contract, payment method (contract/sub-award) etc. can be worked out with the finance committee later)
+- TOTAL
+
+Please note that we would happily accept budget items other than travel, conference registration, and staff.
+
+### Period of Performance
+
+List the expected range of time the budget should be allocated for.  Note that if this is longer than one year, funds beyond that horizon are contingent on funds from the project being available (feel free to ask the finance committee if you have any concerns about this).