R&D Recommendations

Projects the AI thinks qualify for R&D tax credits — promoted from your live portfolio, ranked by estimated qualifying spend, ready to accept or dismiss.

The R&D recommender filters RdClaim records to those where stage === 'RECOMMENDATION'. These are AI-surfaced opportunities. They are not claims yet — they are candidates. Accepting one promotes it to DRAFT and routes it into the claim review flow.

Reading the page

Findings are grouped using the shared RecommendationsTable component — same component the CapEx recommendations page uses, so the UX is consistent.

Each row shows:

• Project name — the live project the claim would be built around.
• Fiscal year — formatted to the framework's start month (e.g. UK fiscal years render as 2024/25).
• Reason — a short rationale from the analysis agent for why this project looks like an R&D candidate.
• Estimated impact — the estimated qualifying spend in the framework's currency, when FINANCIALS_VIEW_SUMMARY is granted. Otherwise hidden.

Actions

Action	Mutation	What happens
Accept	rdClaimAccept	Promotes the recommendation: claim moves to DRAFT stage, routed into the rationale writer for narrative capture
Dismiss	rdClaimDismiss	Hard delete. The claim is removed; the underlying signal will not surface it again unless circumstances change materially

Both mutations refetch ListRdClaims and await the refetch, so the row disappears from the recommendation table and (on accept) shows up in the overview under the appropriate stage group.

WARNING

Dismiss is a hard delete, not an archive. There is no "restore" path. If you dismiss a recommendation and decide later it should have been claimed, you will need to create the claim manually from the project page.

What "accept" gets you

Accepting does not file anything. It moves the claim into draft and opens the runway for:

1. The owner writes the technical narrative in the claim review rationale writer.
2. The claim moves through the approval workflow.
3. Once approved and submitted, it lands in the archive for the next inspector.

Empty state

If no RECOMMENDATION stage claims are open, the page renders the empty state. That means the recommender has nothing it considers worth flagging right now. New recommendations get generated as project metadata changes — new lifecycle stages, new cost centre bindings, fresh effort data.

Related

• R&D overview — every claim, every stage, in one queue.
• Claim review — where accepted recommendations get turned into filed claims.
• Approval workflow — who signs off on the claim before it gets submitted.