Welcome Guest! The IOSH forums are a free resource to both members and non-members. Login or register to use them

Postings made by forum users are personal opinions. IOSH is not responsible for the content or accuracy of any of the information contained in forum postings. Please carefully consider any advice you receive.

Notification

Icon
Error

Options
Go to last post Go to first unread
firesafety101  
#1 Posted : 01 August 2011 16:31:38(UTC)
Rank: Super forum user
firesafety101

I have offered to assist a project manager with writing some method statements, starting to think I made a mistake? My idea of a MS is to describe how the work will be carried out safely, to include use of equipment, PPE, safety of others etc. etc. I did one and he is now suggesting there is not enough detail i.e. "the Works doesn't give much detail of exactly what they are doing. Should it not identify the items they are removing and the method involved for each item? Eg. are they loosening fastenings, drilling them out or cutting them off? How many men required to handle a sheet of cladding safely? Do they leave existing anchors in place or remove these? Care taken in handling sharp edges.....etc." I believe he is looking for too much from a MS and should be writing a "Process method statement" himself. Am I right or wrong?
SteveL  
#2 Posted : 01 August 2011 16:52:32(UTC)
Rank: Super forum user
SteveL

A method statement should enable the person to carry out the works, even if they have never done the job. Teaching to suck eggs comes to mind. The devil is in the detail. The higher the risk the greater the need for step by step. All of the safety parts IE PPE, equipment, traffic management, materials etc, should be listed in other areas, the method statement should be formed from the risk assessment, and is how to complete the works.
Paul501  
#3 Posted : 01 August 2011 17:02:08(UTC)
Rank: Forum user
Paul501

Hi Chris, In my opinion a method statement should detail the controls which have been identified following a risk assessment of an activity, to ensure that all concerned employees are aware of the priciple hazards, safety precautions which need to be taken and details of any boundaries, restricted areas, materials, substances and plant. The statement should also detail step by step what work is going to be done. i think you are right when you say the project manager should write the method statement himself as he would know the work involved to complete the activity whereas you should concentrate on the risk assesment and any safe systems of work required.
SteveL  
#4 Posted : 01 August 2011 17:08:32(UTC)
Rank: Super forum user
SteveL

Chris Sorry never answered your question correctly, yes you are correct, he should be writing the method statement, he is the one who knows the workings. Paul is correct saying you should help with the RA and safe systems.
RayRapp  
#5 Posted : 01 August 2011 20:43:58(UTC)
Rank: Super forum user
RayRapp

Chris I firmly believe that those doing or managing the task should be responsible for writing the method statement. The amount of detail should be directly proportionate to the risk. That said, as a rule I prefer MS to be succinct. Typical content as follows: Location of work Start date and duration of work Scope of works Sequential list of main tasks (can be bullet point type) Personnel involved and any qualifications required PPE Plant and equipment Significant hazards Accident & emergency arrangements Any other relevant information Risk Assessment and controls
Hally  
#6 Posted : 02 August 2011 08:36:19(UTC)
Rank: Super forum user
Hally

Chris, I've dropped you a couple of PC guidelines that we've received over the last year. Regards Jonathan
TSC  
#7 Posted : 02 August 2011 09:18:04(UTC)
Rank: Forum user
TSC

Method statement should be compiled by the person who understands the task and relevant processes so should be the project manager as a follow up to the risk assessment which should have been done with input from the persons conducting the tasks. As for the detail in it, then this should be a reflection of the risks, I have just finished an audit today where I stripped down a risk assessment file to a 1/3 of its original size, a 17 page policy/template with 2 lines of risk information in it for example. My view is that the method stateemnt should contain enough detail for someone who has never seen the location or has full knowledge of the task to build a picture up in their head on the task itself and how it is done. Too many times have I seen location - Joe Bloggs House for example instead of it being described i.e. if it is roof work what height is the roof. The method statement may contain the information that Ray mentioned but sometimes dependant on the amount of method statements i.e. if it is aproject with more than one task you may have one master document for everything else.
BigRab  
#8 Posted : 02 August 2011 09:41:38(UTC)
Rank: Forum user
BigRab

