FAQ

In the most basic sense, a beta is an editor. A beta is someone who reads a story with a critical eye with the goal of improving the technical and creative aspects of a story. On the technical side, a beta will look at grammar, spelling, capitalization, punctuation, verb tense, and more. On the creative side, a beta will look at flow, description, pacing, dialogue, and more. In order to become a beta for Project Team Beta, you must become qualified by passing a test that determines how well you are able to edit a chapter on a technical and creative level.

To become a member of Project Team Beta, you first need to fill out an application. Applications are available here.

To start the process with Project Team Beta, an author must fill out a Story Application. Once the application is approved and the author has received a Welcome Letter, Authors submit chapters via email to Admin@ProjectTeamBeta.com. A moderator will then put the chapter into transit. While the chapter is in transit, it will be sent to two qualified PTB betas. A mod will then email the chapter back to the author. All comments are read through by a mod to ensure the best quality edit possible.

Project Team Beta has an age/content guideline in place to protect our underage members and to protect ourselves. We will only work on stories rated R or NC-17 if the author is over the age of 18. Additionally, we will only send chapters rated R or NC-17 to betas over the age of 18.

The PTB process is not an instantaneous one, and according to our guidelines, we will return a chapter to an author between five and seven days. Each chapter is submitted to a first-run beta and then to a second-run beta. It is recommended that each beta return a chapter within 48 hours. As authors who work with PTB know, the five to seven days is not a hard and fast standard. Many times the process happens much faster than that. The opposite is also true. Sometimes we need extra time to beta and return a chapter to an author.

Yes. You can fill out an application for both an author and a beta. We will not send you your own chapters to be beta’ed.

Chapters are sent to betas based on the author’s and beta’s preferences.

“Not transit-ready” means your story application contained multiple instances of a number of different basic grammar errors. PTB’s transit standard is that all chapters sent in must show a thorough self-edit by the author that demonstrates basic grammar knowledge. At this point, the PTB moderators feel that you are not quite at that level yet.

If your story is not transit-ready, you will be invited into the New Learners group, where PTB moderators will work one-on-one with you and help you learn the basic grammar concepts needed for a thorough self-edit.

This group is for new PTB authors who are working toward being transit-ready. You will be provided resource links to study from and one-on-one help with PTB moderators. Once the PTB mods feel you are ready, you will “graduate” from the program, and will then be able to send in your chapters to be beta’d via transit.

In order to work with PTB, we must start with your story at chapter one. This allows us to provide you with the best possible feedback throughout the entire story.

Project Team Beta allows each author to have one story in transit per fandom and one one-shot at any given time.

After you receive notification that your story has been accepted, you are ready to submit your first chapter into transit. A chapter is submitted to transit by sending it to Admin@ProjectTeamBeta.com. Chapters must be self-edited to the best of the author’s ability, they must contain the appropriate information piece, and they must be in .doc format, which is compatible with Microsoft Word and OpenOffice, a free software package available online.

Yes. After you have edited your chapter according to your beta’s comments, if you feel that your chapter is not yet ready, you may submit it again into transit. Please tell the moderators in your email that your chapter is a resubmission so that there is no confusion.

Not all betas and authors will mesh. You could come across a beta that you were not particularly fond of. If this happens, please politely and respectfully tell a moderator. We will mark it in your info to not to send your future transit chapters to that particular beta.

No. PTB will not force authors to go on Permanent Assignment. However, we do encourage it. Sometimes finding the right betas takes a little longer than most, and we will continue to accept your chapters into transit while you are looking.

If you are looking for a particular type of beta, email PermanentAssignment@ProjectTeamBeta.com. A PTB moderator will put beta suggestions in your record.

Yes. Once your story is put on Permanent Assignment, it is no longer considered a transit story. Your information is moved to the Permanent Assignment tracker, and you have a free space in transit to submit a new multi-chapter story.

Yes. We welcome all one shots, whether or not you have a WIP with us. However, you are still only allowed to have one chapter in transit at a time.

If you are writing for a Contest or Event, there are also time constraints to consider. We suggest that you fill out a Story Application at least 3 weeks before the contest/event deadline (even if your story is not yet finished), and then once accepted, send in your story to be beta’d at least 1–1.5 weeks before the contest/event deadline. The earlier the better though.

All betas can retest after a waiting period of one week. Within that week, betas are given resources so that they may study their weaknesses. On top of that, the betas will be told what their particular weaknesses are, are given an answer key and study guide, and are invited to join the Beta Mentoring group.

