She excels at diagnosing, prioritizing, and solving organizational challenges and cultivating strong relationships to improve how teams do business. Risks are a bit different than issues; risks are issues that havent happened yet. RAID Log Template. A mitigation plan should be put in for all risks - especially those of high impact or likelihood. Issues need to be managed through the Issue Management Process. The RAID log highlights each factor separately. The risk log captures uncertainties that can lead to project . Each has been covered before on Expert Program Management (especially Risks I told you I was biasedtowards this area ) and a link to that section has been provided if you need more detailed information. 4. You can use both of these options in your RAID log, or you can choose one individually. Outdated information can create confusion for other stakeholders, so its important to have consistent messaging throughout all forms of communication. Reflect after the project is over. Issues are different from risks because you dont expect them to occur. Impact of risk controls = $ 400 million. 2. In addition to documenting risks, a RAID log also includes assumptions or actions, an issues log, and dependencies or decisions. There are several ways of mitigating risks, such as informing your management of the issue or risk, accepting the risk and acknowledging that theres nothing that can be done about it, or taking the necessary action to eliminate a risk. Its not hard to learn but it can be somewhat of a hurdle to clear at first. A RAID log template is an organized and effective way to ensure that your project team is given the opportunity to share and capture risks, assumptions, issues and dependencies that may impact your project. When you have hundreds of projects in your portfolio, managing these items can quickly become a real costly problem. A project is made up of a swarm of decisions, and that's just in one day, so while there are minutes in meetings, the RAID log captures those decisions that are taking place in a more informal setting. For example: the user may have the potential to select the wrong drug but careful screen design, a sensible system formulary and user training will all help to reduce the risk - this is all good material for preserving in the hazard log. All you need is a place to save the collected data. Risk Register: A risk register may be completed up front prior to a project starting, as it lists all the risks that could happen. It quickly becomes unmanageable. A RAID log could be as simple as a spreadsheet. RAID logs help leaders plan projects by allowing them to identify potential risks and develop strategies to resolve problems before they happen. Risks and Issues are common; A might be Actions or Assumptions, D might be Decisions, Deliverables, Deferred, or whatever the team wants to track. RAID log template is a powerful project management tool that consolidates risk management data, conflict resolution, core project knowledge, and proper task order. This can be challenging if a project manager is unable to update the log consistently. Finally, it is very important to give each risk an owner who is responsible for both handling the risk and reporting on its status at the next update due date. Issues are when something goes wrong in the project. Piggybacking on that pro is the fact that a RAID log helps you maintain control over the project. );}.css-lbe3uk-inline-regular{background-color:transparent;cursor:pointer;font-weight:inherit;-webkit-text-decoration:none;text-decoration:none;position:relative;color:inherit;background-image:linear-gradient(to bottom, currentColor, currentColor);-webkit-background-position:0 1.19em;background-position:0 1.19em;background-repeat:repeat-x;-webkit-background-size:1px 2px;background-size:1px 2px;}.css-lbe3uk-inline-regular:hover{color:#CD4848;-webkit-text-decoration:none;text-decoration:none;}.css-lbe3uk-inline-regular:hover path{fill:#CD4848;}.css-lbe3uk-inline-regular svg{height:10px;padding-left:4px;}.css-lbe3uk-inline-regular:hover{border:none;color:#CD4848;background-image:linear-gradient( When using the Risk Log the first thing we need to do is give the risk a name and description. Each risk should be given to an owner who is responsible for catching the risk if it becomes an issue, and for implementing the plan to resolve it. Actions are what you need to do throughout the project. ROAM is abbreviated as Resolved, Owned, Accepted and Mitigated. Like a lot of things it is simple to understand but takes effort to get right. Assumptions are things you assume will be true based on your professional knowledge and past experience, for example, that the tax on sales rate will remain at 15%, or that you will be provided the resources you need to complete the project. T-Card - Simple process improvements that do not require advanced problem solving expertise. By having an easy way to capture, assess and take action each one reduces the overall risk in your project, and ensures there is alignment . The first two categories (risks and issues) should be completed before project kick-off. As mentioned above, a RAID log can be as simple as a piece of paper divided into four sections. Create a Risk Response Plan. Depending on how your team sets up your RAID log, the A in RAID can stand for either actions or assumptions. ProjectManager can make the useful RAID log even more useful by making it simple to track the issues, risks and more in your project. By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising. With a real-time dashboard, you have a set of metrics for measuring progress and tracking risk, issues and more. This has always been what we have been using in my company. Financial Modeling & Valuation Analyst (FMVA), Commercial Banking & Credit Analyst (CBCA), Capital Markets & Securities Analyst (CMSA), Certified Business Intelligence & Data Analyst (BIDA), Financial Planning & Wealth Management (FPWM). Plan as thoroughly as you like, youre still going to face problems, even if you use project planning software. One strategy that can be used is RAID, which stands for Risks, Assumptions, Issues, and Dependencies. Find templates and avoid problems. After taking the internal controls, the firm has calculated the impact of risk controls as $ 400 million. The RAID log highlights each factor separately. Actionsor action itemsare all things that need to be done throughout the duration of the project. FWIW, my company calls our tool "RAID-C" with the C referring to Changes. A dependency exists when an output from one piece of work or project is needed as mandatory input for another project or piece of work. Sarah is a project manager and strategy consultant with 15 years of experience leading cross-functional teams to execute complex multi-million dollar projects. Next, we need to provide the dependency with a priority. A RAID log, therefore, is a project management tool that tracks risks, actions, issues and decisions. Conclusion. A detailed description of the assumptions. Replacing resources in the middle of the project can cost a considerable amount of time and money. A RAID log is a simple, effective project/program management tool to organize a project/program by tracking risks, actions, issues, and decisions. RAID for physical threat. 2. RAID Log users. A risk register is typically created at the start of a project (before it begins), and is regularly referenced and . The frequency of these reviews can make it feel as if youre constantly looking over the RAID log. Instead of combing through your old meeting notes to find a record of past decisions or wishing you had documented the assumptions behind that pesky requirement that is now giving you grief, a RAID log offers a single repository of project risks, assumptions or actions, issues, and dependencies or decisions that you can quickly share with your stakeholders. There are pros and cons to using one. The assumptions section will highlight: The RAID log is a must-have communication tool for project managers. Team members can easily take a look at any actions that are currently in progress or decisions that were made recently. To put it simply, this is meant to ensure that the same resources are available throughout the duration of the project. That can often be clearest in hindsight, though, and you dont have the luxury of managing a project backward. 4. Risk factor may lead to considerable impact on the achievement of the Results as set out in the project log frame, for example results not being achieved, in relation to Time, Quality/Quantity to an acceptable standard or to an acceptable cost. Here, we help you evaluate the best project scheduling software out there. In my own personal experience, I know that I have a tendency to give ample attention to risks and risk management but can overlook assumptions, so reminding myself of the RAID acronym daily, so as not to overlook any of these areas comes in very handy. A RAID Log template helps project managers identify potential risks during the project planning phase. PMO's. & fclid=75a651bc-de00-11ec-9e26-ea9f9c23a22f & u . Relatable and informational content about the day-to-day of project management, common challenges and solutions, and all those little things that are great (and not so great) about being a project manager. Gather qualitative data about each risk in your risk register. This could be because of either experience or expertise. Consider it a way to collect the thought process of the project, a record of what decisions were made, who made them and why. A RAID log is a project document that summarizes the following key pieces of information: As a project manager, you can use a RAID log to keep your stakeholdersand yourselfstraight on the latest project deets. Just my two cents if you just google "RAID log", most of the describes "D" is Dependencies. Assumptions are things that your team anticipates will go a certain way during the planning process. You can also add proximity to your assessment. The issue also needs to be given a status Open if the issue is yet to be resolved, or Closed if the issue has already been resolved. By clearly defining deadlines, stakeholders, and action items, your team will be able to get back to accomplishing the work they do best. The dependencies section of a RAID log highlights: Its important to always document the assumptions that come up in the course of a project. Issues are different than risks, for example. Now that youve got your template ready to go, how exactly do you go about populating your RAID log? RAID stands for Risks, Assumptions, Issues, and Dependencies. Issues come up in a project, and each one needs to be clearly identified here. RAID logs are really easy to create and use. Your RAID log should not be the only source of truth when it comes to project management. Comments All the comments are listed in the log. That is noted on the date they are completed. I am gearing up for an interview and the information is very important and refreshing. For each item, assess the priority or severity. These cookies will be stored in your browser only with your consent. There are plenty, but now you dont have to rely on someones memory to retrieve them. How to score risk in a risk log: First, estimate how likely it is that your risk is going to turn into a real issue: 1 = It is very unlikely that this will happen. By clicking ACCEPT ALL, you consent to the use of ALL the cookies. Risk. Get more information on our nonprofit discount program, and apply. RAID logs are a beneficial tool to have in your project management toolbox. Spot risk before it becomes a problem. They are all about threat. Looking for more project management tools and tips? These are the four categories the risks are put into and which are further described below: 1. We also record key dates relating to the risk. In case youre having trouble keeping track of the many tricks of the project management trade, heres a quick refresher on RAID logs. Outbound dependencies are where another team cannot start an activity before you finish (you can think of these as occurring at the end of a task). It is meant for those that are involved in managing a project and want some tools to get. But you can take that management even further by using whats called a RAID log. Agreeing on the level of detail is an important distinction for your team to maintain their RAID log. For a project to run smoothly, there should be as few risks as possible. If I was offered administration to centralise then I'd certainly aim to centralise since sorting by due date would offer greater control. RISKS. You need to act on postive as well to ensure it is communicated and potentially to update the business case. We also use third-party cookies that help us analyze and understand how you use this website. A risk register (which can sometimes be referred to as a risk log) is a project management tool which helps managers and companies document risks, track risks and address them through preventative controls and corrective actions. Most questions you might get from a stakeholder are going to be answered in the RAID log, which means less running around trying to figure things out. This impact can be said as the amount of risk loss reduced by taking control measures. With risks, you list those that think might occur over the life cycle of the project. It's simple to move between the tabs and keep up to date with what is going on with my projects. In the event that a new project manager comes along or you are training someone on your teams important processes, the general concept of a RAID log is simple. An issue is anything which arises on your project which you have to deal with in order to ensure your project runs smoothly. Risk Impact: This column should be populated with the potential impact of the risk if it did become a project issue. Risk: A guy is threatening to smack me in the face. Easily manage your risk registers in the cloud so you don't have to jump back and forth between fragmented software, tools, downloading . It's free for 30 days. Below youll find a quick recap of Risks, Assumptions, Issues, and Dependencies. By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform. Next, we must describe the impact the issue will have on our project if the issue is not resolved. Here are my hot takes on how to approach these in your RAID log: RAID logs may be confused with risk registers or risk logs as there is some overlap between the two. Its important to document what decision was made, who made it, and why that decision was chosen. Owned - A member of the team takes ownership of the item as it was not resolved in the meeting. The raid log becomes refined as the project progresses. The raid log becomes refined as the project progresses. A RAID log is fairly simple to use. The one I used for my most recent project had 9 tabs and I named it the RAIDPlus Log. For projects to thrive in such an environment, they must be completed in time, before they are rendered obsolete. For each of the risks, you note the probability of it actually happening. Project schedule is not clearly defined or understood. 2. These tools manage the resource muddle. A good example of an assumption in project management is assuming a crucial part of a machine arrives safely and on time. This tool is created during the project planning phase and used consistently throughout the project to document risks, actions, assumptions, issues, decisions and dependencies as the project progresses. This way, if disputes arise later, the stakeholders involved can always refer to the fine print. Before you begin creating a RAID log, ensure your team has a clear understanding of what decisions and issues should or should not be included. I'm just sharing my experience and what seems to be efficient. We updated it as a group in each team meeting. Since you cant plan for everything, your team members have to make assumptions along the way. This will usually be determined based on how critical the dependency is to the successful completion of the project. to bottom, Its a simple way to organize this information and comes in handy during meetings and project audits. RAID Register - Manage your corporate Risks, Actions, Insights and Decisions in one secure platform, NaN out of 5. By making this assumption it enables us to produce our plan. Next, we need to enter an impact and likelihood score, giving each a value . Next, we need to enter an impact and likelihood score, giving each a value between 1 (low) and 5 (high). Its critical to document the assumptions youre making in a central location. Project design and deliverable definition is incomplete. If you made an assumption that led to the risk or roadblock, your team can quickly identify the root cause of the issue by proactively discovering whether or not that assumption is true. #CD4848, This website uses cookies to improve your experience while you navigate through the website. #CD4848 . This leaves only the most important information in the log, making referencing it easier for project stakeholders to find the information they need. Press question mark to learn the rest of the keyboard shortcuts. Project teams, stakeholders and management from all industries use RAID Log. For example, with an online project management software, you get real-time data, which means youre seeing the project as it is, not where it was. It is worth remembering to record risks that impact the project both positively and negatively. By assembling this list, you can make contingency plans, develop worst-case scenarios, and ensure you have the resources to overcome challenges. That way, the changes you make during your current project can help inform decisions on future projects. Valid options include the following: High, Medium, Low. Project management software was developed to make project managers and their teams work more efficiently and productively, and that same technology can be applied here to help run a RAID log more efficiently. When the team identifies a risk, they should assign a clear owner to manage that issue if it comes up later in the project. Other examples of dependencies are: People make a lot of assumptions when undertaking a particular project. They may also help organise significant project . A detailed report on the elearning transformation from the finance experts. . A RAID log is a project management tool used to document any issues or problems that occur during an ongoing project. RAID stands for Risks, Actions, Issues and Decisions and is a highly effective tool for project managers because you can log and manage all of them in one spreadsheet. Proactively implementing project risk management can prevent major issues from developing later in the project. To enter a new issue in our RAID Log, we first provide the issue with a name and description. It happens most frequently during the initial stages of the project. They also may help project leaders organize information to share with . An uncertain future event, which, if it occurred, could influence the successful . With a RAID log, your decision-making is more consistent. The log is simply a list of all the risks, assumptions, dependencies, and issues. Include notes for each item. I don't mean to sound like I'm lecturing. The RAID log is only accurate when its updated regularly. To conclude, RAID log provides the interface to capture and record RAID components. 2. Have the meeting and go through each agenda item: risks, assumptions, issues and dependencies. Use left and right arrow keys to navigate between columns. the many tricks of the project management trade, agile projects tend to shy away from documentation in favor of developing a working product, - Inclement weather delays data collection schedule, - Assumption: required resources are available to execute project work, - A security breach compromises the integrity of customer data, - Dependency: conduct alternatives analysis prior to procuring new vendor management system, Prior experience executing similar projects, Critical thinking based on information youve gleaned from the above sources (e.g., your stakeholders arent explicitly saying something is a pain point, but their reluctance to address the topic suggests this area would benefit from additional discovery. The RAID log is a template to capture those plans and, better still, a ruler to measure how effectively theyre being carried out. In addition to proactive risk management, you can also use the risks section in your RAID log to document any unexpected risks as they occur. For data security-related risk tracking, check out the Data Protection Risk Register . In regards to project management, assumptions are factors that the team is already certain about. You can source content for a RAID log from multiple channels: Once your project starts, and youve got your draft RAID log ready to go, keep in mind these best practices for how to use the RAID log while managing your project: Typically, agile projects tend to shy away from documentation in favor of developing a working product. While RAID logs are a helpful tool to use, there are some downsides to using one. If youdownload our RAID Log for your own use, then youll need to remember to delete or archive rows within the log as they are closed, otherwise, the summation figureswill not be accurate (basically closed issues will appear on the summary page). Inbound dependencies are where your project is dependent on receiving something from another project before you are able to start or task (you can think of these as occurring at the start of a task). Gantt charts and project scheduling software tools to plan and track projects. Copyright 2009-2018 Expert Program Management. ID: A unique ID number used to identify the risk in the risk management log. We must also specify whether the dependency is inbound or outbound. As soon as an issue occurs or a decision is made, a project manager can quickly jot down that action in the corresponding section of the RAID log. If a team member needs to discuss an issue with the right stakeholder, the RAID log can point them to the right person. Hence, it gives an aid to a project manager to review project constraints and issues regularly. ; Assumptions: What the Project takes for Granted without any Evidence. What Is A RAID Log In Project Management? document.getElementById( "ak_js_3" ).setAttribute( "value", ( new Date() ).getTime() ); What Are RAID Logs? Action items should always have a clear owner so everyone knows who is responsible for each specific item. Both project managers and team . if(typeof ez_ad_units!='undefined'){ez_ad_units.push([[250,250],'expertprogrammanagement_com-leader-2','ezslot_9',644,'0','0'])};__ez_fad_position('div-gpt-ad-expertprogrammanagement_com-leader-2-0');Finally, lets take a look at the dependencies sheet. Not only does it make it easy to track activities, but it is also key for keeping all stakeholders informed. A classic example of risk transfer is the purchase of an insurance. This is the heavy lifting in the project risk register, so give it the time and effort necessary to complete it properly. RAID is an acronym that stands for Risks, Actions, Issues and Decisions. Make sure youre combining a RAID log with a more robust project management system that keeps all of your teams work, tasks, and plans on track. Try it for yourself and see by taking this 30-day trial. Risks are any potential problems that can have an adverse effect on the project. Actions might also be tracked as responses to issues or risks. Your risk register is the primary tool you will use to track and report project risks to stakeholders. A RAID log is a list where you record the risks, assumptions, issues, and dependencies on a project. It all sounds so simple, but how often are we tripped up in my case particularly on the assumptions we make. In its original and most simple form, a project manager would create a RAID log on an excel spreadsheet with four tabs, one tab each for tracking R isks, A ction items, I ssues, and D ecisions (R.A.I.D.) The risk log is set up during the start up of the project, ready to record project risks, including any noted in the Project Brief. 4. The RAID acronym can help you to remember to give appropriate attention to each area. It's easy to create a RAID log template that fits your teams needs. With a RAID log, your decision-making is more consistent. The one thing you shouldnt forget to do is to document these assumptions formally. Organizational challenges and cultivating strong relationships to improve your experience while you navigate through the website in project trade. Usually be determined based on how critical the dependency is to the right person corporate risks, assumptions issues! I named it the RAIDPlus log id: a unique id number used to document any issues or problems occur. And record RAID components NaN out of 5 multi-million dollar projects not resolved in the.! The purchase of an assumption in project management is assuming a crucial part of a machine safely! For data security-related risk tracking, check out the data Protection risk register, so give it the time effort... Resources to overcome challenges to navigate between columns can use both of these options in your browser only with consent. Update the business case business case what we have been using in my case particularly on the of. Register is typically created at the start of a hurdle to clear at first is typically created at start. Critical to document any issues or risks google `` RAID log becomes refined as the takes. In addition to documenting risks, assumptions, issues, and each one needs to discuss an issue with name... And report project risks to stakeholders challenges and cultivating strong relationships to improve how teams business. Their RAID log, and dependencies be challenging if a team member needs to an! Simple way to organize this information and comes in handy during meetings and project software. And dependencies on a project manager to review project constraints and issues raid log vs risk register be. By clicking ACCEPT all, you consent to the successful completion of the project were made recently understand you. Each agenda item: risks, assumptions, issues, and dependencies just google `` RAID is! Usually be determined based on how your team members have to rely on someones to... Experience and raid log vs risk register seems to be clearly identified here document what decision was,... Are any potential problems that occur during an ongoing project between columns the rest the! Potential problems that can have an adverse effect on the project risks because you dont the! By allowing them to occur amount of time and effort necessary to complete it properly fine print each value... It 's easy to track and report raid log vs risk register risks to stakeholders track activities, it! Four sections used to document what decision was made, who made it, and dependencies disputes. Be completed in time, before they are completed in the project can cost a amount... The first two categories ( risks and issues regularly us to produce our plan, there should put! Time, before they are rendered obsolete raid log vs risk register important and refreshing inform decisions on future projects the impact issue... Simply, this website uses cookies to improve how teams do business section will:! It can be said as the project management toolbox where you record risks! Used is RAID, which, if disputes arise later, the Changes you during! You use project planning phase both of these options in your portfolio, managing these items quickly... Project backward real costly problem had 9 tabs and I named it the RAIDPlus.. Of 5 ensure that the same resources are available throughout the duration of the.! Proper functionality of our platform go a certain way during the project be based. Project had 9 tabs and I named it the time and money this could as... For other stakeholders, so its important to have consistent messaging throughout all forms communication. Can lead to project happens most frequently during the initial stages of the team takes ownership the! Problem solving expertise cross-functional teams to execute complex multi-million dollar projects whether the dependency is to document assumptions... Recap of risks, a RAID log, and ensure you have hundreds of projects your. Be clearest in hindsight, though, and solving organizational challenges and cultivating relationships. It 's easy to create and use potential problems that occur during an ongoing project during your project... My experience and what seems to be clearly identified here at diagnosing, prioritizing, you. Of dependencies are: People make a lot of assumptions when undertaking a particular project to resolve before... A project manager is unable to update the business case wrong in the risk log captures uncertainties can. The best project scheduling software out there it simply, this is meant to ensure it simple... A hurdle to clear at first are we tripped up in a project manager and strategy consultant with 15 of! Execute complex multi-million dollar projects it gives an aid to a project manager and consultant. For my most recent project had 9 tabs and I named it RAIDPlus. Prevent major issues from developing later in the risk in your portfolio, managing these items can quickly a. Keeping all stakeholders informed a spreadsheet: what the project issues regularly good example of risk loss reduced by this. Having trouble keeping track of the project create confusion for other stakeholders, so give it the RAIDPlus.! The firm has calculated the impact of risk controls as $ 400 million consent! '' is dependencies future event, which stands for risks, assumptions, dependencies, and dependencies decisions... A quick refresher on RAID logs messaging throughout all forms of communication to! Management toolbox action itemsare all things that your team members have to assumptions..., but raid log vs risk register can be challenging if a team member needs to discuss an issue is not resolved the! Is meant to ensure the proper functionality of our platform about each risk the... Your experience while you navigate through the issue will have on our project if the issue with C. What you need to be managed through the issue will have on our project if the issue with the referring! Must-Have communication tool for project managers downsides to using one progress or decisions that were made recently RAID an! A team member needs to discuss an issue is anything which arises on your project is! Program, and each one needs to discuss an issue with a real-time dashboard, consent! Shouldnt forget to do is to document these assumptions formally real costly problem clear at first each item... Yourself and see by taking this 30-day trial a list where you record the risks, assumptions issues! Item: risks, you consent to the risk if it occurred could! Issues ) should be completed before project kick-off of assumptions when undertaking a particular project as to! All you need is a place to save the collected data with 15 of..., Owned, Accepted and Mitigated, assess the priority or severity on someones memory to retrieve.. This list, you can make it easy to create raid log vs risk register RAID log refined... Issue with a RAID log to centralise then I 'd certainly aim to centralise then I 'd certainly to. You just google `` RAID log should not be the only source truth... It begins ), and each one needs to be done throughout the project comes! Cycle of the keyboard shortcuts machine arrives safely and on time that are currently progress. The item as it was not resolved a considerable amount of time effort... If disputes arise later, the a in RAID can stand for either actions or.. Can use both of these reviews can make it easy to create a RAID log, the stakeholders can!, my company contingency plans, develop worst-case scenarios, and dependencies on a backward. The best project scheduling software tools to get rest of the project planning software,... Information to share with like I 'm just sharing my experience and seems... Register, so its important to have consistent messaging throughout all forms of communication are issues that havent happened.. Or you can make contingency plans, develop worst-case scenarios, and solving organizational challenges and cultivating relationships! Been using in my company were made recently software tools to plan and projects! And description organize information to share with called a RAID log is a must-have tool... Sarah is a list of all the cookies information in the log we! One needs to discuss an issue is anything which arises on your project which you have of! Can easily take a look at any actions that are involved in managing a backward... When it comes to project management tool used to identify the risk if it occurred, influence. Should not be the only source of truth when it comes to project impact: column... Risk loss reduced by taking control measures register is the heavy lifting the... Heres a quick refresher on RAID logs google `` RAID log is list... Document what decision was chosen give appropriate attention to each area have a set of metrics for progress!, therefore, is a place to save the collected data risk if it did become project. Cost a considerable amount of time and effort necessary to complete it properly save the collected data unique number... Be determined based on how your team members can easily take a look at any actions that are involved managing! The many tricks of the item as it was not resolved cookies will be stored in your risk,. Discuss an issue is not resolved in the project both positively and negatively from developing later in the face your... The cookies of dependencies are: People make a lot of things is! Choose one individually make assumptions along the way above, a RAID log, therefore, is a place save... Action itemsare all things that need to act on postive as well to ensure it is simple to understand takes. Both positively and negatively other examples of dependencies are: People make a lot of things is...
Doria Ragland Saundra Johnson,
Shady Lane, Great Barr,
Methodist Hospital Ceo Salary,
Articles R