The problem that we all have here is that there is no legal requirement for a method statement, no definition of what a method statement is and no specified format. Everybody has their own pet idea of what should be in such a document and off we go on the merry go round of creating more and more useless paperwork. Let's remember that what we are talking about here is a SAFETY method statement and not a full blow by blow description of how the work is done. This document is intended to be information for the people involved in the work and not some kind of back covering exercise for the client. If you have done suitable and sufficient risk assessments for the work to be done then all that is required, in my opinion, is some detail of the specifics of what is to be done, where it will be done, by whom and with what. Such as site; date; access arrangements; protection arrangements if working adjacent to a "live" road or railway etc.; plant and equipment; PPE; any PTW arrangements; employees and supervisors involved; special instructions pertaining to the site or the activity and a reference to the risk assessments. Anything more than this is just unnecessary paperwork.
tabs  
#9 Posted : 02 August 2011 10:35:44(UTC)
Rank: Forum user
tabs

I disagree that a method statement needs to be an instruction manual for someone who has never done the job before - I prefer to see one which is written to reflect the competence of the people doing the works. "Remove widget but be aware of low level access and underground services" would be fine for someone experienced in removing widgets - describing the methodology of removing widgets may be needed for special widgets or people not used to removing widgets. The document should differentiate the job from standard jobs, and identify the parts which follow standard procedures. The document should not be a collection of every working instruction ever written - and parts which do not specifically refer to this job in hand must be removed (otherwise it is seen as licence to do that as well - often without agreement). There is a legal requirement for a safe system of work, and in my company the method statement usually forms part of that safe system.
Hally  
#10 Posted : 02 August 2011 10:36:24(UTC)
Rank: Super forum user
Hally

BigRab wrote:
Anything more than this is just unnecessary paperwork.
I'd normally agreee BUT try telling certain PC's that you won't amend your current Method Statements to THEIR format and you'll find they threaten to take business away. I've had that problem with one who will remain nameless obviously. We also had one to do for an alcoholic drinks conglomerate that refused us access as our MS wasn't good enough and to their format. They sent us their format and i had to remove the majority of our MS to fit in their tiny boxes so in fact couldn't put in all the important info that was needed (obviously our staff had the proper ones from us as well) so it would have been interesting if any incident had happened and the HSE got involved as i suspect they may have been hit hard with a visit to go through all of their preocedures. They laughably approved our MS even though it wasn't anywhere near good enough then, but again not much we can do if they have such poor understanding of how people work in construction and any allied industries to that.
firesafety101  
#11 Posted : 02 August 2011 11:55:33(UTC)
Rank: Super forum user
firesafety101

BigRab I like your post and agree with what you say but we appear to be in the minority. It is difficult to get a proper definition of what should be included in a MS so it is always left to whoever requires the MS to decide if it is good enough. You may find, as in Hally's case that the person "marking" the MS is not as well qualified as the writer, but its a case of do what I say or else. Thank for the examples Hally.
Steve e ashton  
#12 Posted : 02 August 2011 12:45:33(UTC)
Rank: Super forum user
Steve e ashton

