Intel Service
Engagement path
How an application audit of a budget planning packet moves from first message to findings memo.
An engagement at Intel Service is built around the packet you must submit. The steps below describe a typical full application audit; shorter checks compress the middle stages.
Path
Request and materials
You write with deadline, approximate page count, and whether the packet is bilingual. We confirm confidentiality and ask for the draft application, ceiling memo, and prior-year schedule if available.
Fee note and window
You receive a fixed-fee note and a reserved review window. Work begins when the deposit clears and the draft packet is marked complete enough to read.
Reading and cross-checks
We read forms, schedules, and justifications together. Issues are logged with page references — missing annexes, figure mismatches, and narrative gaps that invite panel questions.
Findings memo
You receive a ranked findings memo. A clarification call is included so the submitting officer can decide which edits to own before circulation.
Optional panel prep
If you will speak to the application in committee, a separate briefing can follow using the final packet.
What you should send early
Incomplete packets create false urgency later. Send signature status, annex lists, and known weak lines in the first message when you can.
Begin
Browse audit types or request a review with your fiscal cycle and deadline.