Restricted support

Support for CUI/CDI without file custody.

Standard GoalFlow does not store restricted files. When CUI, CDI, ITAR, export-controlled, or unknown-sensitive material may be involved, files stay in the client approved system.

Standard lane

Upload non-CUI files.

Use normal intake for commercial, non-sensitive, or approved standard-handling documents.

Restricted lane

Keep controlled files with the client.

GoalFlow tracks coordination, status, owners, and next actions while source files stay with the client.

How we handle it

Restricted Handling Advisory Add-On.

This is a service lane, not automated CUI hosting. It adds setup, review, coordination, and evidence work for cases where controlled material may exist.

01

Open the request

Tell us the case may involve restricted material. Do not upload files into standard GoalFlow.

02

Confirm the client system

We document the approved client workspace, access method, human owner, and delivery path.

03

Coordinate without custody

GoalFlow stores non-sensitive workflow status, tasks, and review notes. Restricted files stay with the client.

What not to send

Do not upload restricted files here.

No CUI/CDI storage

Standard GoalFlow blocks restricted files before storage where declared or detected.

No restricted email intake

Email should not be used for controlled files. Use the client approved system instead.

No AI on restricted work

AI is not used for CUI/CDI handling unless a separate approved environment exists.

Safe first step

Open the request. Keep controlled files out.

Start intake