This is a subject very very close to my heart at the moment. As client H&S I am getting ever more angry that so many contractors appear to think they have to record everything at least three times. Once in their HSMS standard documents, once in a risk assessment template and again in a method statement template..... What a waste of everyones time and effort. And what a laugh that so many are on templates - and actually OMIT the site-specific stuff that might actually be important (e.g. - recent example - all operatives to be competent and trained, all to wear appropriate PPE, welfare unit to be provided blah blah blah.. No mention anywhere AT ALL of the 30metre sheer cliff less than three metres from where the work was going to happen - or the controls needed to make the work safe! Nor of the very low 132kV overhead line at that location... Whilst the contractors may be competent in construction (I have led or assisted in most of the competency assesments, so I have to believe they are...) I sometimes despair at the lack of competence of the people who write some of the documents. My view - RAMS are written to supplement the general way of doing things (company procedures, trade training etc., reviewed previously by the client, and well understood / trained to all the workforce) with site- or task- specific information needed to get the job done safely. Nothing less, and (PLEASE) nothing more and more and more.... (HINT - the project I am on has one contractor who has target-estimated a need for upwards of 5,000 risk assessments / method statements for his section of the project... If I have to read 10,000 times that only CSCS card holers will be allowed on site - I swear I'll swing for someone!) Big Rab and Tabs - Spot on.. Steve
firesafety101  
#13 Posted : 02 August 2011 13:33:09(UTC)
Rank: Super forum user
firesafety101

Steve I can't beat your 5000 but I did receive 39 risk assessments from the PM.
Hally  
#14 Posted : 02 August 2011 13:37:12(UTC)
Rank: Super forum user
Hally

Steve, Another example for you as to how onerous PC's can be on checking RAMS... We might be putting up temporary fencing and using the following items. Mesh Fence Panel Couplers Blocks RAMS rejected due to the PC's templated checklist stating all tools must be PA Tested and we haven't stated they would be. The fact that we didn't mention any portable electric tools and i don't know how we'd PA test a spanner... The site manager then had to request their H & S Department to give the ok for it to be passed without PA details which wasted two days...at their own expense. Would like to be joking (bit early for the friday thread) but you can understand the frustration that us as a subcontractor (and other subcontractors) have with stupidity from Site managers and the like who can't make their own decision without going through a centralised H & S office.
Ron Hunter  
#15 Posted : 02 August 2011 13:47:18(UTC)
Rank: Super forum user
Ron Hunter

Chris, you have to work with the premise that the people doing the task are competent or working under competent supervision. Limiting the document to a safety method statement (addressing only how significant hazards are to be dealt with) will reduce your task even further - in essence a detailed discussion of controls, equipment and major sequencing. IF your MS is going beyond a single page then you really have to start to question its value. Enough to satisfy the client or principal contractor, and enough to provide an on-site brieing to those involved, because -let's be honest- the people doing the task (at least in construction and related fields) are never going to actually read or refer to this document, are they?
JohnW  
#16 Posted : 02 August 2011 16:04:02(UTC)
Rank: Super forum user
JohnW

I'm coming in late on this thread so I'll just post what I generally do/provide/assist with regards to Method Statement, usually I'm helping a contractor to submit one to a builder. The aim is to achieve what the client wants and to provide all the info that RayRapp mentioned in his posting. The MS we produce is in two parts. Part 1 is the step-by step how the job is accomplished: delivery, unloading, access to work area (e.g. work at height), setting up the work, PPE, installation, task etc. tidy up, leave site and any notes on COSHH, confined space, permits etc as appropriate. The text in the Part 1 will refer at times to other documents, e.g. to points raised in the Risk Assessments, and it will also refer as appropriate to sections in Part 2 of the Method Statement which is in effect a document of the site rules and the site/client policy with reagrd to the main H&S subjects e.g. asbestos, lifting operations, manual handling, dust, weather, first aid, work at height. The aim is to avoid muddling the step-by-step instructions with too much detail, and to avoid 'writing out Part 2' every time there's a new Method Statement, though of course if something in Part 2 changes or doesn't apply then that is noted. Hmm, sounds complicated until you get into the swing of it :o) Chris (OP) your client seems to be looking for more in 'Part 1' as he knows most of what is in 'Part 2' ? JohnW
firesafety101  
#17 Posted : 02 August 2011 17:21:29(UTC)
Rank: Super forum user
firesafety101

John its not the Client being picky it is the project manager being scared of the Client. The job involves removing and replacing wall cladding. The job has been running for 7 months and the chaps doing the work are well familiar with the routines. It is now time for Special panels to be installed, exactly the same method as before but this time a little different hence the new method statement. Our PM wants every single detail in the method statement despite the lads knowing what to do. I believe we should give the installation team some credit for what they are already doing.
JohnW  
#18 Posted : 02 August 2011 21:42:39(UTC)
Rank: Super forum user
JohnW

I can understand 'giving them credit' for a job that is only slightly different from the previous 7 months, but in your initial post you said "are they loosening fastenings, drilling them out or cutting them off? How many men required to handle a sheet of cladding safely", and if they are doing such tasks then seems like it involves manual handling, tools, dust, risks of cuts and eye injuries (hopefully asbestos survey or absence confirmed) etc so sounds like a good candidate for a 'proper MS' to me :o) JohnW
Grant1962  
#19 Posted : 03 August 2011 00:22:21(UTC)
Rank: Forum user
Grant1962

Hi Guys, Everyone will have a different opinion, health and safety is good at that but I tend to use the following subject headings in my method statements: remember- each to their own, just as long as it is safe. Oh and finally only use method statements for onerous or medium to high rish tasks otherwise you'll be spending eternity writing them for every task someone can think of. Method statement number & LOCATION OF WORKS 1. HAZARDS AND ASSOCIATED RISKS 2. PERSONNEL INVOLVED 3. TOOLS 4. PLANT & EQUIPMENT 5. P.P.E 6. MATERIALS REQUIRED 7. SAFETY CHECKS 8. METHOD: 9. EMERGENCY EQUIPMENT / FACILITIES 10. CLOSE OUT / COMPLETION CHECKS 11. ADDITIONAL RELEVANT INFORMATION 12. WASTE DISPOSAL (What was disposed and where etc?) 13. SYSTEM OR EQUIPMENT ISOLATIONS REQUIRED (Sources of energy or fluid flow etc) 14. AUTHORISED BY: 15. CONTACTS: (Key personnel within the project) 16. AUTHORISING SIGNATURE 17. DATE 18. Operatives acceptance signatures
firesafety101  
#20 Posted : 03 August 2011 12:23:03(UTC)
Rank: Super forum user
firesafety101

Thanks everyone, lots of food for thought now.
BigRab  
#21 Posted : 03 August 2011 12:59:24(UTC)
Rank: Forum user
BigRab

Hally wrote:
BigRab wrote:
Anything more than this is just unnecessary paperwork.
I'd normally agreee BUT try telling certain PC's that you won't amend your current Method Statements to THEIR format and you'll find they threaten to take business away. I've had that problem with one who will remain nameless obviously.
I know the problem very well Hally, I am tired of being 'phoned by clients who have been refused access to a site because their paperwork is not in the PC's preferred format. I usually end up burning lots of midnight oil so that they can get on site the next day. So, along with ChrisBurns and steve e ashton and others who are professionals and who agree, maybe we should start standing up to these jobsworths and making it clear to them that WE are the professionals and WE will decide what is necessary. It may leave us a bit impoverished but think of the sense of satisfaction we would have in defending our integrity!
Alan Haynes  
#22 Posted : 03 August 2011 14:48:05(UTC)
Rank: Super forum user
Alan Haynes

quote=BigRab] .......So, ..... maybe we should start standing up to these jobsworths and making it clear to them that WE are the professionals and WE will decide what is necessary. It may leave us a bit impoverished but think of the sense of satisfaction we would have in defending our integrity!
Hang on a mo! - As professionals we can advise what is actually required, and I agree that clients often over egg their requirements [I well remember the Network Rail 50+ page long Method Statements of old], BUT if the Client [or PC as 'quasi client'] decides that he wants more than is strictly necessary, then you give him what he wants. He's paying the bills after all.
13farrar  
#23 Posted : 04 August 2011 10:44:39(UTC)
Rank: Forum user
13farrar

