Project Proposal

Once you receive a device (or choose your own), 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 you will 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!

• Repair information already on the internet about your device
  Are there disassembly instructions available? If so, how good are they, and how are yours going to be better?
  

• The specific topics you will address on your troubleshooting pages
  Choose 1-3 symptoms that users might experience with their malfunctioning device. Each symptom will be the topic for a troubleshooting page. (Check with your instructor for the exact number of troubleshooting pages required for your class). Whenever possible, choose symptoms related to known problems with your particular device model rather than general problems common to all devices. Phrase topics as user-observed symptoms. For example, “Device won’t power on,” “Audio is distorted,” “Screen is unresponsive,” etc. When phrasing your topics, think about what a user may see, hear, or experience. This helps readers quickly find the repair information they need without having to already know the underlying cause.
  

• Proposed page titles
  When you create your troubleshooting pages and device page on the iFixit site, you'll be prompted to create page titles. It is important for page titles to be written correctly the first time around so that an accurate URL is created. We try to keep page titles consistent across the site, so the titles for your pages should follow this format:

  • Troubleshooting Page Titles: [Device Name] [Specific User-Observed Symptom]

    • Example: Lenovo Essential G560 Does Not Power On

  • Device Page Title: [Device Name]

    • Example: Lenovo Essential G560

    • Please note: The word "Repair" will auto-populate on the device page title after you've created the page.
      

• The specific guides you will write for your device
  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, replacing one problematic component can revive a non-functioning device. Many repairs require advanced techniques (such as board-level fixes), so by creating replacement guides, you’re helping more people fix their stuff! To 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.

  • Most student groups write guides for 5-7 components, but the number varies. Check with your instructor for the required number.

  • If you’re not sure which guides to write, check out the Student FAQ for some ideas. 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 iFixit.com 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 an example.)
  

• The camera you will be using
  Any digital camera of 6 megapixels or greater that can mount to a tripod is acceptable. Please note, this rules out most smartphones.

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

• Device: Samsung Galaxy S5

• Team tag: CPSU-DOE-F23S4G7

• Camera: Nancy's 16.1 MP Canon PowerShot SX700

• Group email addresses: abc@university.edu, 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. Save your proposal as a PDF and include it as an attachment in your email. Keep in mind, it can take up to two business days for the iFixit technical writers to respond to your email.