Finding, exporting and accounting for records — and the two things Records deliberately cannot do.
Agency-wide visibility and the ability to produce a file, without the ability to alter what a sworn officer attested to.
You work at demo.myjurat.com, signed in with your agency Microsoft account. reporting.myjurat.com is the citizen-facing site; reports filed there arrive on the staff side for review.
Records sees every case at the agency — not just its own — and can export any of them. What it cannot do is sign, and that boundary is the point of the role rather than an oversight.
| You can | You cannot |
|---|---|
|
Yes Create a statement request or victim packet Yes See all pending and completed work Yes Download or export any case Yes View the full audit trail Yes Send a reminder on any case Yes Add or remove an assisting officer |
No Countersign a statement No Store a personal signature No Reassign the primary officer No Revoke a case No Lock or unlock a case No Run a training sign-in sheet No Reach the admin console |
A countersignature is a sworn act by the officer on the case. Records is an administrative role, so it does not hold a signature at all — there is nothing to apply by accident. If a statement is stuck waiting on an officer's signature, the answer is a reminder or a supervisor, not a workaround.
Search is the first stop and covers everything at the agency. Search by case number or by name.
For browsing rather than looking something up:
Every timestamp you see is in your agency's own time zone, set once by your administrator, so nothing needs converting in your head.
The common request: a prosecutor, a defence attorney or a public-records applicant wants a statement.
A victim packet exists in two forms. The officer copy carries the chain-of-custody page — who created and sent the packet, signing times and addresses. The victim copy deliberately does not. When you produce a file, you are producing the officer copy. Do not hand a victim the version you exported for a case file.
Short answer: very little, and never silently.
When an officer submits a form, their editing ends. Only an administrator can correct a completed record afterwards, and every correction is written to the audit trail with the previous and the new value. Answers that the form locks at signing cannot be changed by anyone at all.
So if a record looks wrong, the question is not "who could have quietly changed this" — it is "what does the audit trail say", and it will say.
You have the full audit view. Every consequential action is recorded — who did it, when, and from where. Use it when someone asks how a document came to exist, or whether a statement was altered after signature.
On a victim packet you can also see whether the victim actually downloaded their packet, and when. "Completed" means the documents were signed; it does not by itself mean the victim has the file. That row answers the question directly, in both directions.
You can send a reminder on any case waiting on someone else — a requested statement, one sent back for clarification, one waiting on a signature.
Two things Records cannot resolve, and who can:
| Situation | Who fixes it |
|---|---|
| Waiting on an officer's countersignature | That officer, or a supervisor |
| Wrong primary officer on the case | Supervisor or Admin |
| Created in error, needs revoking | Supervisor or Admin |
| Case needs locking | Admin |
| Statement link expired | Any officer on the case — resend issues a fresh link |
Your administrator sets how long records are kept before becoming eligible for disposal. Records staff should know two things:
Online reporting uses a separate role from your Jurat one. Records staff often hold Supervisor there, which sees every submitted report rather than only assigned ones.
Your agency can also set online reports to Records only, which narrows the queue to Supervisor and Admin levels. If your agency treats online intake as a records-desk function, that is the setting behind it. See the Online Reporting Guide.