Engagement process
How an Intel Studio application audit of a compliance reporting application actually runs.
Audits fail when access arrives late or when findings surprise owners who never saw the working papers. This page sets the rhythm we keep so your filing calendar stays intact.
1. Brief and conflicts check
You describe the application, filings, and timing. We confirm we are not conflicted with implementers on the same system and propose a discovery call.
2. Discovery and proposal
A short call clarifies pack count, entities, and access. You receive a written proposal with fee, deposit, and fieldwork window keyed to your filing date.
3. Access and kickoff
Accounts, document stores, and owner introductions are confirmed before the clock on fieldwork starts. Kickoff names the coordination contact and escalation path.
4. Fieldwork
Walkthroughs, sampling, and evidence tests proceed against the agreed packs. Emerging issues are raised early — not saved for a dramatic close.
5. Challenge draft
You review draft findings for factual accuracy. Tone and severity stay with us; facts can be corrected.
6. Memorandum and next actions
The final memorandum and prioritized remediation list are delivered. If you want verification later, we schedule it as a separate engagement.
What we need from you
A coordination contact with authority to unlock access, a realistic filing date, and candour about workarounds already in use. Hidden bridges discovered mid-audit force a re-scope conversation.
Natural next step
Browse the audit offerings or send a brief with your next filing window.