A gap analysis lays the current state beside the future state and asks, for each capability: is there a gap, and what closes it?
A simple table works: capability, current state, future state, gap (yes or no) and action. Actions fall into a few kinds: build or change a system, change the process, train people, change a policy, or acquire something (data, a tool, a skill). Some rows will show no gap: say so, it matters as much as the gaps.
Gaps can be about technology, process, people or data. A capability can have more than one: approvals in the system need a build and training.
The gap table feeds the requirements (each gap needs something specified), the plan (each action has an owner) and the business case (each action has a cost).