The first class session  will cover some of the principles of preparing and responding to a client's project brief.

The meetings with the client during the second week will enable each group to define and scope the consultancy project for the preparation of a project proposal to the client and for submission to the unit convenor.

The project proposal must have at least the following features included within the page limit of 2000 words or approximately 5 pages. 

• A clear statement of the project objectives.
• A clear statement of the way in which the group intends to carry out the project.
• A work plan showing the milestones to be achieved during the project.
• A summary of the outputs to be delivered to the client.
• A notional Business Plan and schedule of putative progress payments.

• Each group will be required to give a 15-minute presentation of its Project Proposal to the class.  The purposes of this are to provide initial practice in presentation skills for the final presentations to each group's client at the end of the unit, and to receive feedback from other groups on the communication and feasibility of the project.

  The marking criteria and weights for the Project proposal are set out in the table below:

  Clear statement of the project objectives

  2

  Clear statement of the way in which the group intends to carry out the project

  2

  Work plan showing the milestones to be achieved during the project

  2

  Summary of the outputs to be delivered to the client

  2

  Notional business plan and schedule of putative progress payments

  2

  TOTAL

  10

Report Length 3000 words and Group Presentation

You will have to show what you have done individually as a contribution to this report.

This assignment is the first step in completing your group's project - its purpose is to explore and document the broader context of the issues and concerns of your client in the project that the group will be doing for them.

Each group will be required to give a 15-minute presentation of their context reviews to the class.

This context has an internal and external component. The context report it is to bring you "up to speed" in terms of what an experienced consultant would be able to understand from the brief, from their knowledge of the policy or legal context, why the organisation wants this work done;  where it fits, and expertise from other projects.  The work done is not sent to the client. 

You will be developing an understanding of the context in which the organisation works, its culture and the significance of the project to the future work of the organisation/ client. You will need to understand the regulatory or resource barriers, so that you can best collect information and formulate recommendations within the organisations constraints. You also will want to look beyond the organisation to what is happening in other jurisdictions and countries to benchmark the current practice and to stimulate creativity or innovation.

Clear and appropriate identification of the context for the project - within the client's organisation and beyond.

3

Contextual issues related to the client's business are analysed and evaluated.

3

Contextual issues related to best practice outside the client's organisation are analysed and evaluated.

3

Clear linkage from outside best practice to the needs of the client's organisation with respect to the project.

3

Quality and substance of the presentation to the class of the "Context Review Report".

3

TOTAL

15

 Draft of final report submitted to unit convenor and mentor for review

Please see Final Report Expectations under Assignment 3 

Note: It is up to the group to decide who is going to integrate the various writing styles and contributions into a well edited cohesive report. We expect good English and spell check, well laid out draft reports.  

Evidence of  individual contributions to the report in the log books submitted

Each Group will make their cleint presentation summarising key findings of the report and the approach undertaken to reach the objectives. 

Feedback from class members and staff is used to improve the final presentation for the client. Please see guidlines for this presentation under assignment 3. This activity is not marked

Final (darft) reports) should be sent to the client Monday 9th June to check the report is satisfactory to be submitted. 

Final written Report printed copy provided to the client (and electronic version)

• Report includes an Executive Summary and appendices with data and further information for th eclient's use

Report presented to unit convenor

Log book submitted from each student

Record of individual contribution to final repost submitted

Final Report Expectations

The project report must have at least the following features included within the page limit. Additional supporting material of a technical or other nature should be attached as Appendices to the report proper and bound with it. The report should address all of the objectives determined in the project proposal, and the following format is suggested:

• A statement of the project objectives.
• A description of the way in which the group carried out the project.
• A summary of the findings in relation to the objectives.
• Quantitative data should be provided where appropriate.
• Discussion of the findings. (You may present the discussions of different aspects after the findings on each, or reserve the discussion until after all of the findings have been set out).
• Conclusions and clearly defined recommendations to the client.

Guidelines for the presentation of the bound report (if required)

• The title page must include the title of the Report, the year, the names of the group members, and any other information necessary for cataloguing the report in a library.
• The report should be of a quality suitable for presentation to the Environmental Manager (or equivalent) who may refer it to the CEO of your client: professional appearance with appropriate high-quality (colour) graphics to illustrate the key points, appropriate binding.
• The Executive Summary should not exceed one (1) page, be quantitative and informative, and include the main findings and recommendations to the client. It should be bound with the report after the title page.

A check list for the bound report

1. Appearance

• Is aesthetically attractive (far more important than many people realise!)
• Is font too small / large and therefore unattractive to read?
• Is there good use of boxes, space, colour and graphics throughout?
• Are graphics clear and do they show the important features?

2. Structure

• Is it well laid out, and with a clear flow of logic?
• Does the report avoid confusion between summary and conclusions?

3. Style

• Is the report written in language appropriate for CEOs, using only English and avoiding technical and academic jargon (except where necessary, e.g. plant species)?
• Has the report been checked for spelling and grammatical errors (can be both irritating and distracting).
• Are references complete in accordance with the GSE Guidelines?
• Has attention been given to the details, e.g. Spelling of plant names, technical terms?

4. Content

• Is the status of the issue clearly summarised? (Why do the project?)
• Does the report contain all the information needed for the decision-makers to proceed to the next step?

5. Discussion

• Is the argument compelling?
• Is there any poor writing that hinders comprehension?
• Is writing verbose and passive?
• Is rationale well presented?
• Is the discussion strong, looking at issues just beyond the sites?
• Is there reference to best-management practices?
• Are the arguments and comparisons all coherent?
• Does it provide a clear basis for subsequent recommendations?

