Skip to content
DekkoCORE

DekkoCORE · Use caseExample instrument · Matter SW-2026-0418

Title

Warrant applications, reviewed and signed.Without the drive, the fax or the inbox.

DekkoCORE gives police and issuing officers one encrypted place to share a warrant application and its affidavit, request a signature from the judicial officer, and send the signed warrant to the officers who'll execute it. Every view, download and signature is recorded against the document.

Book a demoGo to the operative clauses
Recitals

Whereas, today:

  1. (A)warrant applications are emailed as attachments, then forwarded;
  2. (B)printed affidavits are driven to an issuing officer after hours;
  3. (C)signed pages are scanned, photographed or faxed back; and
  4. (D)copies holding an informant's details are made that nobody can later account for.

This instrument sets out how the same warrant moves in DekkoCORE instead.

Parties and access

Definitions.

In this instrument, with the access each party has in the Hub:

Investigator
“Investigator” means an officer who drafts and updates the application and affidavit.
Editor
Supervisor
“Supervisor” means an officer or legal reviewer who reviews, redacts and sends the warrant for signature.
Manager
Issuing Officer
“Issuing Officer” means the judicial officer who reads the application in the secure viewer and signs after signing in.
Signature request
Registry
“Registry” means the staff who file the signed warrant in their own records.
Download
Executing Officers
“Executing Officers” means the officers who read the warrant on a phone at the door, without keeping a copy.
View only, with expiry
Oversight Body
“Oversight Body” means a body that reviews a matter and its history when asked.
View only
Operative clauses

One warrant, from application to report back.

Search warrant SW-2026-0418, a fictional matter, in six clauses.

  1. 1.21:10Investigator

    The application is drafted in the Hub.

    The Investigator writes the application and affidavit in the browser's document editor, in a Hub that only the people working on the matter can open.

    1. (a)documents are co-edited in the browser;
    2. (b)files carry classification markings; and
    3. (c)no USB drive or printed copy is part of the handover.
  2. 2.21:32Supervisor

    A Supervisor reviews it, and the informant is redacted.

    A Supervisor checks the application. Before it goes further, the informant's details are redacted, which makes a separate copy that recipients can't un-redact.

    1. (a)redaction makes a copy and never touches the original;
    2. (b)recipients can't remove redactions; and
    3. (c)every view is logged against the file.
    Extract from the affidavit, redacted copy

    On 12 October the informant, J. Citizen of 14 Example Street (redacted in the shared copy), observed the vehicle at the premises.

    Original unchanged · Recipients can't remove the redaction

  3. 3.21:40Investigator

    A signature is requested from the Issuing Officer.

    The warrant goes to the Issuing Officer as a signature request, with the supporting documents in the same folder. The request can expire, so an unsigned warrant doesn't sit in anyone's queue indefinitely.

    1. (a)signature, name and date fields are set per signer;
    2. (b)supporting documents are shared alongside; and
    3. (c)the request itself has an expiry.
    Sign hereIssuing Officer · Signature, name, date · Request expires in 12 hours
  4. 4.22:05Issuing Officer

    The Issuing Officer signs, after signing in.

    The Issuing Officer signs in, reads the application in the secure viewer and signs the warrant in the browser. Signers must be authenticated before they can sign, and the signature, its time and its signer are recorded.

    1. (a)signers sign in before they can sign;
    2. (b)signatures and stamps are applied in the browser; and
    3. (c)signed and approved events appear in the file history.

    Issuing Officer

    Signed 22:05 · after signing in

  5. 5.22:20Executing Officers

    The signed warrant goes to the team executing it.

    The signed warrant is shared with the Executing Officers on view-only access, so it can be read on a phone at the door without a copy being saved. Their access can end on a set date.

    1. (a)view-only access works on a phone;
    2. (b)access ends on a set date; and
    3. (c)access can be revoked at any time.
    Shared with the Executing Officers · No download
  6. 6.Day 3Investigator

    The report back joins the same record.

    After execution, the report goes back into the same folder. The application, affidavit, warrant and report sit together, with a history of every view, download, signature and approval ready to export.

    1. (a)one folder holds the whole matter;
    2. (b)each file's history is ready to export; and
    3. (c)tenancy-wide audit logs are there for oversight.

    report_back.pdffiled with the warrant

    1. 22:05SignedIssuing Officer
    2. 22:20ViewedExecuting Officers
    3. Day 3UploadedInvestigator
Schedule 1

Protections.

  1. 1.1Informants stay protectedRedact names before anything is shared. Redaction makes a copy, and recipients can't remove it.
  2. 1.2Staff identities stay internalWith de-identified sharing on, outside parties see a consistent alias instead of an officer's name and email.
  3. 1.3Nobody sees more than their partEach person sees only what's shared with them, and outside parties can't see each other in the Hub.
  4. 1.4DekkoSecure can't read itEnd-to-end encrypted and zero-knowledge, hosted in Australia and IRAP assessed to PROTECTED.
Schedule 2

Annexures: in the product.

Annexure ASW-2026-0418

Signing a document in DekkoCORE: a signature on the signing line, the list of signatories and a Finish approval button
Signed in the browserSignatures, stamps, names and dates applied to the document, with every signatory listed.

Annexure BSW-2026-0418

DekkoCORE file history listing each view, signature, approval and download with the date and the user
Every step, on the recordViews, signatures, approvals and downloads, logged against the file with the date and the user.
Schedule 3

Questions and answers.

Q.Is an electronically signed warrant valid?

That depends on the legislation and practice in your jurisdiction, so your legal team decides whether electronic issue is permitted. DekkoCORE records who signed, when they signed, and every view of the document before and after.

Q.Does the issuing officer need an account?

Yes. Signature requests go to authenticated users, who must sign in before they can sign. They can be invited when the request is sent, and they see only what's shared with them.

Q.Which documents can be signed?

Signature requests support PDF and Word (DOCX) documents, with no file size limit on the request file. Several people can be asked to sign the same document.

Q.How do we protect an informant's identity?

Redact the informant's details before sharing. Redaction creates a copy of the PDF with the redactions applied, which recipients can't remove. Check every redaction before sharing, because search-based redaction may not find every match.

Q.Can executing officers keep a copy?

Not if you share on view-only access. They can read the warrant in the secure viewer, including on a phone, but can't download it, and their access can end on a set date.

Q.Where is the data stored?

DekkoCORE is hosted in-country in Australia, the United States and Canada, and is IRAP assessed for Australian government PROTECTED information.

Execution

Walk us through your next warrant.

Show us how applications reach your issuing officers today. We'll set the same path up in DekkoCORE, with signing, redaction and the record in one place.

Signed by the Issuing Officer

Matter SW-2026-0418 · 22:05

Signed for your agency

Sign here: book a demo
Name, agency and date
Related instruments