Project Proposal

Once you receive a device, we require that you submit a proposal and wait for iFixit’s approval. It will save you time in the long run if you carefully read the instructions below.

A proposal outlines what your project will look like from start to finish. We have a sample proposal to help you get an idea of what yours should look like—just bear in mind that every instructor has slightly different specifications, so make sure to cover all the required points for your class. You are more than welcome to use the sample proposal as a reference, but the content must be written in your own words.

Important things to include in your proposal:

  • The device will you be working on
    It's important to get the device name exactly correct, which can be tricky because some devices have crazy names like the SuperSonic Matrix Mid SC-999. (Try saying that five times fast!) If your device was provided by iFixit, use the full name listed on the white iFixit label affixed to the device. Devices can have multiple labels, so be sure you are looking at the one with the correct name. To find the correct label, look at the pictures below. If you've decided to use your own device, take the time to research the full device name. Your best bet will be to search the manufacturer's product page. If you're still unsure of your device's correct name, ask us!

Keep in mind,  on the label in the bottom left, the “N:” is  not  a part of your device name. Some device names are a bit long, so keep an eye out for text that runs onto the second line of the label.

Keep in mind, on the label in the bottom left, the “N:” is not a part of your device name. Some device names are a bit long, so keep an eye out for text that runs onto the second line of the label.

  • The URL of the existing device page
    There should be a device page on iFixit already, so take some time and search for your full device name. Once you think you've found it, use the identification information in the "Background and Identification" section (if applicable) to confirm that it's the correct page—this is where all of your guides will link to. Please include a link to your device page in the proposal.

  • A list of existing guides found on the device page
    To make sure your group doesn’t create any duplicate content, it’s important for you to include a list of any existing guides for your device.

  • The specific guides you will write for your device
    As mentioned before, each guide should show how to replace a specific component of your device (battery, display, motherboard, etc.). We ask that you focus on replacement guides because often all it takes to fix a device is the replacement of a single, faulty component. Additionally, some components such as RAM and hard drives in laptops can be simply upgraded to keep devices working longer. To have the biggest impact—and help keep the greatest possible number of devices out of landfills—choose the components that are most likely to fail, break, or require an upgrade.

    • Do not create a Teardown, Disassembly, or Technique guide.

    • You are not responsible for repairing a broken device or broken components. You are simply demonstrating how to replace the components.

    • List all the guides you intend to create, making sure you have enough to meet your class requirements.

    • Later, you may run into new parts to write guides for, or discover that a guide you had planned to do isn't possible, and that’s okay—just email us to make sure your proposed changes are suitable.

  • The intended audience for your project
    Audience analysis is an important part of technical writing. Take a look at and get familiar with the demographics of the users on the site—the Answers forum is a good place to start. Remember, the overall goal of the project is to help as many people as possible repair their things so that they don’t get thrown away. In order to best help someone, you need to know who you’re talking to. Take a look at our mission. Who are we trying to help? How will this inform your project?

  • Links to each team member’s profile page
    We suggest linking to each member’s profile page in the signature portion of your proposal. (See sample proposal for example.)

  • The camera you will be using
    Any digital camera of 6 megapixels or greater that can mount to a tripod is acceptable. Your instructor will tell you if you are allowed to use a smartphone camera to take your photos. However, even if smartphone cameras are allowed, we recommend using a digital camera. Digital cameras have manual settings that can be adjusted according to your specific lighting situation. Plus, we have handy tips for operating your camera!

Please include a header at the top of your proposal in this format:

  • Device: Samsung Galaxy S5

  • Team tag: CPSU-DOE-F18S4G7

  • Camera: Nancy's 16.1 MP Canon PowerShot SX700

  • Group email addresses:, etc. (These must be the same email addresses that you and your team members used to create your iFixit accounts.)

Don't forget: include your team tag in the subject line of your email, CC your teammates and instructor, and include a brief message in the email's body to provide context for your proposal. Keep in mind, it can take up to two business days for the iFixit technical writing team to respond to your email.


Feeling Lucky?

Don’t leave your grade to chance. Be sure to review the Unit 1 instructions and checklist to make sure your dots are in a row. When you’re ready, email your proposal to techwriting[at]ifixit[dot]com, and we’ll let you know when you’re ready to move on to Unit 2.