How Should Grants Teams Document Conflict-of-Interest Decisions?
Connect disclosures and recusals to reviewer access, accepted scores, and award approval
Published
A reviewer discloses a relationship with an applicant after opening the proposal and saving a draft score. The programme records a recusal, but can it show which material the reviewer accessed, what happened to that score, and which reviewers contributed to the final award decision?
Keep a connected record of the disclosure, authorised determination, affected assignments, access changes, score treatment, and approval. A conflict of interest can involve a financial, professional, institutional, or personal relationship that raises a question about impartiality. The programme's policy determines which relationships require disclosure and how they must be handled.
Start with the programme's rules and decision authority
Disclosure, conflict determination, and recusal are separate events. A disclosure reports a relationship or interest; the authorised officer determines its significance; recusal removes participation within the required scope. A possible match should create review work with a recorded outcome.
Policies differ. NIH's peer-review guidance gives an employment-conflict example in which a reviewer cannot evaluate one application or attend its discussion but may review others. Other circumstances can have a broader scope. Record the actual application, competition, panel, or period covered by the decision.
Separate reviewer-integrity rules from recipient disclosure duties. For U.S. federal awards, 2 CFR 200.112 requires recipients and subrecipients to disclose potential conflicts in writing according to the federal agency's policies. That does not establish one universal reviewer or waiver procedure for every foundation, institution, or funding programme.
Follow the decision from disclosure to effect
- 1 · Disclose
Capture the relationship
Identify the person, applicant or organisation, relevant dates, affected work, and supporting declaration.
- 2 · Determine
Record the authorised outcome
Retain the policy version, reviewer, rationale, scope, and any permitted conditions or expiry.
- 3 · Apply
Change participation
Reconcile assignments, document access, notifications, discussion participation, and score eligibility.
Screen relationships before granting application access
Maintain identities for reviewers, applicants, investigators, institutions, and partners. Use controlled relationship types and relevant dates alongside explanatory text. Record which information and rule version produced a match, who resolved it, and when the decision took effect.
Give reviewers the information needed to identify conflicts through the approved screening process before releasing the full application package. Where a conflict is reported later, preserve the earlier assignment and available access evidence. Distinguish an assignment, an attempted request, a successful download, and participation in a discussion; one event does not prove all the others occurred.
NIH's confidentiality guidance, for example, restricts disclosure of review materials to authorised participants and requires confidentiality certification before access. Apply the relevant programme's confidentiality and handling rules alongside its conflict policy.
Make recusal affect access and scoring
Implement the authorised decision across application documents, reviewer workspaces, notifications, meeting materials, and scoring. Check direct file and API access as well as the visible assignment list. Measure the time until existing sessions and issued links stop granting access under the agreed policy.
Retain the original review record with its disposition. Mark a draft or submitted score as excluded, replaced, or otherwise handled under the approved decision rather than deleting it and hiding the earlier activity. If a score already influenced moderation or a recommendation, record the reassessment and resulting package version.
Where the applicable policy permits an exception or management plan, record its authorised approver, basis, conditions, scope, expiry, and monitoring. Keep exception approval distinct from a routine administrator changing an assignment.
Preserve the scoring and award context
| Record | What to preserve |
|---|---|
| Application package | Submitted version, accepted amendments, eligibility decision, and released review package. |
| Conflict determination | Disclosure, policy version, authorised decision, affected scope, and participation conditions. |
| Review instrument | Criteria, weights, guidance, scoring scale, calculation, and effective version. |
| Reviewer result | Submitted values and comments, revisions, acceptance or exclusion, reasons, and authority. |
| Award decision | Accepted reviews, adjustments, recommendation version, committee outcome, approval, and issued notice. |
Preserve the inputs and calculation used for the decision. A later rubric change should not silently recalculate an earlier ranking. If moderation changes a score, retain the submitted value, revised value, reason, and approval, with the original conflict outcome still linked.
Work through a late disclosure
Suppose a community skills fund receives application GRT-1042. Reviewer R-17 downloads the proposal and saves a draft score, then discloses recent paid work for the applicant. The programme's authorised officer determines that R-17 must not participate in reviewing that application.
Record the determination
Link the disclosure to R-17, the applicant, GRT-1042, and the applicable policy. Retain the officer's rationale, decision time, scope, and any required follow-up.
Apply and test the recusal
Remove the assignment, stop application-specific notifications, and verify that the reviewer cannot retrieve the proposal or scorecard. Record the earlier download and follow the programme's instructions for previously obtained material; revocation does not recall a downloaded copy.
Reconcile the review package
Preserve the draft score as excluded from the award calculation. Assign an eligible replacement reviewer, retain the replacement review, and record any reassessment needed if the earlier score had already been used.
Approve the current recommendation
Link the final recommendation to the accepted reviews and conflict outcomes. The authorised approver can see which inputs support the award without receiving unrelated private disclosure details.
Separate private disclosures from operational outcomes
A coordinator may need to know that a reviewer is excluded from one application without seeing the financial or personal details behind that decision. Control detailed disclosures separately from the assignment and scoring status shown to programme staff.
Configure retention and disclosure rules by record type and funding requirements. Produce an award record that explains the decision while protecting unrelated confidential material. Keep access and administrative changes reviewable, including corrections after an award.
Test the conflict decision through to the award
- Detect a possible relationship and record an authorised resolution before full review access.
- Recuse a reviewer after a download and demonstrate the access and notification changes.
- Exclude or replace a score without erasing the original record or its reason.
- Reconstruct an award using the rubric and accepted inputs in force at the time.
- Test permitted exceptions against their scope, approval, conditions, and expiry.
- Produce the award record without exposing unrelated private disclosures.
Connect the disclosure to the decision it changes
A useful conflict record shows the relationship reported, the authorised determination, the participation changes, and the accepted evidence behind the award. Keep those records connected as applications, reviewers, and recommendations change.
Sources reviewed: November 12, 2026. NIH examples illustrate NIH peer-review policies; 2 CFR 200.112 addresses applicable U.S. federal-award disclosures. Configure the workflow for the funder, jurisdiction, and institutional rules governing the programme.