Grant calendar

Start with active awards

Begin with money already awarded and obligations already accepted. Put new opportunities in a separate section so a possible application does not hide a required report. For each active award, collect the signed letter, agreement, reporting template and later notices. Read the current documents before copying last year’s dates. A small team can keep this in a spreadsheet; changing software will not supply missing terms. Grantkeeper can turn the files you provide into a draft register. The person who manages the award checks each row against the source. Keep the funder’s exact name and an internal award ID so two grants from one foundation do not merge.

Use one row per deliverable

One award can have several reports, payment requests and renewal decisions. Give each deliverable its own row. Record the award ID, deliverable name, period covered, due date, time zone, source page, owner and current status. Add a field for the last time someone checked the date. Use unknown when the agreement does not supply an answer. If the source says a report is due after a milestone, record that condition rather than inventing a calendar date. Ask the funder to clarify the trigger. Keep the answer with the award documents so the next person can understand why a deadline was added.

Work backward from the real deadline

Set an internal draft date and a finance review date before the external deadline. These are team choices, not funder requirements. Ask program staff how long they need to gather the evidence. A report due on Monday may need figures checked the previous week, especially if the finance volunteer works only on Thursdays. Keep internal targets visibly separate from the actual due date. In a fictional example, a November 30 report has attendance data due November 12, finance review November 19 and a director review November 24. These dates illustrate a plan; they are not a recommended schedule for every award.

Give each row one owner

The owner is the person who makes sure the deliverable moves, even when several people contribute. Record the program contact and finance reviewer separately if that helps. Do not assign a whole department and assume someone will notice. Agree a backup for absences. The weekly handoff should say what the owner needs next: a participant count, an expense export, a signature or a question answered by the funder. A vague status such as in progress hides work. A clear status such as waiting for September attendance from Maya tells a colleague what to do if the owner is away.

Choose a tracker and a calendar role

Use the tracker for the full record and the calendar for visible dates. Google Sheets and Airtable exports can supply Grantkeeper with a snapshot to organize. A private calendar feed can supply upcoming events, but the existing Grantkeeper calendar connection reads only and looks at a limited date range. It does not create the reminders for you. You add checked dates to the calendar yourself, or ask for dated tasks in the connected TickTick list. Confirm those tasks appeared where expected. Do not assume a file export keeps updating. Ask for a new review after the source records change.

Run a short weekly review

Look at the next thirty days together, then scan farther ahead for work that needs a long lead time. Ask three questions: what is due, what is missing and who will act next? Keep application go-or-no-go decisions separate from report completion. Grantkeeper can prepare this handoff from the current export and highlight conflicting dates. Someone still checks the agreement and any new funder email. If a date changes, update the tracker and the visible calendar or task together. Save the notice that supports the change. A reminder that still shows the old date creates a second problem rather than solving the first.

Close the loop after submission

Keep the final document, submission confirmation and any reply in the award folder. Record who submitted it and when. A prepared draft is not a submission, and a sent email is not proof that a portal accepted an upload. If a receipt is missing, leave the status as awaiting confirmation. Carry forward any follow-up question into the next weekly review. When the award ends, ask the award owner which records and dates still need attention. Grantkeeper can organize the handoff, but the funder’s terms and your organization’s own record policy determine what happens next. Keep uncertain obligations as questions for the responsible person.

Keep a source trail

Keep the original files beside the working draft. Give each file a clear date and keep later corrections as new versions. A sentence that contains a number should point to a record that another person can open. If a source is missing, keep the question visible rather than filling the space with a plausible answer. Remove private details that the reader does not need. A public update, a staff task list and a finance working paper can use the same checked fact, but they need different access. Test folder permissions with the person who will receive the finished work.

Leave a useful handoff

Finish with the next action, its owner and the date someone will check it. Save the reviewed version where the team already looks for this work. Tell the next person what changed and which questions remain open. Do not mark a task complete because a draft exists. Completion means the person responsible has confirmed the actual result, such as a checked document, a corrected record or a message that was sent. At the next review, start with unresolved items rather than rebuilding the whole process. This keeps a small team’s routine manageable when a volunteer is away or a staff role changes.

Related recipes: Award letter to reporting plan, Weekly grant handoff, Grant deadline register. Integrations: Google Sheets, Airtable, Google Calendar, TickTick.