Cross-returns submission readiness
One place to answer “are my statutory returns ready to submit?”. Every return builder is driven and its bespoke findings normalised into a single ready / warnings / blocked verdict, then rolled up worst-of into one portfolio status.
What this is
Each statutory return is driven over a deterministic synthetic portfolio. The portal builders' cross-row findings, the HESA sign-off verdict, and the TCSI pipeline status are all normalised into one uniform summary: blocking errors, advisory warnings, and the rows the verdict was computed over.
How to use
- 1.Read the overall verdict — the worst-of across the portfolio (blocked beats warnings beats ready).
- 2.Scan the cards: blocked returns first, then warnings, then ready.
- 3.For a blocked return, clear the blocking errors before the submission window opens; for warnings, review the advisory findings.
- 4.Regenerate the same scorecard from the CLI: `databridge returns readiness` (add `--out` to write docs/RETURNS_READINESS_SAMPLE.md).
- Errors
- 1
- Warnings
- 1
- Rows
- 2
View findings
- Errors
- 0
- Warnings
- 1
- Rows
- 1
View findings
- Errors
- 0
- Warnings
- 1
- Rows
- 2
View findings
- Errors
- 0
- Warnings
- 0
- Rows
- 4
View findings
- Errors
- 0
- Warnings
- 0
- Rows
- 1
View findings
- Errors
- 0
- Warnings
- 0
- Rows
- 8
View findings
Synthetic demo portfolio
This scorecard is driven over deterministic synthetic data (no citation needed). To check your own returns, use the panel below — it runs live through the POST /returns/readiness endpoint (also the CLI’s returns readiness --input).
Paste a ReadinessInputs JSON — any subset of the six returns’ builder inputs. It runs live through POST /returns/readiness, the same engine as the CLI’s returns readiness --input.