This is a study guide of sorts for betas who are studying to pass the PTB beta test. Betas are given resources to study from, exercises to practice on (including a practice test), and one-on-one help with PTB moderators.

No problem. We will work around your schedule. Email Admin@ProjectTeamBeta.com and let us know when you would like us to send you chapters. Common requests are: once a week, once every two weeks, only on Fridays, etc.

The PTB moderators read through every chapter sent into transit. If we feel that the chapter has not been thoroughly self-edited by the author, we will not send it to a beta. However, sometimes chapters do slip through, and if you feel that the chapter has one too many mistakes on multiple basic grammar concepts, contact a mod ASAP at Admin@ProjectTeamBeta.com.

Some stories just aren’t our cup of tea. If you are able, please try to finish beta’ing it, and then when you send it back, mention that you’d rather not beta future chapters, and we won’t send you chapters from that story anymore. However, if you do not like it at all, it offends you in some way, etc., please contact a mod ASAP at Admin@ProjectTeamBeta.com, explaining the situation, and we will reassign it.

This varies. At the most, we try to send betas chapters once a week. However, how busy our betas are depends on how busy transit it. PTB has been through times where we haven’t been busy at all, and betas were getting chapters every two weeks, sometimes three. The same is true for the opposite. PTB has been very busy, especially at the beginning of summer, and betas have gotten chapters every 3-4 days.

If PTB is especially busy, we will send out a notice to the betas, explaining the situation. However, we will still follow beta preferences. If you request only to be sent a chapter once a week, we will only send you a chapter once a week, regardless of how busy we are.

All betas are required to return a chapter within 48 hours. If you are unable to beta it within that time period or if you need an extension, contact Admin@ProjectTeamBeta.com.

If you are ever unable to beta a chapter, contact Admin@ProjectTeamBeta.com ASAP, and we will reassign it.

Of course! We understand sometimes a chapter needs more time for various reasons. Contact Admin@ProjectTeamBeta.com ASAP. The most we usually give for extension is two days. There are exceptions, but usually if you are unable to beta a chapter within 4 days, we will reassign it.

Have fun! And email Hiatus@ProjectTeamBeta.com the day you want to start your hiatus and the day you can start accepting chapters again. At the end of your hiatus, we will send you a confirmation email asking if it is okay to take you off hiatus. Please respond to this email ASAP.

If a beta does not return a chapter with 48 hours and does not contact our Admin account, we will send the beta a Late Notice. The beta then has 24 hours to contact our Admin account. If we do not hear back from the beta within 24 hours, we will put the beta on Placed Hiatus. This means the beta will on a required one-week hiatus. There are exceptions, but usually, if the beta has more than three placed hiatuses, we will ask the beta to resign from PTB.

If you are put on Placed Hiatus, and there was a good reason as to why you were unable to contact us (ie. No internet connection, etc.), email Hiatus@ProjectTeamBeta.com your explanation ASAP.

No problem! Email Hiatus@ProjectTeamBeta.com, explaining your situation. We will put you on Permanent Assignment Hiatus, meaning you will still be a PTB beta, but you will no longer receive transit chapters until you are ready.

Technical feedback is all the grammar related comments, including but not limited to: dialogue punctuation, comma usage, verb tense, etc. We expect all of our betas to at least comment on the basic grammar concepts.

Creative feedback is all the comments related to plot development, character development, pacing, etc. These are your opinions you give the author to help improve their story.

No. However, we do encourage it. If at any time you feel a story could improve in some way, or if something doesn’t make sense or if the timing is off, etc., please don’t hesitate to comment on it.

Please remember that most of creative feedback is your opinion. Tell the author in a respectful and polite way. Ultimately, it is up to the author to follow or to not follow your feedback.

Permanent assignment typically does not happen until at least three or four chapters of a story have been edited through transit. This allows for authors to work with several different betas and receive a variety of feedback before settling down with the same two betas for the remainder of their story. Permanent assignment is completely optional. If you prefer to keep sending your chapters to transit and receiving different betas each chapter, that’s fine too! There is not a set requirement for when or how stories get placed on permanent assignment.

Great! Send an email to PermanentAssignment@ProjectTeamBeta.com telling us about your request. We will make a note in our trackers and contact the author to see if he or she feels ready for a permanent assignment and thinks your style of editing is a good fit for what he or she is looking for.

Great! Send an email to PermanentAssignment@ProjectTeamBeta.com telling us about your request. We will make a note in our trackers and contact Beta Betty/Beta Bob to find out if he or she is available to take on additional permanent stories. Sometimes, our betas have a full load but still enjoy editing the occasional random chapter through transit. Please be patient with us as we help you find permanent betas for your story.