I have just re-written 2 method statements to reflect what the PC's site manager wanted to see before allowing our men to continue. There is no great shortage of detail in our documents, but because he holds the power and can stop our work, he has done. He reckons that an MS should be so written as to describe to a novice or casual onlooker how something is installed or put together in great detail. We have worked for this particular contractor for five or more years with only minor re-submissions required, but this latest site manager is surely taking the biscuit. Apart from downing tools yesterday and my additional man hours, he has now got the company of our Contracts Manager for hours today. Meanwhile, we are happily delivering quality finished work to his colleague's sites all over England from the same starting point, ie our MS and competent committed workforce.
13farrar  
#24 Posted : 04 August 2011 10:46:04(UTC)
Rank: Forum user
13farrar

I have just re-written 2 method statements to reflect what the PC's site manager wanted to see before allowing our men to continue. There is no great shortage of detail in our documents, but because he holds the power and can stop our work, he has done. He reckons that an MS should be so written as to describe to a novice or casual onlooker how something is installed or put together in great detail. We have worked for this particular contractor for five or more years with only minor re-submissions required, but this latest site manager is surely taking the biscuit. Apart from downing tools yesterday and my additional man hours, he has now got the company of our Contracts Manager for hours today. Meanwhile, we are happily delivering quality finished work to his colleagues' sites all over England from the same starting point, ie our MS and competent committed workforce.
Ron Hunter  
#25 Posted : 04 August 2011 11:08:41(UTC)
Rank: Super forum user
Ron Hunter

