Key takeaways
-
Pre-award and post-award are not two separate problems handled by two separate teams that never need to talk. They are one continuous handoff, and the gap between them, the moment an award becomes active, is exactly where institutions lose track of budget details, compliance obligations, and invention disclosure deadlines that started at proposal time.
-
Closeout is not a formality at the end. Federal awards generally require all final reports submitted and all financial obligations liquidated within 120 days of the period of performance ending, and that clock starts whether or not the institution has actually finished reconciling the award internally.
-
A research administration workflow that tracks the grant but not the invention disclosure clock running in parallel is missing a deadline research administration doesn't own but still depends on the PI meeting: two months to disclose an invention, two years to elect title.
Why "pre-award" and "post-award" are really one continuous handoff problem
Sponsored programs offices are typically organized around the moment an award becomes active, with pre-award staff handling proposal development and post-award staff handling compliance and spending. This division makes operational sense and creates a real coordination gap: the budget assumptions, the compliance commitments, and the intellectual property considerations built into a proposal do not automatically transfer to whoever manages the award once it starts.
A PI's certification made at proposal time, a subrecipient commitment negotiated during budget development, or an anticipated invention flagged during the science itself can all get lost in the handoff if nothing carries that context from the pre-award record into the post-award one, including the subrecipient monitoring duties that continue once the award is active.
What pre-award actually has to clear before a dollar is spent
Institutions sometimes need to spend before an award is formally active, to keep a project moving while the paperwork finalizes. Under 2 CFR 200.458, costs incurred before the award's start date are allowable only if they were necessary for timely performance, would have been allowable had they occurred after the start date, and carry written approval from the federal agency.
An institution that spends ahead of an award without securing that written approval first has created a cost the audit will treat as unallowable, regardless of how reasonable the spending was on its own merits.
What changes the moment the award is active
Once an award is active, the institution takes on ongoing obligations that pre-award activity did not carry: budget revisions above a defined threshold need prior sponsor approval, internal controls have to demonstrate the institution can actually manage the award responsibly, and any subaward relationship comes with its own monitoring obligation.
None of this is new information to a research administration office in the abstract, and the same internal control expectation applies regardless of which stage the award is in. What is often missing is the specific continuity: does the office managing post-award compliance actually have the pre-award record showing what was proposed, budgeted, and committed, or is it reconstructing that context from the award notice alone.
The technology transfer clock nobody outside the tech transfer office tracks
A discovery made under a federally funded project triggers its own timeline, independent of the grant's own reporting schedule. Under 37 CFR 401.14, an institution must disclose a subject invention to the funding agency within two months of the inventor's written disclosure to the institution's own patent personnel, and if the institution elects to retain title, that election has to be made within two years of the disclosure to the agency, or sixty days before certain statutory bars on patentability take effect, whichever comes first. NIH's own Bayh-Dole guidance walks through this same framework for NIH-funded research specifically.
A PI who mentions a potential invention to a program officer in a progress report, without that mention ever reaching the technology transfer office, has started a clock nobody is actually watching.
What closeout actually requires, and how late it starts
Closeout is not the moment an award naturally winds down. It is a specific deadline: under 2 CFR 200.344, a recipient must submit all required financial, performance, and other reports, and liquidate all financial obligations under the award, no later than 120 calendar days after the period of performance ends.
An institution that treats closeout as a project to start once the award has clearly ended is starting 120 days late against a clock that began the day the award's performance period actually concluded, not the day someone in sponsored programs noticed.
The research administration lifecycle, stage by stage
|
Stage
|
Deadline or trigger
|
What has to carry forward
|
|
Pre-award spending
|
Requires written sponsor approval before the award start date
|
Documentation the cost was necessary and would have been allowable later
|
|
Budget revisions
|
Prior approval required above defined thresholds
|
The original proposed budget as the baseline for what counts as a revision
|
|
Invention disclosure
|
Two months to the institution; two years to elect title with the agency
|
PI communications flagged for technology transfer review
|
|
Closeout
|
120 days after the period of performance ends
|
Final financial and performance data reconciled against the original award
|
A governed pre- to post-award workflow
Proposal-stage commitments carry forward automatically into the active award record
Budget assumptions, subrecipient commitments, and compliance certifications made at proposal time are attached to the award once it activates, not left behind in a separate pre-award file.
Pre-award spending requests route through the specific approval 2 CFR 200.458 requires
A request to spend ahead of an award's start date is checked against the written approval requirement before any cost posts, not discovered as a problem during the next audit.
Budget revisions are checked against the original proposal baseline
The workflow can show what changed and by how much, supporting the sponsor approval determination under 2 CFR 200.308 rather than requiring someone to reconstruct the original budget from memory.
Any mention of a potential invention routes to technology transfer immediately
A PI's report, email, or presentation referencing a new discovery triggers a flag to technology transfer, starting the two-month disclosure clock deliberately rather than by accident.
Closeout begins counting down from the actual period-of-performance end date
The 120-day clock is tracked from the real end date, not from when someone in sponsored programs happens to open the file, giving the institution the actual time available rather than a shortened version of it.
Every office involved sees the same award record
Pre-award, post-award, and technology transfer are working from one connected record instead of three separate ones that each know only part of the award's history.
Kissflow and the research administration stack
Kissflow is the governed execution layer at the edges of the research administration stack. It does not replace the sponsored programs office's judgment, the PI's science, or the technology transfer office's patent strategy. It replaces the handoff gap between pre-award and post-award, and between post-award and technology transfer, where context currently gets lost because each office works from its own record.
If your institution runs Cayuse, Huron, or Kuali for research administration, Kissflow does not compete with any of them for grant and contract records. It sits alongside them as the layer that carries proposal-stage context into the active award, flags pre-award spending and invention disclosure moments as they happen, and counts down closeout from the actual date it starts.
The differentiation that matters to a research administration office: when a sponsor's specific pre-award cost policy differs from the institution's default, or a new invention disclosure requirement applies to a particular award, the office updates the workflow directly, instead of retraining every PI and department on an exception a generic grants system was never built to flag.
Frequently asked questions
1. Can an institution spend on a project before the award officially starts?
Only with written approval from the federal agency, and only for costs that would have been allowable had they been incurred after the award's start date. Spending without that approval first creates an unallowable cost.
2. How long does an institution have to disclose an invention made under federal funding?
Generally two months from when the inventor discloses it in writing to the institution's own patent personnel, with a separate two-year window from disclosure to the agency to elect whether to retain title.
3. What has to happen within 120 days after an award ends?
All required financial, performance, and other reports must be submitted, and all financial obligations under the award must be liquidated, unless the agency grants a justified extension.
4. Why does the handoff between pre-award and post-award create risk?
Because budget assumptions, compliance commitments, and potential invention disclosures made during proposal development do not automatically transfer to whoever manages the award once it becomes active, unless something specifically carries that context forward.
5. Does every budget change on an active award need sponsor approval?
Not every change, but reallocations above defined thresholds between budget categories generally do, and the determination depends on comparing the requested change against the originally approved budget.
6. Does Kissflow replace our research administration system like Cayuse or Huron?
No. Kissflow is the workflow layer that connects pre-award, post-award, and technology transfer records and tracks the deadlines that span all three. The research administration system remains the system of record for the underlying grant and contract data.
Request a 30-minute walkthrough to see how Kissflow connects pre-award, post-award, and technology transfer into one continuous workflow instead of three disconnected records.
