Once you’ve chosen a repair guide topic, the next step is to send us a proposal. The proposal should describe the project you intend to work on. The proposal doesn’t need to be long, but we’ll use it to help start your project off in the right direction—after all, our goal is to publish your final project for all the world to see!

A proposal is required for the project, even if it is informal. Proposals allow us to give you the necessary privileges to work on the site without problems, and to verify that no one else has selected the same project as yours. You can find a sample proposal here. Also, make sure to include a brief message in the email's body to provide context for your proposal.

Proposal Prep

What to Include in Your Proposal

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

  • Fast Fix: Leaky Faucet (or whatever fix you’ve chosen)

  • Team tag: CPSU-DOE-F26S1G1

  • Camera: Nancy's 16MP Canon PowerShot SX170 IS

  • 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!

Email your proposal in PDF format to techwriting[at]ifixit[dot]com. Include your team tag in the email's Subject field, as well as a brief message in the email body. (It's a nice professional touch—and a general courtesy—to not send a blank email with an attachment.) Remember to CC your instructor and teammates.

It can take the iFixit technical writing team up to two business days to respond to your email, so make sure to plan accordingly.

Once you've got the go-ahead from our tech writing team, you're clear to proceed to Checkpoint 1!


Stop right there!

Do you have the droids you’re looking for? Don’t let a Jedi mind trick fool you—or hurt your grade. Take a moment to review the page and make sure you have met all the proposal requirements. When you are ready, be sure to email your proposal to techwriting[at]ifixit[dot]com. We’ll get back to you and let you know when you’re ready to move on.