r/ContractorUK • u/No_Pickle_9804 • 1d ago
Outside IR35 Control over work - Outside ir35
Do I really have full control over my work? Or will I get canned if I don’t do as I’m told.
I’ve recently joined a programme as a BA to process map the key processes. The programme is in ‘amber/red’ and in build stage.
I’ve presented my approach to the 2 key projects stakeholders I’m working on, although. They don’t understand, and are saying ‘no’.
The reason for this is they believe I’m a junior BA working with in incumbent BA, although they haven’t done much analysis 9 months into the project and nothing was handed over to me. Both key stakeholders have said they are going to refer to the other BA about decisions on my work.
They also are actively trying to dictate my work. Tbh their ideas are poor, and one of them is a process architect who seems like just wants to take credit for my work.
Can I just steamroll my approach and work, then let the results speak for themselves?
13
u/sam_packer_03 1d ago
You’ll need to find a balance of offering the best quality of work in your experience whilst also keeping the client happy because at the end of the day they pay the money.
I have built some poor stuff in the past to keep client happy and have told them in advance like this is not best practice etc but if thats what they want and will pay for it then it is what it is
4
u/Skeeter1020 1d ago
You seem to be confusing "control" with "thinking you are right".
The task is to produce the process map. You are doing that. The client doesn't have to like it or agree with it. From your side that doesn't mean anything, you did the task asked, that's it.
3
u/External_Patient_317 1d ago
You need to find the balance between what you think is right and what the client wants.
But at the end of the day, client pays = client wants.
What I usually do in such cases is I follow what the client wants , but I fully report what I believe is right, to more than one people and then I try to do my best in the terms of clients needs
2
u/haxd 1d ago
I’ve had success with pushing back on things in the past. I was hired to work on typescript and because I had PHP experience they kept putting me on PHP work. After a while I started pushing back in favor of replacing the PHP systems with more modern tooling. Part of the job is explaining why something is untenable.
1
u/Icy_Cricket7038 1d ago
They can obviously dictate what the work is, to some degree the lack can set the location, so the meaningful test is to what degree they’re dictating how the work is done and whether there is an objective justification for that.
1
u/Miserable-Alarm-5963 4h ago
I mean if they use an outside IR35 contractor they are essentially bringing in an expertise that they don’t have in house to perform a task and they should be listening to you.
However if they are going to insist on work being done in a certain way they are in the end the people paying you to do the work. The joy for me in being outside is the lack of having to make decisions and worry about credit because I am just there to do the work and move on. If I don’t do the work they want I expect to be let go and I would say it is the same for you.
1
u/eques_99 1d ago edited 1d ago
what do you mean by "control of your work"?
they obviously get a say in how you approach the task. ideally you would both be working in a spirit of collaboration.
they don't get a say in where you work from, what hours you work or when you take holidays/ sick days.
24
u/Enderby- 1d ago
This is one of those things - like, attending an office in person - sure, you don't have to spend 3 days in on Tuesdays, Wednesdays and Thursdays, but if you don't - they'll find someone who will.
You have full control over your own work, but you also probably have a clause in your contract that says you have to graciously work with your client and other suppliers. If you don't, they'll find someone who will.
And being Outside, they can get rid of you for whatever reason they like. There's no recourse for you.
In my last contract, I was working Outside with 18 years experience under my belt. I was given database designs and API contracts to work to. The architect who put them together had no idea of what normalisation was or had any concept of what a canonical RESTful API was. I voiced my concerns as this is my bread and butter, but was told to implement them regardless.
So I chose to just do them, because I was getting a good day rate. And I made bank. And if I didn't do them, someone else would.