Establishing task specific competency should be measured before appointment. The client /principal should be satisfied you know what you're doing before entering into contract and allowing you on Site. I do hope that in some situations described here that contractors are sticking to industry standard contract rules and CHARGING for downtime and these additional requirements. Let these jobsworths realise how much this will cost (including the cost of contract termination if they aren't happy) and they may quieten down a bit. You have a Contract which is binding on both parties. To suggest a MS has to be able to be understood by the man on the Clapham Omnibus simly beggars belief. Pitty these people if they're ever put in a position of responsibility at the "cutting edge" of civil and buldings engineering technology!
firesafety101  
#26 Posted : 04 August 2011 11:20:01(UTC)
Rank: Super forum user
firesafety101

This thread is going longer that I first imagined, it is obviously of interest to more than a few. I will say at this point that as I asked the question re the amount of information required I have been on the other side of the fence recently when I poo pooed an electrical contractor's method statement because it was merely a one pager with no detail at all on his safe working or safe isolation procedures. I will never tell an electrical contractor how to carry out his work but this one needed to say more. (The Client that employed the electrical contractor questioned me about my decision so really been on both sides). I have also sent back a one page so called method statement and risk assessment issued by a plumbing contractor who was about to start work installing a full blown central heating system into a home for retired persons, not mention of the gas supply/safety or thermostats controls or anything like that. I do think I was justified in both cases.
Ron Hunter  
#27 Posted : 04 August 2011 11:40:56(UTC)
Rank: Super forum user
Ron Hunter

We could bring this back to the bottom line question: "What is the purpose of a (safety) Method Statement" when in most instances, they are not a legal requirement? Looking at some of the examples above (e.g. installation of wall cladding) I would have to question the requirement. In many instances, specialist requirements for 'method' will rest with the Designer or the Supplier and that information would already be available. In the specifics you mention Chris, is it not in all respects "reasonable" to expect a qualified and competent contractor to comply with EAWR in respect of isolation and live working (accepting that on ocassion live working is necessary). A little knowledge, as we all know, can be a dangerous thing. There is the potential pitfall of assuming liability where we exert influence over methodology of the 'competent' contractor. Balancing that of course, we would all accept that there are situations where we have to stop the work because we see someone doing something manifestly unsafe. But then again, do you ask the contractor to provide you with a written method for climbing up and doen a ladder? I add this to the thread not with the intention of crticising, rather to extend the debate.
13farrar  
#28 Posted : 04 August 2011 11:43:20(UTC)
Rank: Forum user
13farrar

ChrisBurns wrote:
I have been on the other side of the fence recently when I poo pooed a contractor's method statement because it was merely a one pager with no detail at all on his safe working Similarly Chris, we were asked recently to carry out some tricky work at height (tricky to write MS, not tricky to do). The work directly followed another sub-contractor who was in mid flow. When I asked could I see the other subbie's MS, the PC produced a 15 page document which included just THREE lines of actual MS: this read along the lines of: 1. PC to offer clear space to work in. 2. PC to tell us where to do it. 3. We will do it. Needless to say, the other subbie then had to stop work to produce an acceptable MS (the point here being that nobody from the PC had actually read the MS before I did!). Happy days.
firesafety101  
#29 Posted : 04 August 2011 11:49:10(UTC)
Rank: Super forum user
firesafety101

Ron I hear what you say and do agree with some. The cladding operation is quite low risk but working at height so that upgrades the risk. It is the Client that requires the comprehensive MS and I have tried to get the PC to lower his requirements a little, maybe to test the water by providing something less than in the past? I have also tried to advise the PC that they have CDM a bit mixed up as the designer is interfering in as much as he is carrying out the CDM-C role when there is a CDM-C who shows very little interest at all. The designer has asked to see the SWMP, (we do have one) but he is not aware that the Client has not issued the SWMP to the PC? I am adviser to the PC so not really hands on, have to keep some distance.
BigRab  
#30 Posted : 04 August 2011 12:23:51(UTC)
Rank: Forum user
BigRab

