Personal bio requested for team presentation

[MrMarkyMark]

I'm not sure you are. Are other external professionals required to provide this kind of thing? Does the photocopier repair man have to provide a "bio" when he comes on site? If not, then I don't you should be required to either. You're an independent professional service provider, contracted to provide a service and deliver against an agreed schedule of work. Nothing else should come into it. Your "bio" (i.e. your CV) should only be required when you're being interviewed for the gig.

Have you ever truly done a truly senior program level role?

Product specialist for a large international banking project ,for example?
I have, everyone wants to know who you are and where you have been before.

[northernladyuk]

Have you ever truly done a truly senior program level role?

Product specialist for a large international banking project ,for example?
I have, everyone wants to know who you are and where you have been before.

Not when they hear they don't.

[itjobs]

Its easy to keep it short as long as you can stick to the facts that is relevant to the project. Go for it when you get a bit of marketing opportunity. It speaks volumes.

[billybiro]

This is a load of tulip and behaviour of people like you is only giving the rest of us bad rep.

Plenty ClientCos have teams and entire divisions of contractors working on a specific project. Being part of the team or not has nothing to do with IR35

Really? So being a contractor on a team full of permies where you're doing essentially the same job as the permies (as is the case in an agile software development team, for example) is absolutely fine from IR35 perspective is it?

Please, do tell how you'd convince Hector that you're absolutely not part and parcel and should be considered to be entirely different from the permies that work for the same client and within the same team as you.

[billybiro]

everyone wants to know who you are and where you have been before.

I understand this, but there's a world of difference between simply letting "everyone know who you are and where you've been before" and being an intrinsic part of a team which could be staffed by permanent staff and have you, as the the contractor, doing the same job as them on a day-to-day, week-to-week basis.

[SueEllen]

Really? So being a contractor on a team full of permies where you're doing essentially the same job as the permies (as is the case in an agile software development team, for example) is absolutely fine from IR35 perspective is it?

Please, do tell how you'd convince Hector that you're absolutely not part and parcel and should be considered to be entirely different from the permies that work for the same client.

You are incorrectly presuming that people in teams all do the same role. Many teams are made up of people in different roles with different skill sets, and as in Agile teams the teams are self-organising e.g. you are proactive then you don't fall under IR35.

[billybiro]

Sorry, billy, I disagree. If a team is being assembled to deliver a project, then it's part of the project team. The copier repair man is not part of a project.

It would be a different kettle of fish if your contract says your job is to provide support for anything and you are not actually delivering anything different to the permies.

Exactly, but if you're an intrinsic part of a "team" containing permanent staff, and there's multiple people on that team performing largely the same role (developer, BA, PM etc.) then you are almost certainly delivering the same thing as one or more of the permies. Then what?

[WTFH]

Exactly, but if you're an intrinsic part of a "team" containing permanent staff, and there's multiple people on that team performing largely the same role (developer, BA, PM etc.) then you are almost certainly delivering the same thing as one or more of the permies. Then what?

Then you're not really a contractor.

[NotAllThere]

I'm not sure you are. Are other external professionals required to provide this kind of thing? Does the photocopier repair man have to provide a "bio" when he comes on site?...

Twaddle for three reasons.

1. It would be perfectly normal for the photocopier repair man to introduce himself to the permie he's working with, with a brief description of his skills, even if it's limited to "Hi, I'm Billy Biro, and I'm here to fix your photocopier". The bio is appropriate to the amount of interaction the external will have and the level to which he's working.
2. You'd find your work extremely difficult to do if you never introduced yourself, formally or informally, to the people you'll be working with. You're not coming in to clear a drain blockage - your work means you're obliged to interact rather more with the permies. Personal introduction is "part and parcel" of that.
3. The external consultants from big-co also give personal introductions to the project team.

[kaiser78]

Exactly, but if you're an intrinsic part of a "team" containing permanent staff, and there's multiple people on that team performing largely the same role (developer, BA, PM etc.) then you are almost certainly delivering the same thing as one or more of the permies. Then what?

Same goal maybe but different deliverables, which is a key distinction. As a PM working on a project my role and deliverables would be totally different for example to say the Architect, BA, Developer, Test functions on the same project.

The notion that one should not be part of project team because one is a contractor is wide of the mark.