Research Administration Software: Pre Award to Closeout Without Shadow Spreadsheets in Every Department

Why research administration is the least forgiving system on campus

It is day 104 after the end date on a five year NIH award. The final Federal Financial Report is due at 120 days. The grant accountant has the award in the finance ERP showing $41,388 of unexpended balance, the department has a shadow spreadsheet showing $12,000 because they are counting a subaward invoice that has not arrived, and a cost sharing commitment from year two was met with faculty effort that was never certified against the right account. Three people are on a call trying to agree what number goes in a federal report. Nobody is confident. The report will be filed anyway.

This is the recurring shape of research administration at a mid to large research university. The systems are not missing. Kuali Research, Cayuse, InfoEd Global, Huron Research Suite and Streamlyne all exist and each covers real ground. Kuali and Huron are genuinely capable across the pre award and post award lifecycle. The trouble is the seam between whichever of those you run and your finance ERP, because the sponsored project is a financial object in one system and an administrative object in the other, and the two are reconciled by people.

Problem 1: proposal budgets are built in Excel because the system cannot express your rates

A proposal budget is not a list of costs. It is a model with a salary base, an escalation assumption per year, fringe rates that vary by employee class and change at the fiscal year boundary, a facilities and administrative rate negotiated with your cognizant agency that applies to a defined base with exclusions, subaward first 25,000 handling, participant support that is excluded from the base, and cost sharing that may be mandatory or voluntary committed. Then the sponsor has its own form with its own categories and its own limits.

What a custom build does: hold rates as versioned data with effective dates and bases, so a proposal spanning a rate change computes correctly across years without anyone remembering to switch. Model the budget as a structure that can be extended per sponsor program rather than as a fixed set of lines. Then generate the sponsor forms from the model rather than asking anyone to retype. The rule we apply is simple: if the administrator has to open Excel, the build has failed at that point, and we treat every Excel escape as a defect to be fixed rather than a workaround to be tolerated.

Problem 2: award setup is manual re-keying between two systems that both think they are authoritative

The notice of award arrives. Someone reads a PDF and creates an award record in the research system. Someone else creates a project and a set of accounts in the finance ERP. The budget gets entered again, by period, by category. Terms and conditions get summarised into a field. Compliance approvals for human subjects, animals, biosafety and conflict of interest get checked against other systems, and if one is missing the account is set up anyway with a note.

What a custom build does: one award object that owns the terms and the budget structure, and a deliberate one way posting relationship to the finance ERP for the ledger. The ERP owns actuals because that is what a general ledger is for. Your layer owns the award, the budget periods, the commitments the ledger does not know about, and the reconciliation. Automated compliance gating is the piece that pays for itself immediately: an account cannot be released while a required protocol approval is missing, and the requirement is derived from the proposal rather than remembered. Document extraction handles the notice of award itself, pulling period dates, amounts, reporting deadlines and terms into fields for a specialist to confirm rather than transcribe, which turns a two hour setup into twenty minutes.

Problem 3: subawards are where the money and the risk both leave the building

A large award passes 30 percent of its value to three collaborating institutions. Under Uniform Guidance you are the pass through entity, which means you owe risk assessment of each subrecipient, a properly formed agreement, monitoring during the period, review of their invoices against their budgets, and reporting of the subaward under federal transparency requirements. In practice this runs on email, a Word template modified per agreement, and a folder of PDF invoices.

What a custom build does: the subaward is a child award with its own budget, period and terms. Invoices arrive as documents and become structured lines through extraction, then validate automatically against the approved budget and remaining balance with exceptions routed to the department for review. Risk assessment is a scored workflow that repeats annually rather than a memory. Reporting obligations generate as tasks against dates rather than being remembered by the person who has always done it. And the invoice that arrives 100 days after the award ended, which is the classic closeout killer, is anticipated because the system knows what has not yet been billed.

Problem 4: effort certification is a ritual that convinces nobody

Twice a year a form goes to faculty asking them to certify that the percentage of effort charged to each sponsored account reasonably reflects the work performed. The faculty member sees percentages produced by a payroll distribution set months earlier, has no memory of the period, and clicks certify. The institution now holds a signed statement that means very little, obtained at meaningful administrative cost, and it is one of the most reliable audit findings in the sector.