Alan Haynes wrote:
quote=BigRab] .......So, ..... maybe we should start standing up to these jobsworths and making it clear to them that WE are the professionals and WE will decide what is necessary. It may leave us a bit impoverished but think of the sense of satisfaction we would have in defending our integrity!
Hang on a mo! - As professionals we can advise what is actually required, and I agree that clients often over egg their requirements [I well remember the Network Rail 50+ page long Method Statements of old], BUT if the Client [or PC as 'quasi client'] decides that he wants more than is strictly necessary, then you give him what he wants. He's paying the bills after all.
Well Alan the PC might well be paying the bills for the actual work but it is usually the contractor who has to pick up the bill in terms of time spent (rehashing RAMS and providing unecessary elaboration) before he can even get onto site. This sort of timewasting elaboration is a sign that the PC's Site Manager (or perhaps their senior management) is not competent in health and safety and are simply back covering.
Ron Hunter  
#31 Posted : 04 August 2011 12:49:29(UTC)
Rank: Super forum user
Ron Hunter

You touch on another issue there Chris. All the tricky, complex or unusual stuff SHOULD be identified by the CDM-C in the Project PCI and all should be answered via the initial CPP? That way, the PC is left in no doubt as to what requires Project Specific methodology, and what doesn't.
firesafety101  
#32 Posted : 04 August 2011 12:58:47(UTC)
Rank: Super forum user
firesafety101

Ron, all well and good but if as I say above the CDM-C is virtually anonymous how can he determine anything. The Designer even issued the PCI to me and that does not specify the exact requirements for info in a method statement, just that they require copies of everything.
Canopener  
#33 Posted : 04 August 2011 13:32:35(UTC)
Rank: Super forum user
Canopener

I’ve followed the thread with some interest. I suggest that the answer to the headline question “Method Statement - how much detail?”, is however much detail is required in order to complete the task ‘safely’. As already alluded to, this depends on the relative risks and the complexity of the task. Much the same applies for risk assessments, and safe systems of work as well. Beware of sacrificing clarity for brevity. I think Ron makes a number of interesting points and he may be right in his suggestion that exercising excessive control over another may not necessarily help to manage the risk any better, and that it may increase the liability on the person exercising the control. If you employ competent contractors, using a robust selection process then there is a reasonable assumption that they will carry out the work competently and ‘safely’, without the need for excessive supervision or ‘interference’. Of course, one of the problems that we have and have discussed on these forums before is that there is no legal definition (that I am aware of) of a method statement and I sometimes get the feeling that some people use MS for something that I would consider to be a SSOW. Again arguably they could be one of the same thing. The other thing I would add is that just because something may not be a strict legal requirement, doesn’t mean that it doesn’t serve a useful purpose; it may or may not. Whether or not a MS is a legal requirement or not, is arguably up for debate. Might they come under ‘systems of work’ in S2 which is not defined within the Act?
Ron Hunter  
#34 Posted : 04 August 2011 14:40:19(UTC)
Rank: Super forum user
Ron Hunter

Going off topic, but does "safe systems of work" really need a definition within the Act? The dictionary definition of "system" should be sufficient?
Canopener  
#35 Posted : 04 August 2011 15:12:50(UTC)
Rank: Super forum user
Canopener

Ron, the reason that I mentioned systems of work (NOT SAFE systems of work), is that the absence of a definition leaves it open to wide interpretation that might reasonably include a MS, and that therefore an MS might well be considered to be a legal requirement. In fairness we have seen debates on this forum a number of times about what is a SSOW, MS etc etc. Arguably that in itself might suggest that some form of definition in itself might be helpful, or at the very least that we can't always reach a consensus of what one or the other is. My quick look at the dictionary of 'system' didn't entirely enlighten me to what a safe system of work was. Secondly, most regs start out with definitions and interpretations, including such things as what construction is with CDM. Reasonably this is unlikey to be the same as dictionary definition. Is it me or have the forums of late become even more niggly that normal?
Ron Hunter  
#36 Posted : 04 August 2011 15:29:03(UTC)
Rank: Super forum user
Ron Hunter

Must be the weather.
JohnW  
#37 Posted : 04 August 2011 19:26:02(UTC)
Rank: Super forum user
JohnW

Just a comment on an earlier posting,
13farrar wrote:
He reckons that an MS should be so written as to describe to a novice or casual onlooker how something is installed or put together in great detail.
Ha, that sort of 'opinion' was mentioned earlier. Surely a project manager would NOT want a novice or casual onlooker doing the work, so why write out an MS for one? I think he doesn't like reading MS's that HE doesn't understand.
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.