What Is A Project Agreement And Why You Should Use One

Employers should think of a Project Agreement as a chocolate cake and the details that goes into creating one the ingredients for a successful business relationship. A Project Agreement is a written and binding contract between employer and freelancer. It is the official word, promise or handshake that says, “I mean what I say and I say what I mean.” A good working relationship can still occur between employer and professional without a Project Agreement, but, if not, it is added insurance that a project can still be delivered to the employer on time and within budget to you.

Reasons for using a Project Agreement are numerous; but its key selling point is that both freelancer and employer receives equal protection under the agreement. The freelancer receives a promise from the employer that they will be paid for services rendered, and the employer receives a promise from the freelancer that their project will be completed as requested.

The lure has been set and all that is needed is to cast your reel into the water and whoola, a Project Agreement you can live with. What will enable an employer and freelancer to live with a Project Agreement has more to do with creating (as requested by the employer to the freelancer) and approving one (employer can decline or approve a Project Agreement). Like a house without solid foundations, it can fall like a house of cards, so to can a Project Agreement that lacks structure, clear guidelines, and objectives.

Think of completing a project not as a sprint but a marathon, and before you run the marathon you need a training schedule that you can adhere to and follow. This is not to say, that the schedule, shown to be too strict or too lenient, can not be changed if the person is not getting the results they desire. A Project Agreement is a schedule that employer and professional freelancer follows.

What Is A Project Agreement

A marathon training schedule can look something like this: Monday: 9:00am: eat oatmeal, wheat toast, boiled egg and orange juice for breakfast, 10:00am run ten miles, and 5:00pm do strength training exercises.

Although a Project Agreement does not resemble a marathon training schedule in any way, it does in one, and that is in its details. The simple fact is, knowing the who, what, when, where and how, is what will see employer and professional through to a project completion date.

The Who: Who is doing what and under what circumstances? Who retains ownership rights over the product? Who is completing the project?

The What: What is going to happen every step of the project? In what circumstances will Escrow be used? Escrow is a risk free way to do business. An employer can refuse to release funds to a freelancer if they find their work unsatisfactory. If problems arise, what should be done? What is the size of the product i.e number of pages or words required, and the format of the article?

The How: How will the project be completed? In a day, week or in a month? How many due dates does the employer want? One due date or a couple in an effort to break the project down into manageable parts. How will disputes be settled if any should arise. An employer can take advantage of mediation and arbitration services, if an issue between them erupts that can’t be easily resolved. If necessary, how will revisions be made?

The When: When and under what situation should termination occur? Should it occur when the freelancer continues to turn in work that is sub-par? Is the freelancer hard to contact? Does the freelancer continually fail to meet numerous deadlines?

The Where: Where and in what way will communication take place between employer and freelancer? By email, phone or in person?

In conclusion: A Project Agreement is just the map you will need as you drive the sometimes sunny, sometimes difficult road when trying to complete a project.