6. Recommendations

• Are the recommendations precise, strong and focussed?
• Will they allow the client to move to the next step in the process without unnecessary replication of the work done?

A check list for the Executive Summary

1. Layout

• Is the layout attractive and readable?
• Is the layout imaginative to reduce words and clearly present the main messages?
• Is there good use of headings to separate background from findings and recommendations? This format means that the CEO does not have to go looking for an obscure message.

2. Findings

• Is the message clearly conveyed?
• Does it clearly state the task to be addressed, the approaches, the results and the recommendations?
• Is there any unnecessary material?

3. Recommendations

• Are the recommendations precise, strong and focussed?
• Will they allow the client to move to the next step in the process without unnecessary replication of the work done?

The marking criteria and weights for the Project Report are set out in the table below:

Executive summary

5

Clear statement of the project objectives

5

Clear description of project context

5

Clear linkage from outside best practice to the needs of the client's organisation with respect to the project.

5

Clear presentation of the project findings

10

Conclusions based on findings

10

Useful recommendations for the client to act upon

10

TOTAL

50

 Group presentation to the client

Each group will be required to give a presentation of their findings to the client at a time to be arranged.

The presentation will be assessed by GSE staff with regard to the assessment from the client.

The format for the session will be:

• a 20-minute presentation by the group
• 10 minutes for questions and discussion with the client.

However the client might choose to ask questions during the presentation

The presentation may be extended to discuss the findings, recommendations and their implications.

 Guidelines for the oral presentation of the report

• The group should plan to use PowerPoint slides and a data projector for the presentation.

The availability of the necessary equipment should be arranged with the client and / or the GSE office prior to the presentation.

• Remember to have an appropriate amount of information on each slide (not too much) and to choose a style and colour scheme that is easy to read on a large screen - check this!
• The content (including graphs, tables and diagrams) in the presentation slides should correspond with those in the bound report and be easily correlated with them by the audience.
• Avoid simply saying what is on the screen - certainly do not read from it! It is very effective if what is being said is a focussed commentary on what is on the screen which is in turn a sharp summary of the main points of what is being said.
• The group will have the opportunity to rehearse the presentation before that to the client when they present to the GSE staff and other groups. This is the time to ensure the timing is right and the visual aids are clear.

A check list for the presentation

• Good introduction of team and clarity of purpose?
• Presentation placed in context at outset?
• Good cover and explanation of the issue and findings?
• Case well argued with good graphics, etc?
• Alternatives/options presented and well argued?
• Recommendations carefully placed in the context of findings?
• Good cover of cost implications of recommendations?
• Integrated use of anecdotes / humour etc to maintain interest / attention?
• Good use of presentation technology?
• Effectiveness of presentation material?
• Clear letters and diagrams, unclutteredd slides, text visible against background
• Well-balanced use of time?

The marking criteria and weights for the Final Presentation are set out in the table below:

Professionalism of team

Project team well presented and suitably dressed

1

Project team introduced clearly and roles identified

1

Content of presentation

Clear statement of the project objectives

1

Clear description of project content

1

Clear description of the methodology for the project

1

Clear presentation of the project findings

3

Conclusions based on findings

1.5

Useful recommendations for the client to act upon

1.5

Style of presentation

Well paced and completed in time

1

Quality of overheads/slides

1

Easily understandable

1

Manner and vocal quality

1

TOTAL

15

Logbook and Reflection on Practice

An electronic version of a logbook will be provided for each member of the class in the first session.

Each student in each group is required to maintain this as a diary of work carried out and record of the "chargeable" time (excluding travelling time) for each task.

The logbook approach allows a fuller simulation of the work of a consultancy team that really has to track the chargeable time for each task to enable accurate invoicing and personnel payments.

 The time is indicative of the quality of excellence you should be pursuing in all aspects of the unit and in particular in the final written report and presentation to the client for whom your group is doing the project.

The introduction of the logbook system arose out of some discontent in the past among students who found themselves working in a group where there was unbalanced group participation. The logbooks give students the opportunity to ensure all group members are contributing as planned. To be meaningful, therefore, the logbooks will need to be submitted on at least two occasions during the semester and shared with other members of the group.

Professional reflection on the experience of the work

The important issues with regard to the logbook are whether or not the other members of the group agree or disagree with the times recorded and are satisfied that the effort from each member is fair. Unsatisfactory work contributions can occur in a real-life consulting practice and the issues can only be resolved by decisive action on the part of those adversely affected.

Where members of a group are not satisfied with the effort of another group member, they must act immediately. There is no point in waiting until the end of the semester, nothing can be done at such a late stage. The logbook should be noted accordingly.

Alternatively, if there is a desire to avoid immediate confrontation within the group, the matter can be brought to the attention of the unit convenor by the group leader. In regard to the latter course of action, however, it needs to be appreciated that no meaningful action can be effected if the group member in question is not faced with the issue.

The other value of the log book is that it enables you to assess the real time each section of the work took, so that when preparing future budgets you have a more realistic appreciation of where time is spent. 

You will be expected to assess the input in clusters of work and reflect on the issues about the effectiveness of the use of time. A 2 page reflection on practice is required that assesses:

• the requirements to complete tasks 
• lessons learned in undertaking the project in regard to professional disciplinary skills;
• lessons learned in regard to how the group work was managed and what has been learnt about the self in the group process and professional work.