When performing BIAs, several best practices can be used. Following is a list of some of them:

• Starting with clear objectives—Everyone involved with the BIA must understand its scope, which is best defined in writing. Many projects get off track simply because individuals have varying understandings of the requirements.
• Not losing sight of the objectives—The purpose of the BIA is to identify the critical functions, critical systems, and MAO. This data is used to determine the recovery priorities.
• Using a top-down approach—Starting with the CBFs and drilling down to the IT services that support them is the top-down approach, whereas by starting with the servers, important elements that are needed for the success of the CBFs will be missed.
• Varying data collection methods—When collecting data, the method used must be matched with the organization’s practices. Solid data may be obtainable from individual interviews with some people, but access to other people for individual interviews may not be available. In this case, questionnaires can be used. Group discussions are often useful when collecting BIA data, and such discussions can be coordinated in conference calls, meetings, and workshops.
• Planning interviews and meetings in advance—Data gathering is an important part of the BIA, so ensuring that the attendees have enough time to provide the data needed is important. If they’re rushed or aren’t prepared, the data that’s needed may not be provided.
• Not looking for the quick solution—The BIA is time consuming especially in data collection, evaluation and the identification of priorities. Shortcuts are likely to overlook critical functions or processes.
• Considering the BIA as a project—All normal project management practices apply. Milestones should be set and progress tracked.
• Considering using tools—Many tools are available that can assist with the completion of disaster preparedness projects that can also help with developing a BIA.