The steps on this page are organized in six sections and are intended to help you create a first draft of your Departmental Broadening Participation in Computing (BPC) Plan. The sequence and content of steps is based upon past Departmental BPC Plan workshops, but there are certainly other paths to create a Departmental BPC Plan.
You can request to meet with a BPCnet Consultant at any time. BPCnet consultants can offer insight into BPC planning, formatting your plan, developing goals, and offering advice on implementing a specific BPC activity. This service is paid for by CRA, making it free to you!
This page has many sections. They are individually small and can be usefully read in sequence, or you can jump to the sections of interest to you.
In this section you will review your local context and the requirements for Departmental BPC Plans. You will not start drafting your plan until Step 7 in the Starting Section.
Your Departmental BPC Plan will help you make your context more inclusive and equitable and ultimately broadening participation in computing. Before beginning, it is useful to understand the breadth of participation you currently have.
BPC is a specific part of the larger work of Diversity, Equity, and inclusion (DEI). Your institution likely has many resources and allies in the DEI space that can help you in your BPC efforts.
It is not necessary to be an expert in BPC to write a good BPC plan or to contribute meaningfully to BPC, but it is helpful to understand what BPC is. NSF has other initiatives, such as broader impacts, that can also have some overlap with BPC but there are some distinct differences.
Plans must have the following required content: required header information, Context, Goals, Activities, Measurement. However, they vary in the space they allocate to each of these. Some plans nest the relevant activities under their related goal. Other plans separate the goals and activities and indicate which goals each activity aligns with.
There are three sets of checklist requirements: “Document Structure Checklist”, “Tone and Clarity Checklist”, and “Departmental BPC Plan Content Checklist”. Departmental BPC Plans must be verified by BPCnet consultants using these checklists before they can be used in Connected Project BPC Plans. The checklists have evolved over time, so not all previously verified plans may fit all of the current criteria.
The words that are used to describe certain identities change across time and are often contested. Terminology is important because the words we use can hurt or help, exclude or welcome. Some terms reinforce stereotypes and disadvantages, invisibility, and dehumanization. New terms are created to resist this dehumanization, fight invisibility, and highlight realities as a means to challenge and dismantle disadvantage. Most plans need to refer to the communities they aim to support; you’ll revisit how to do this in step 18 after you write your goals.
In this section you will write a specific kind of goal and matching activity. This should help get you started; you will add other goals and activities later on. The objective here is for you to better understand the pairing of goals and activities, while constructing a goal that we feel could be used in any Departmental BPC Plan.
The template ensures you use font and spacing that satisfies the NSF formatting rules, a header that satisfies BPCnet.org rules, and an outline of sections to help scaffold your writing.
While they are referred to as “Departmental” BPC Plans, these can be written at any organizational level within an institution and there can be multiple plans within an institution. For example, you could have a plan for the whole institution, a college, a school, a department, a center, or a specific research group.
Departmental BPC Plan goals are narrower in their definition than you might be used to. To get started, we recommend writing a goal related to faculty engagement first because it is a goal that every Departmental BPC Plan could include. The Four Common Goal Patterns section in the BPC Plan Goals page provides example templates for goals. Goals are required to be specific and time bounded. We have customized two of these templates to focus on faculty engagement. If you already know the proportion of faculty engaged in BPC activities you can use Version 1. If not, use Version 2.
As noted in the Four Common Goal Patterns section in the BPC Plan Goals page, for ongoing activities, “by [YEAR]” may be replaced with a frequency such as “every year.”
BPC plans and activities do not need to be novel. There is a list of 60+ example activities at Example Activities to Use in BPC Plans that can be included in any BPC plan. Many plan writers find that it is helpful to customize these existing activity descriptions to align with their current and proposed activities. Many of the example activities include links with more information. You will eventually need to remove the links that are provided (to adhere to the NSF formatting rules), but we encourage you to read the additional information before removing.
In this section you will compile a set of goals and activities for your Departmental BPC Plan. This section focuses on how to write goals and activities, but not on the specific goals and activities to pick; those should be selected based on your context and the interests and abilities of your faculty. We encourage you to not worry about the 2-page page limit yet. At this stage you will likely have more goals and activities than will fit in your two page Departmental BPC Plan.
In the next steps, you will focus on what activities will be included in your plan. Pause here and make notes about what other goals you hope to achieve. Goals come in many flavors; read the Common Goal Topics section in the BPC Plan Goals page, for several common topics.
You may have members of your department who are engaged in BPC activities already.
Most plans will include new activities as well as current ones. Pick activities that will help achieve your goals and that take advantage of your local context as noted in Steps 1 and 2.
In the process of drafting a Departmental BPC Plan, it is common to have activities that are not aligned with any goals and goals that have no supporting activities. However, this alignment is required by the Checklist for Departmental BPC Plans.
SMART goals are required for plans to be verified on BPCnet.org and subsequently submitted to the NSF as part of a Connected Project BPC Plan. See SMART Goal Requirement section in the BPC Plan Goals page, for a brief definition of SMART goals.
Common ways to phrase SMART goals is to use one of the four goal patterns noted in the Four Common Goal Patterns section of the BPC Plan Goals page.
One item in the Checklist for Departmental BPC Plans is “Identifies how outcomes will be measured for each activity” with this addendum: “Some intended outcomes may be difficult to measure; in such cases, it is sufficient to measure an intermediate outcome. For example, it is sufficient to measure the number of students who receive funding to attend a diversity conference instead of the long-term impact of their attendance.” Many plans include collecting measurement data as a BPC activity in itself.
In this section you will draft your Context section. You have a lot of flexibility in what you include here and the steps guide you to providing typical content. You can review Verified Departmental BPC Plans for other examples.
The context section helps plan readers understand the size and general demographics of the department. Some plan writers like to add additional information about the college or institution or brief summaries of past BPC successes, which is welcome but not required.
The Checklist for Departmental BPC Plans requires that communities be identified with terms from NSF CISE’s definition of BPC, but many plans mention those terms only once to define another term to use in the rest of the plan. There is no single recommended term for referring to such groups of communities. See the Terminology Guide: Referring to Communities Underrepresented in Computing in BPC Plans for additional information.
Demographic information about your students may be found in your institutional data reporting system or at https://bpcnet.org/research-data/ under Postsecondary Computing Degrees Awarded (IPEDS). Some goals might also benefit from demographic information of a broader context than the department itself, such as university, state or regional demographics, or you can use the K-12 data available from https://bpcnet.org/research-data/ under K-12 Enrollment (CCD).
In this section you will prepare for your plan to be Verified by BPCnet. The steps below guide you to revisions that will eventually be required for verification.
Since Departmental BPC Plans can be submitted to the NSF as part of Connected Project BPC Plans, it is required that Departmental BPC Plans also meet the NSF formatting rules, which prohibits the inclusion of links.
Since Verified Departmental BPC Plans can be used in Connected Project BPC Plans submitted to the NSF (see Connected Project BPC Plan ), it is necessary to have an identifier by which PIs can refer to each activity. This is also required in the Checklist for Departmental BPC Plans.
The Checklist for Departmental BPC Plans includes a requirement to identify “a contact person for each activity”. Many plans do this by providing the name of an individual (or a role such as “Director of Graduate Studies”) in parentheses at the end of each activity. Some plans include a sentence explaining that the contact for the Department BPC Plan is also the contact for all activities. The contact person should be available to help new people join the activity and answer questions about it.
There are many aspects of a Departmental BPC Plan and it is easy to overlook some things while working on others. A pass to look for things that often get overlooked can improve the quality of your plan. BPC consultants will also help ensure that you meet all of the requirements.
The Checklist for Departmental BPC Plans is used by BPCnet consultants as the criteria for if a plan is ready to be verified and published on BPCnet.org. Reviewing each item in the checklist before submitting it can help the verification process go more smoothly.
In this section you will finalize a draft of your plan and submit it to BPCnet for verification.
Because Departmental BPC Plans may appear on BPCnet.org and in NSF grant proposals, there may be institutional policies about what they can include and who has to approve them before they are published. This may require input from administration and legal counsel within the institution.
Internal feedback and approval are important to ensure buy-in from faculty and others who will be performing the plan’s activities. It is common that most faculty, staff, and students are unaware of many of the BPC activities within a department. Sharing a draft of the plan for feedback can be an additional way to provide transparency about the ongoing BPC activities. You may find it helpful to label activities with (new) or (ongoing) to clearly communicate with internal stakeholders; such labels are not needed on the submitted plan.
You will receive confirmation that your plan has been received, after which it will be routed to a BCPnet.org consultant to review and verify, using the Checklist for Departmental BPC Plans and the consultants’ expertise. Typically, it will be returned with some suggested revisions before being verified and published on BPCnet.org. After your Departmental BPC Plan is Verified, BPCnet will not post your plan online without your confirmation. This means that you can seek final approval from your unit after your plan is Verified. Additional changes can likely be Verified quickly.
BPCnet.org has compiled a series of videos that explain different aspects of a Departmental BPC Plan. The videos go into detail about types of BPC Plans and their activities, context, goals, evaluation, and measurement.