Minimum viable context
Name the market, service option, blocker, deadline, and team owner. That lets the first review decide whether the request is a fit without exposing unnecessary material.
Request
Start here when you know the pressure is real but the safest first step still needs to be scoped.
Use this page to choose a starting option, explain the blocker, and keep the first request manual and non-sensitive.
Before you send anything
- Do not send credentials.
- Do not send regulated internal documents.
- Keep the first request high level and specific.
What to include and what not to send yet
A good first request is small, specific, and easy to route to the right lane.
- Include the service interest, the country or market context, the current blocker, and any relevant deadline.
- Do not send credentials, regulated internal documents, or raw supplier exports.
- If the fit is real, the next step is a scoped first review and a secure file exchange only after that fit check.
What happens after submission
The request is reviewed manually to confirm the best-fit lane and the smallest sensible first engagement.
- Confirm the actual issue and team owner.
- Route the request to Regulation Radar, Supplier Readiness Workspace, or Audit Pack Support.
- Keep the work inside the not-legal-advice and secure file-exchange boundary.
How public-form trust is handled
The form is designed for low-sensitivity routing. It uses HTTPS, length limits, honeypot and rate-limit controls, and a private server-side queue outside the public web root. It is not a place to upload or paste regulated evidence.
Manual review
A human review step confirms fit and scope before a paid engagement, secure file exchange, legal-review question, or deeper evidence request is proposed.
Preference control
Newsletter or follow-up preferences require a positive request and can be withdrawn through the contact route.
Send a RegulationsOffice request
Keep the first request high level. Initial review stays manual until a secure file exchange path is agreed. Submissions are routed to a private server-side review queue; do not send sensitive files through this public form.