• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Guarantee/Warranty Period"

Collapse

  • Wanderer
    replied
    Originally posted by kingcook View Post
    Hey, what are people's opinions here on length of warranty period, after contract end date? The agency has put a 6 month period, but that sounds OTT.

    This is a contract to work on existing code as a developer.
    some random thoughts:

    Providing a warranty is going to be good for your IR35 status but you want to be sure that the wording is such that you don't get ordered to fix all manner of defects in the future.

    Software developers generally don't give a warranty on software, they provide a support contract. You could offer the agency a support contract if they wish.

    If the software passes the client's tests then there is no need for a warranty. Giving one would leave you wide open to them abusing it to obtain free consultancy.

    Any warranty you did give would have to be pretty tightly worded.

    Leave a comment:


  • BlasterBates
    replied
    Guarantee doesn't make sense when you work on a consultancy basis.

    Guarantee is basically for fixed price projects or a well defined deliverable with an acceptance test specification. In that case 6 months would be fine, I remember this from sometime ago. Thereafter should go into a service agreement. For example if there is a complaint and you can show it's part of the acceptance test you can then charge for an enhancement.

    I would be very wary about signing a guarantee for a "bum on a seat" contract. It would be too ill defined and you don't have enough control about what everyone else is doing and how it's specified. A lot of problems are caused by misunderstandings.

    However this would be a big plus point for being outside IR35. From that point of view, has it's attractions.
    Last edited by BlasterBates; 26 November 2012, 12:20.

    Leave a comment:


  • borderreiver
    replied
    You have to be able to investigate whether any reported defect was present in your code at the time you handed it over to the client.

    If you can show that the defect, real or not, was not present at that time, it's not your problem and you should expect to be able to bill them for the time you spent analyzing the non-defect (depending on your relationship with the client: I would not bill for an analysis that only lasted an hour or two, for example). I would make sure a clause like this is in the contract before agreeing to any warranty period.

    Leave a comment:


  • Boo
    replied
    Originally posted by kingcook View Post
    Hey, what are people's opinions here on length of warranty period, after contract end date? The agency has put a 6 month period, but that sounds OTT.

    This is a contract to work on existing code as a developer.
    I give 1 months warranty but I in no way apply that to other people's code. Tbh, if they've got other people working on the code then it really lets you off the hook IMO, in legal terms ayway. But there are the IR35 considerations to think of and also customer relations. To me that would count for more than the exact contract term though it would be business like to try to reduce the term as far as possible during the negotiations.

    Boo2

    Leave a comment:


  • kingcook
    replied
    Originally posted by JamJarST View Post
    How bad is your work that you don't think it will hold up for 6 months?
    My concernis that i'll be maintaining/bug fixing code that has been worked on by other people, an would no doubt get worked on by others after my contract ends.

    For them to come back to me 5.5 months later saying X or Y doesn't work could be a can of worms considering the above.

    Leave a comment:


  • eek
    replied
    Guarantee/Warranty Period

    On code that's not 100% your own? I'd be very careful there unless its paid for time and materials.

    Leave a comment:


  • kingcook
    replied
    Originally posted by northernladuk View Post
    Surely the devil is in the details here. Gaurantee against what?
    Guarantee aganst any defects.

    Leave a comment:


  • JamJarST
    replied
    Originally posted by kingcook View Post
    Hey, what are people's opinions here on length of warranty period, after contract end date? The agency has put a 6 month period, but that sounds OTT.

    This is a contract to work on existing code as a developer.
    How bad is your work that you don't think it will hold up for 6 months?

    Leave a comment:


  • northernladuk
    replied
    Surely the devil is in the details here. Gaurantee against what?

    Leave a comment:


  • kingcook
    started a topic Guarantee/Warranty Period

    Guarantee/Warranty Period

    Hey, what are people's opinions here on length of warranty period, after contract end date? The agency has put a 6 month period, but that sounds OTT.

    This is a contract to work on existing code as a developer.
Working...
X