Project & Regulatory Discovery

The situation

Organizations usually know what they want to accomplish long before they know what compliance questions the work creates. A partnership is forming, a team is being staffed, a demonstration is being planned, and the regulatory picture is still undefined. You should not have to diagnose the regime before asking for help.

Why it matters

Working the regulatory analysis during project planning preserves options. Collaborations can still be structured, access managed, information systems designed, staffing planned, technical boundaries drawn, authorizations pursued, workflows adjusted, decisions documented, and the right specialists involved. The same considerations discovered later usually arrive as constraints instead of choices.

What we do

• Start with the objective: what you are trying to accomplish, who is involved, what may be exchanged, and where the work will occur.
• Map the touchpoints: technology and information, access, countries, organizations, technical assistance, equipment movement, and information systems.
• Map which regulatory regimes may be implicated, including DOE Part 810, the EAR, NRC Part 110, and information-security expectations.
• Analyze how the applicable requirements interact and what each one demands of the project, and define which internal functions and outside specialists need to participate.
• Deliver a regulatory issue map, a preliminary applicability assessment, compliance workstreams, decision points, risk areas, and a sequenced plan for authorizations, controls, and documentation.
• Continue into the work that follows — authorization strategy, controls, and program build-out — or say plainly when a matter belongs with counsel or another specialist, and coordinate with them.