Restricted support
If CUI, CDI, ITAR, export-controlled, or unknown-sensitive material is required, standard GoalFlow stops at the boundary. Work proceeds only through a client-hosted review, a sanitized non-CUI export, or a separate approved restricted enclave.
Standard path
Use the standard request form for commercial, non-sensitive, or approved standard-handling documents.
Restricted path
GoalFlow tracks only safe coordination status. If New Avenues must take file custody, the request is out of scope here.
How we handle it
Standard GoalFlow cannot process restricted files. The request form exists to route the request into one of the allowed outcomes before anyone sends files.
01
New Avenues reviews inside the client approved system or screen share. No downloads, uploads, copies, or pasted excerpts.
02
The client prepares a clean package with restricted content removed. Only that non-CUI export can enter standard GoalFlow.
03
If the work requires New Avenues to possess restricted files, standard GoalFlow stops until a separate approved enclave exists.
What not to send
Standard GoalFlow blocks restricted files before storage where declared or detected.
Automation, queues, package generation, and AI are not used on restricted source files in standard GoalFlow.
If client-hosted review or sanitized export is not available, the request does not proceed in this workflow.
Safe first step