What a custom build does: reduce the distance between the person and the number. Show the certifier what was actually charged with the payroll detail behind it, show the committed effort from the proposal and the award alongside it, and highlight variance rather than presenting a clean percentage as though it were self evidently correct. Where committed effort was 20 percent and charged effort was 8 percent, that is a cost sharing question and an award compliance question, and it should be surfaced at certification rather than found later. Some institutions have moved to payroll confirmation approaches instead of periodic certification, which the Uniform Guidance permits within its internal control requirements. Whichever model your institution uses, get it decided with your research compliance office before design, since it changes the data model rather than a screen.

Problem 5: closeout is a deadline you meet with numbers you cannot defend

Federal awards carry a closeout timeline after the period of performance ends, and the final financial report has to tie to your general ledger. What stands in the way is predictable: late subaward invoices, unliquidated encumbrances, payroll accruals that cross the end date, cost transfers proposed at the last minute, cost sharing that was committed and never documented, and equipment or fabrication that needs a disposition decision.

What a custom build does: start closeout at 90 days before the end date, not after it. A closeout workspace opens automatically with a checklist derived from the award's own characteristics, meaning subaward reconciliation appears only where subawards exist and equipment disposition appears only where equipment was purchased. Every open item has an owner and a date. Cost transfers proposed inside the closeout window carry a mandatory justification and route for approval with the age of the original charge visible, because a transfer of a nine month old charge is a different risk from a two week old correction. The final report is generated from the ledger with an explicit variance report showing anything that does not tie and why, so the number you file is one you can explain a year later to an auditor who has no memory of the phone call.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape for research administration. A first release covering proposal budgeting with versioned rate structures, institutional routing and approval, sponsor form generation for your top submission paths, and award setup with automated compliance gating and posting to the finance ERP runs $120,000 to $250,000 and ships in 16 to 24 weeks. A full platform adding subaward lifecycle with invoice validation, effort certification or payroll confirmation, cost share tracking, invoicing and letter of credit draws, and the closeout workspace runs $400,000 to $1.2M phased over 12 to 24 months. This is the most expensive category on a university campus and any developer quoting materially below that range has not understood the finance integration.

What drives price up specifically: the finance ERP, because a chart of accounts designed in 1998 and a sponsored projects module bolted on later can consume months on their own. The number of agency submission paths you support, since each system that receives proposals speaks its own protocol and formats. The number of rate agreements, which multiplies for institutions with affiliated hospitals or multiple campuses. And the number of departments running shadow spreadsheets, because every one of those contains a requirement nobody has written down and discovering them is real work.

Build versus buy, and when buying is the right call

Buy, and do not call us, if you administer under about $25M a year with a small number of sponsors and no complex rate structure. Streamlyne or Cayuse configured properly will serve you, and the difference between a good configuration and a custom build at that volume is not worth the multiple. Institutions in this position should hire experienced research administrators before they buy software of any kind.

Build, or more precisely build a layer, when two or more of these are true. First, every department runs a shadow spreadsheet, which is the clearest signal that the central system does not answer the question people actually have. Second, award setup takes more than two weeks from notice of award to a spendable account. Third, your closeout process routinely produces final reports that required a negotiated number. Fourth, subaward invoices are validated by reading rather than by rule. Fifth, you have received an audit finding related to effort, cost transfers or subrecipient monitoring in the last three years.

Our honest position: rip and replace of a full research administration suite is rarely the right project, and we would advise against it in most cases. The successful pattern is keeping your system of record for proposals and awards, and building the layer that makes it usable, meaning budgets that express your reality, a PI facing view that includes commitments, subaward invoice validation and a closeout workspace. That layer is a fraction of the cost of a replacement and delivers most of the benefit inside a year.

How to choose a developer for research administration software

Ask them to explain the difference between a modified total direct cost base and total direct cost, and how they would model an exclusion. If that question produces silence, they will learn Uniform Guidance on your budget and the first version will be wrong in ways that reach your federal reports.

Ask what they have actually built against agency systems. Submission to Grants.gov is a different problem from an agency portal with its own validation rules. Ask for the specific path and how they handle a rejection at 4:55pm on a deadline day, because that scenario decides whether faculty trust the system.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else. At Digital Heroes the code is yours from the first commit. Research administration records support federal reporting and audit defence for years after an award closes, and that history should never sit inside a vendor relationship you might want to end.