Welcome to Agentic Effort Reporting thatassembles each certification from committed and charged effort.

Effort reporting asks a professor to certify percentages nobody tracked, months after the fact. Risely's agents assemble each certification from what was committed and what was charged, and the PI signs a form that is finally ready to sign.

Effort certifications · spring cycle

3 need a look · 38 ready

The early-career awardmatches the commitment
The clinical awardcalendar shows 32% against 40% committed
The energy awardmatches the commitment

The variance becomes discussable

evidence attached
committed
40%
calendar
32%

Risely's agents assemble and chase. The certification itself waits for its person.

The certification assembles itself from the record.

Committed effort comes from the award. Charged effort comes from payroll. The form arrives with both already on it, so certifying becomes a review instead of an act of reconstruction.

Where the form comes from

The awardwhat the proposal committed
Payrollwhat the ledger actually charged
The certificationshows both on one form, ready to review

The professor used to reconstruct percentages from memory, months late. Now the form arrives already built.

The variance surfaces while the semester is still on.

Committed says 40% and the calendar shows 32%, and that gap is a finding waiting to happen. Flagged now, with evidence attached, it becomes a payroll adjustment instead of a repayment.

One award, two numbers

comparing

committed
40%
calendar
32%

The gap surfaces while the semester is still on, with the calendar evidence attached. The correction is a payroll adjustment rather than a repayment.

The chase runs itself. The signature stays human.

Risely's agents draft, attach, remind, and escalate what stalls. The certification itself carries legal weight, so the signature belongs to the PI and never to the system.

Who does what

·Certification draftedRisely's agents
·Evidence attachedRisely's agents
·Reminder sent twiceRisely's agents
·Certifiedthe PI and only the PI

A certification carries legal weight, so the signature is never automated. Everything before it is.

The audit reads one record.

A federal audit samples one certification and judges the whole institution by what it finds. Here it finds the commitment, the charges, the variance note, and the signature in one place, which is the entire defense.

What the sample finds

pulling

·The commitment comes from the award
·The charges come from payroll
·The variance note carries its evidence
·The signature is dated

A federal audit samples one certification and judges the institution by it. This one holds together.

One charge moves. The cycle re-checks.

A payroll correction, a mid-semester course release, an award that starts late. Any of them changes what a certification should say, and every one runs the same way.

  1. A payroll correction posts

    one month re-charges to a different award

  2. The certification re-assembles

    committed and charged, side by side

  3. A variance flags itself

    with the calendar evidence attached

  4. The conversation happens early

    while the semester can still absorb it

  5. The PI certifies

    one signature leaves nothing to chase

What changes, and how it runs.

Cycles close without the chase

38 of 41 certified on the first pass.

Variances get caught in-semester

The correction is an adjustment instead of a repayment.

The audit finds one record

Commitment, charges, variance note, and signature together.

The technical read

Connects read-only to your grants system, payroll, and HR records to start

The PI signs every certification

Every action lands on an append-only log

SOC 2 Type IIFERPAGDPR

Runs alongside what you have. Nothing rips out.