If you’re a beta and haven’t yet read the entire story, do that now! It’s almost impossible to be up to date on every story you receive via transit, but you should definitely read all the previous chapters of any story you are permanently assigned to.

The next thing you should do is contact the other members of your beta team (the two betas and the author). Discuss how you would like to beta the story. Does the author want to send the chapter to the same first beta and same second beta for each chapter? Do the betas want to take turns being first and second beta? Would whoever is the first beta like to see the feedback left by the second beta after he/she finishes? Does the author have a story outline she would like to share with one or both of the betas? Is there a specific type of feedback the author is looking for? How often does the author intend to update? The world is your oyster, so feel free to talk about anything!Once you’ve got a plan in place, the author should begin to send chapters to the betas.

Betas are still expected to stick to the 48 hour turnaround time. If you cannot return a chapter within 48 hours for whatever reason, you MUST contact your author and discuss the situation with them. If you find yourself consistently taking longer than 48 hours to return a chapter, you may wish to reconsider being a permanent beta for the story.

If your betas suddenly disappear or are consistently taking longer than 48 hours to return a chapter to you, please contact us at PermanentAssignment@ProjectTeamBeta.com and let us know. We will help you resolve the issue.

Contact PermanentAssignment@ProjectTeamBeta.com. We can arrange for you to submit chapters through transit while your permanent beta is unavailable.

It is very easy to save a file in .doc format using OpenOffice. Simply follow the instructions below:

1. Once you are ready to save your document, select “file” from the menu.

2. Scroll down and select “save as.”

3. Under “file name,” enter in the name of your document.

4. Select “save as type” and a scroll-down menu will appear with a list of file formats available. There are three different options available for .doc format. Please select the “Microsoft Word 98/2000/XP” (.doc)” option.

5. Click “save.”

It is very easy to set up OpenOffice so that your files are automatically saved in .doc format. Simply follow the instructions below:

1. Start OpenOffice.

2. When the message “Welcome to OpenOffice.org” appears, select “tools” from the drop-down menu in the upper left-hand corner of the page.

3. Click “options.”

4. In the left-hand column, select the “+” that appears next to the “load/save” to expand the menu. Once the menu has expanded, click on “general.”

5. Under the “Default File Format and ODF Settings” heading, make sure the document type is “text document.” Under the “Always Save As” heading, select “Microsoft Word 97/2000/XP.”

6. OpenOffice will warn you that by not using ODF 1.2 file format, some information may be lost. Project Team Beta has not observed any loss of data while switching between Open Office and Microsoft Word.

7. If you do not want to receive a warning every time you save a .doc file, uncheck the “warn when not saving in ODF or default format” box.

8. Select the “ok” button when finished.

The comment feature in OpenOffice is slightly different from Microsoft Word. While you can still add a comment, the item being commented on is not highlighted. Instead, a caret or anchor appears at the current cursor location. Due to this difference, it is important for betas and authors alike to name the specific area in question in the comment box. The phrase or character being highlighted will not transfer over from one program to another; therefore, the comment will simply be accompanied by a caret at the beginning of the area that would have traditionally been highlighted in Microsoft Word.

To add a Project Team Beta style comment using OpenOffice, simply follow the instructions below:

1. Place your cursor at the beginning of the area you are commenting on.

2. Select “insert” from the main menu and scroll down to select “note.” You may also use a short cut by pushing Ctrl + Alt + N.

3. In the right-hand margin, a colored box will appear with your name, date, and time. Type your comments inside the colored box.

4. If you wish to reply to or delete a comment box, left click on the down arrow to the right of the signature line at the bottom of the comment box. Select the action you would like to take.

Project Team Beta style comments will most likely be hidden when a document is first opened in OpenOffice.

To view Project Team Beta style comments, simply follow the instructions below:

1. Select “view” from the pull-down menu at the top of the page.

2. Select “notes” so that a check mark appears to the right of the option in the pull-down menu.

If there are a large number of comments, it can be a little difficult to determine which comment goes with which anchor in the document. To see which comment goes with which anchor, hold your cursor over the comment. The dotted line leading from the comment to the anchor will turn into a solid line, showing the location of the anchor.

The author name, the date, and the time will appear at the bottom of each comment box. Comments from different authors will be displayed in different colors.

To change the name displayed in the Project Team Beta style comment, simply follow the instructions below:

1. Select “tools” from the pull-down menu.

2. Select “options.”

3. Expand the OpenOffice.org menu if it is not already expanded and select “user data.”

4. Enter the name you wish to appear in the comment box.