Board packets and 990 records

Start from the actual agenda

Ask the chair which decisions and updates belong in this meeting. Build the packet index from that agenda rather than collecting every document in the office. For each item, name the document owner, reporting period and expected attachment. A decision request needs a clear question and the material the board needs to consider it. An information item can be shorter. Grantkeeper can organize the supplied documents and draft a missing-file request, but it should not invent an agenda decision. Keep the index available to the chair and secretary so they can confirm that the packet matches the meeting they intend to run.

Confirm versions with their owners

A filename ending in final does not prove that a report was approved. Compare the date, period, title and visible version label inside each file. When two documents conflict, ask the owner which one belongs in the packet. Keep a short record of that answer. Finance checks financial reports before circulation, including the period and the basis used in the source report. Grantkeeper can flag a statement from the wrong month or a missing attachment, but it cannot establish that the ledger is complete. Keep the reviewed version separate from working copies so an old attachment is not reintroduced at the last moment.

Describe progress without inventing impact

Program updates should distinguish completed work, planned work and outcomes supported by evidence. A completed project task can show that a workshop was arranged; it does not prove that participants learned a skill. Ask the program lead for the actual measure and period behind each result. Grantkeeper can draft a short board update from a Trello or Asana export and link statements back to tasks. Missing evidence remains an open question. Keep delays and decisions needed visible rather than smoothing them into optimistic prose. A board can act on a clear gap; a polished paragraph that hides uncertainty makes review harder.

Protect sensitive meeting material

Share the packet with the people who need it and check the folder permissions before distribution. Personnel matters, private care information and donor details may need a narrower route than the general packet. Ask the chair how those records should be handled under the organization’s own process. Do not place sensitive material in a public task title or a broadly shared chat. Grantkeeper can work from the subset you authorize and prepare a smaller board version. A Dropbox or Drive link is not proof of restricted access; test it with the intended recipient. Keep the packet index useful without exposing details that do not belong there.

Turn accepted minutes into clear actions

After the meeting, distinguish the accepted record from rough notes or an automatic transcript. Ask the secretary to confirm which motions were adopted and which ideas were only discussed. An action list needs the recorded decision, owner, due date and source paragraph. Leave missing owners or dates blank until someone confirms them. Grantkeeper can prepare that list and draft tasks, but it should not turn a suggestion into board approval. Keep confidential discussions out of shared task lists. When an owner reports completion, link the evidence or checked result rather than marking every old action complete just because another meeting has arrived.

Gather and organize 990 records only

Use the checklist supplied by your qualified preparer for the exact year under review. Gather and organize the requested financial reports, governance records and program summaries under those headings. Do not assume every church or nonprofit has the same filing duty or needs the same form. Those decisions belong to the preparer. Grantkeeper can build a document index that says where a requested record is located, which year it covers and what remains missing. It does not choose classifications, answer tax questions, determine exemptions or fill a return. If the checklist asks for something unclear, record a question for the preparer instead of guessing what would satisfy it.

Keep the year-end handoff reviewable

Label each supplied file with its reporting period and owner. Preserve the original export and any later corrected version, and explain the difference in the index. If a requested record is missing, say missing rather than not applicable. A finance lead or preparer decides whether an item applies and how to resolve it. Keep a question log with answers and dates so staff do not ask the same thing through several email threads. Grantkeeper’s role is to gather and organize this handoff. The final review, any form preparation and any filing stay with the responsible qualified person and the organization’s normal approval process.

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: Packet version check, Board action list, 990 document index. Integrations: Dropbox, Notion, QuickBooks, Xero.