How a review moves

The audit trail

Follow the Buildgridbase process for a secure, bounded bursary application supporting-record audit from enquiry to recheck.

Reviewer making careful notes beside ordered paperwork

1. Name the bursary, not your identity number

The first enquiry should contain the provider, programme, public checklist link, deadline and approximate page count. Do not attach records. We use these details to determine whether the review fits our scope and calendar.

2. Agree the boundaries

Our written estimate names the records to be reviewed, fee, target date, included clarification and deletion schedule. It also notes work we will not perform. You accept this scope before any copies are requested.

3. Transfer only the agreed copies

We provide transfer instructions after booking. Keep all originals. Remove unrelated information where the funder does not require it, and never send card PINs, passwords or portal credentials.

4. A reviewer creates the audit note

The reviewer reads the funder checklist alongside the supplied set. Observations reference a file or page and use four plain categories: missing, inconsistent, unclear, or confirm with funder.

5. You act on the note

Corrections remain yours. You may need to revisit an issuing institution, commissioner of oaths, school, university or funder. The clarification round explains our notes but cannot replace guidance from those bodies.

6. Limited recheck and deletion

Where included, corrected pages are checked within the stated window. Working copies are then deleted according to the agreed retention period, unless law requires otherwise.

Have a checklist and closing date?

That is enough for the first conversation. Keep personal records out of the web form.

Describe the application