Compliance support

Preparing an Executive Office for a Regulatory Document Request

A regulatory document request routine for an executive office, covering the request owner, the records map, the collection controls, and the production record.

4 min readHireExecutiveTeam editorial
Preparing an Executive Office for a Regulatory Document Request article illustration
Table of contents
  1. Name the request owner and the legal contact
  2. Map the request to records that already exist
  3. Control the collection and the privilege review
  4. Produce the response and preserve the record
  5. Related resources
  6. Frequently asked questions

Record the date the request arrived, the authority that sent it, and the response deadline in one request log. An email that sits in a shared inbox while three people assume someone else owns it can consume most of the response window. Record the owner and the legal contact on the same row. The log should be the single place the office checks for status.

Assign one request owner in the executive office and one legal or compliance reviewer who can approve the scope. A response assembled by several people without a named owner tends to answer the easiest questions and miss the mandatory ones. Record both names and their deputies. The owner should have the authority to stop collection when the scope is unclear.

Read the request literally and list the categories, date ranges, custodians, and formats it names. A request for communications about a specific decision is different from a request for every message in a mailbox. Record the exact language beside each category. The legal reviewer should confirm the reading before anyone searches.

Confirm the deadline in writing with the requesting authority when the date or the delivery method is ambiguous. A response sent to the wrong address or in the wrong format can be treated as late even when it was prepared on time. Record the confirmation and the contact. The confirmation should be stored with the request log.

Map the request to records that already exist

Draw a records map that shows which systems hold the requested categories and who administers each one. An executive office may hold records in email, calendar, chat, document management, travel, and paper files, and each has a different search method. Record the system, the custodian, and the search capability. The map should be reviewed before the first search rather than assembled during it.

Identify the executive's devices and accounts that fall within the request, including shared mailboxes and delegated calendars. A search that covers only the primary inbox can miss the assistant's mailbox where the actual coordination happened. Record each account and the reason it is in scope. The legal reviewer should approve the list of sources.

Check whether the request touches privileged legal advice and route those records to the legal reviewer before collection. An executive office often holds legal advice without labelling it, and a broad collection can waive a protection the organisation intended to keep. Record the privilege flag and the reviewer. The collection team should not decide privilege on its own.

List the records that are missing or are likely to be difficult to produce, and raise them with the requester early. A gap explained at the deadline looks like concealment, while a gap explained at the start can be managed. Record the gap and the proposed approach. The legal reviewer should approve any explanation before it is sent.

Control the collection and the privilege review

Give each collector a written search protocol with the terms, the date range, and the fields to preserve. Two collectors using different terms will produce a set that cannot be described consistently in the response. Record the protocol, the collector, and the date. The protocol should be attached to the request log rather than kept in a personal note.

Preserve the original records and work from copies so the collection does not alter the source. Opening a file can change its metadata, and a changed timestamp can undermine the response later. Record the preservation step and the hash where the system supports one. The original should remain in place until the matter is closed.

Log every document collected with its source, its date, and the reason it is responsive or non-responsive. A production without a document-level log cannot be defended when the requester asks how the search was conducted. Record the identifier and the decision. The log should be reviewable by someone who did not run the search.

Run a privilege and redaction review before anything leaves the office, and record each redaction with its basis. A document released with an unredacted third-party name or an internal legal note can create a new problem while answering the old one. Record the redaction, the reviewer, and the date. The reviewed version should be the only one sent.

Produce the response and preserve the record

Check the production against the request categories one more time before it is released. A response that answers nine of ten categories is still incomplete and may invite a follow-up request. Record the category, the count, and the reviewer. The final check should happen on the exact files that will be delivered.

Send the response through the channel the authority specified and keep the transmission confirmation. A production delivered by an informal link can be disputed even when the files were correct. Record the recipient, the timestamp, and the method. The confirmation should be attached to the request log.

Write a closing note that states what was produced, what was withheld, and what remains outstanding. A file that is closed with no summary forces the next person to reconstruct the matter from the correspondence. Record the summary, the approver, and the close date. The note should be short enough to read before a follow-up call.

Keep the request log, the collection protocol, and the production record for the retention period the legal team sets. A matter that is reopened after the files are destroyed becomes a defence problem rather than a records problem. Record the retention date and the custodian. The legal team should confirm the period in writing.

Read also: records disposal certificate log and document retention coverage audit.

Frequently asked questions

Should one assistant support the whole executive team?

Sometimes. It works when priorities are clear and executives share one operating rhythm.

What should happen before a consult?

List the meetings, inbox rules, recurring reports, and decisions that need support.

Ready to define the role?

Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.

Book a consultation