Request Intake

Every request for user data starts as a message in some channel. Intake turns that message into a record with an owner, a receipt time and a set of fields that the later steps rely on.

Intake is the opening step in the lifecycle of a law enforcement data request. It begins when something arrives and ends when the request is logged and handed to the next step.

Where requests arrive

Requests reach a company through whichever channel the requester can find. Agencies send email and paper. Some serve a registered agent, and some complete a web form the company publishes. Under the EU e-Evidence Regulation, authorities and providers also exchange orders through a secure decentralised IT system, which carries each order as structured data.

What arrivesWhat intake has to establish
EmailA message with attachments and a sender addressThe original message and every attachment, stored unaltered with the receipt time
Post or registered agentA paper document, delivered to an office or served on an agentThe date of receipt, the person who took delivery and a scan of the whole document
Web formFields the requester completed and an uploaded instrumentThe completed fields together with the uploaded document, under one request number
System-to-systemA structured order sent through a platform or the EU’s decentralised IT systemThe issuing authority, the order’s own fields and the time the system recorded receipt

What intake records

Whatever the channel, intake writes down the same facts about the request:

  • Requester and agency. The name, title, agency and contact details as stated.
  • Instrument type. Subpoena, court order, search warrant, preservation request, emergency request or another instrument.
  • Authority cited. The statute, rule or court order the request relies on.
  • Scope. The accounts or identifiers named and the date range covered.
  • Deadline. The return date, or the time limit the instrument sets.
  • Non-disclosure condition. Any order or instruction that bars telling the account holder, with its end date.

What intake feeds

Four later steps work from the intake record:

  • Verification confirms that the requester is the official the request names.
  • Classification identifies the instrument and the data it can reach.
  • Routing sends the request to the reviewer who handles that instrument.
  • The deadline is set from the receipt time and the instrument’s own terms.

Under Regulation (EU) 2023/1543, an addressee that receives a European Production Order Certificate with no notification to the enforcing State sends the data within 10 days of receipt. In an emergency case the period is eight hours from receipt, so the receipt time written at intake is where both periods start.

When intake is informal

A request that lands in one employee’s personal inbox can sit unread while its deadline runs. Two employees who each receive a similar request can answer it differently. When a regulator or a court later asks what the company disclosed and why, no record exists to show it.

Frequently asked questions

What does request intake capture?

Intake captures the original document, the requester and agency, the instrument type, the authority cited, the accounts and date range named, the deadline and any non-disclosure condition. It also records when the request arrived and who received it, so every later step works from the same record.

Why does the receipt time matter?

Many deadlines run from receipt. Under the EU e-Evidence Regulation, an addressee has 10 days from receipt of a European Production Order Certificate that needs no notification, or eight hours in an emergency case. Subpoenas carry their own return dates. A logged receipt time lets the company show when each clock started.

Is intake the same as verification?

Intake comes first. It receives and logs the request and records what the requester says about themselves. Verification then checks those details and confirms that the requester is a real official with authority to ask.

See what
we can do
for you.

Request a demo