Request intake

For fixed-scope requests, custom packs, and commercial follow-up. The goal is to get enough context for a useful scoped reply, not to route you into a placeholder.

Email stays the default channel because scope, artifacts, and constraints are easier to review, forward, and verify in a written thread. No form. No routine calls.

Start intake by email hello@civitasanalytica.com

What to send

organization or project name, plus the responsible owner
objective, review trigger, and why it matters now
clear scope boundary: what is in and what is out
deadline, reviewer window, or internal timing constraint
available artifacts: links, files, screenshots, or policy docs
privacy, legal, or commercial constraints and the best contact details

Why email

it supports direct artifact and file links without reformatting
it keeps scope, questions, and decisions in an attributable written thread
it fits the async operating model; there is no form and no routine call scheduling

What happens next

Acknowledgement typically lands inside 1 business day. If key context is missing, the first reply asks for it.
Scope triage usually follows in 2-3 business days, depending on materials and constraints.
If there is fit, you receive a bounded email outline covering deliverables, boundaries, next step, and expected working cadence.