Congratulations! It is a beta!

When you take your first steps into writing fan fiction you might hear people say: ‘I am done with this story, now I am sending it off to my beta’ or ‘Beta reader: ’. But what is a beta reader exactly? What can you expect from a beta reader and what should a beta reader do?

Basically, a beta reader is the editor of your story. The origin of this name comes from the computer software industry where beta testers or beta readers test the software extensively before the software is released to the clients or consumers. Basically, this is what a beta reader does before you publicly release your story on the Internet: they go over it and give you concrete feedback so that you can tweak it or ‘whip it into shape’.

What is a beta and why do I need one?

An author might think: ‘I don’t need a beta, my writing is good enough.’ This is something that is said often, especially after a reviewer suggested it and maybe a writer is right when they just want to write, publish it and do not look back or shake off reviews easily. It does depend on how feedback sits with you, the author; after all a reader made a comment about your writing which either effects you or not. Of course it is understandable that an author feels hurt or upset by such a comment, but do at least consider it. Bear in mind that even if you have a perfect skill set when it comes down to grammar and spelling, writing a story is a completely different matter. Writing is a skill that some are gifted with naturally, others just have to learn it: but it is something you can learn. Some writers can benefit greatly from a beta reader if they want to improve their skills.

Where do I go to find a Beta?

Betas are all around you. They are readers and, often, writers of fanfiction just like you. When you are ready to find a beta, consider those readers who have reviewed work you've posted previously; they have already demonstrated some interest in you and your subject matter. Consider those writers in your fandom you particularly admire; you are already familiar with them and know their capabilities. If they are not able to beta for you, they may be able to recommend someone who can. If, in a story you like, you spot a 'thank you' from an author to a beta reader, consider contacting that beta - you already know they can do a good job. Also, many fanfiction archives, like Open Scrolls, have a space, a thread, or link to somewhere beta readers can offer their services and writers can seek them. Go exploring, and see what you find out.

I have found a beta. What should I do next?

The key factor here is communication: tell your beta what you need. The more specific you are, the better the beta read will be. It might be that the beta you had in mind cannot perform the beta read you needed for your piece, but it at least does save you from a lot of disappointment when the story is returned to you.

Like writers, betas come in different forms. Most often a beta will have listed what beta skills they have and what they prefer to read and what not. If you are not certain what you exactly need, here are three main descriptions of beta readers in the Tolkien fandom:

- line betas: these betas comb through your story for spelling, grammar and typo’s
- content betas: these betas have a knack for reading your story to help you improve its flow, pacing, logic, characterisations, story structure and plot or story development
- canon betas: when writing fanfic of a fandom, a certain amount of research must be done to make it fit within the fandom. These betas know the works extremely well and will help you to make it fit and help you to write the characters in style of Tolkien.

Once you have established what kind of beta you need, you and your beta can communicate about what the story needs.

Beta reading: guidelines for both sides.

When engaged in a beta-author relationship, there are certain things both sides should receive from each other. A lot though depends on the agreement which is made when the author contacts the beta reader. One important matter both parties should decide on is the time a piece is returned to an author.

This work is not intended to set in stone how long a beta read should last. Every one has a life and unexpected events can happen; but be reasonable towards each other. A beta reader can have many beta reads to do and might give you fair time estimation. If you are in an absolute hurry to publish your work (deadline for a challenge or you cannot wait to share it with the rest of the world), it is important that you tell that to your beta reader. Be aware that if you want your work to be returned within 24 hours it might be the case that your beta reader missed things. Give your beta reader the time to go through your work properly.

What can an author expect from a beta reader?

1. Your beta reader should show interest in your story. If they do not, you will notice that in their comments. Do pay attention to the beta reader’s interests before you ask them to look at a story. If they say that they do not like to read about Hobbits, do not let them read a Hobbit story.
2. Honesty is the key here: a beta reader should be honest with you. Yes this might hurt, but most often a beta will tell you what works and what will not work (and will explain it). Your beta is not working on your piece to hurt your feelings. Try to take a step back and use critical feedback from your beta reader to place it in a different perspective.
3. Your beta should be thorough, but expect that even they will miss things. We’re all human after all.
4. Expect comments to sneak in like: oh this is good, or I had to laugh so hard about this.
5. Not every beta reader is able to read a story for everything. If you have enlisted a line beta to look at your piece for grammar and spelling, it would be unreasonable to expect your beta reader to comment on things like flow and pacing that they do not master fully.
6. Different persons, different opinions: do expect them to pop up in a story and pay attention to them: they might be useful.
7. A beta reader should be neutral. If they are patronizing or patting your ego: you will be on the loosing side here.

What can a beta reader expect from an author?

1. A piece should be at least checked on spelling and grammar by the available word processor.
2. An author should tell you what they need from you or what you should pay extra attention to. Only after a longer period while working with the author you can estimate what they need.
3. Expect questions coming back from your author: they might not understand some things completely or will need more help with their work.
4. A piece should at least show the changes you made or suggested. A beta read takes hours and a lot of time; if an author refuses to incorporate any suggestion you made you are entitled to say no the next time.
5. An author should give you a reasonable amount of time to work on a piece; in return you should alert the author that the read might take longer.
6. Give credit where credit is due. Expect to be listed by the author in the story for the work you have done on it.
7. Giving concrete feedback is not always easy: be fair, reasonable and bring it gently. The author did ask for your beta read, so you should receive thanks for it.

Tips and suggestions:

* Use more than one beta to get a good and thorough read of your story.
* If you are capable of handling it: join a writer’s workshop or beta-circle. The benefits are that there will be many fresh eyes looking at your piece. This doesn’t always work great because the more opinions you get, the more confusing it can be. Most often the feedback is returned directly and can overwhelm you.
* Betas doesn’t necessarily have to be a friend or your friend. In some cases the relationship between an author and beta reader might go askew and you will loose a friendship as well. This being said, betas can become a personal friend too.
* Know when to move on to a different beta reader. After a while you might have mastered a specific skill set which you worked on with your current beta, but in order to grow, you sometimes have to move on.
* When enlisting the help of a new beta, make sure to include information about the story in question in your first message or email. A quick note may seem non-threatening, but it doesn't tell the potential beta much useful information. A full synopsis isn't necessary, but including some facts about the piece like the main characters and the length, can help betas decide if they can devote the appropriate amount of time to the project or recommend another competent beta if they cannot help you personally.
* Do your best to spell and word your communication properly, especially in a request for help. L33t and "creative spelling" don't belong in a story and, therefore, shouldn't appear in emails to a beta reader.

Above all: communicate with your beta reader. The more you ask, the more you will learn.