Unspoken Assumptions – More on the Client / Consultant Relationship


I wrote some notes last week on the unspoken assumptions that govern (or fail to govern) the relationship between a client and a consultant. Put together, these might constitute a Services Charter that formally documents the way in which Client and Consultant work together.

Better to write these things down than deal with misunderstandings later. Misunderstandings impact on revenue and reputation.

customer supplier

Services Charter

Here’s a further set of clauses that such a charter might include::

Working Practices

Working Time

Professional service time includes all time during which professional staff are adding value to the client through project or assignment work, on the assumption that such time is spent efficiently on relevant issues falling within the scope of the project or assignment during reasonable working hours or agreed overtime.

Such time is not always spent at the client’s place of work, but when time is spent elsewhere this is by agreement.

All working time is recorded by professional staff using the Professional Services Organization’s (PSO’s) professional services software and is subject to review and approval for invoicing by the PSO’s project managers and/or services managers as well as by the client. The PSO’s presumption is that project and assignment time will be invoiced whether on-site or off-site.

Sometimes the client will be unable to verify that time reported by professional staff has been spent in the way each individual has reported (especially if the work is done off site, but also at times when the work is done on site), but the working relationship between the PSO and the client requires a degree of trust on this matter. If the client wishes to dispute such time then he or she may do so (see Disputes).

The PSO’s time recording software records time to the nearest (greater) quarter of an hour in respect of time spent by the PSO’s staff. Thus if 10 minutes are spent, a quarter of an hour will be reported.

For on-site assignments a minimum of two hours is charged for an assignment. This mitigates the inefficiencies (lost consulting time) incurred by the PSO when consultants move between locations, and encourages clients to consider ‘packaging’ issues into assignments of greater duration, whether ad-hoc or project assignments. Doing this is mutually beneficial.

Working time will usually be standard time for the location. This is determined by the location of the client. In general, unless required otherwise, the client’s working conventions (arrival and departure times) will be observed by the PSO. When projects are executed at the client’s location and full days are worked by the PSO’s staff, a full day will be reported and charged when the client’s hours are observed. In these circumstances, if a client specifically asks the PSO’s staff to arrive late or leave early, a full day will nevertheless be reported and charged, unless other terms have been agreed in advance.

Working Conditions


The client is responsible for providing for the PSO’s staff with a safe and clean working environment, with sufficient space made available for the conduct of his or her work. This will usually mean a specific working space or desk where the consultant can work without distraction.

Refreshments and Meals

The client is responsible for providing for the consultant access to refreshments, such as tea, coffee, and water. There is no obligation on the client to provide these free of charge.

The client is responsible for providing for the PSO’s staff access to meals at mealtime, either in the client’s staff restaurant or through recommendation of a local restaurant.

Both parties understand that pauses of a few minutes (sometimes including smoking breaks) are part of working life, and this applies equally to professional work. We believe it is reasonable that pauses of up to five minutes occur every hour, though this by no means confers a right to such breaks in circumstances that make such breaks inconvenient.

The duration of meal breaks will conform to local standards and will not usually be reported as or considered as consulting time unless they are effectively ’working lunches’ with the client’s staff, where serious issues pertaining to the project or the assignment are discussed. If meals are taken with the client and as a consequence the duration of the meal exceeds local standards, the PSO reserves the right to treat the excess time as services time spent with the client.


We generally discourage our professional staff from making personal phone calls, reading or preparing emails that are not relevant to the client’s assignment, or from browsing the internet for irrelevant purposes. However, it is understood that occasional private calls, even calls to other clients, when important, are part of everyday life. When these exceed more than five minutes the client may dispute charges for this time. We generally discourage clients from making unarranged calls to staff when they are not working on the client’s project or assignment.


The client is responsible for ensuring that the PSO’s staff ‘s working environment is quiet and comfortable, and that professional staff are not interrupted or otherwise prevented from making progress with the project or assignment.

Standards of Behaviour

The PSO requires that clients behave respectfully towards its staff, just as the PSO enjoins its staff to behave in a respectful manner towards the client’s staff. Ideally this is a friendly relationship based on mutual respect and common goals.

In this relationship anger, as well as other displays of emotion, is inappropriate. Where there may be cause for anger, we would ask the client to abide by the procedures laid out in Disputes just as we ask our staff to do so.

In situations where the client engages in angry, insultingly disrespectful or verbally aggressive behaviour we ask our staff to request a pause, or to withdraw from the situation. The PSO reserves the right to withdraw professional staff permanently from the project or assignment when this situation occurs frequently or is extreme.

Furthermore, the PSO reserves the right to withdraw from meetings or gatherings or from the working environment if disputes between the client’s staff are unduly emotional.

Standards of Appearance

Unless agreed otherwise consultants will wear business attire. If the client permits, consultants will wear business casual or more informal clothes.


Last instalment on Friday.

Unspoken Assumptions – Do we have the same understanding as our customers as to what consulting means?


I’ve blogged extensively about how the performance of a professional services company might be measured (see PSO Posts). I identified eight different measurements. At least five of these can be affected by your customer’s perception or misperception of your business:

  • Standard Fee Variance will be affected by the willingness of a client to accept a PSO’s most profitable fee rates
  • Utilisation will be affected by the way a PSO and client work together
  • Realisation will be affected by the willingness of a client to accept that a PSO’s work is chargeable
  • WIP Days will be affected by the willingness of a client to accept an invoice
  • Debtor Days will be affected by the client’s willingness to pay

Many aspects of the relationship between you and your customer are defined by contract, but in my experience assumptions by one side or the other are often undocumented, and when it matters, it turns out that they differ.

customer supplier

It makes sense for a PSO to agree in advance the way in which both parties should work together. You might think that these understandings should be part of the Terms of Reference for a particular project, but they are often sufficiently general, and summarise the style and philosophy of a PSO so comprehensively, that there is some value in publishing these terms and agreeing them separately, even in advance of project negotiation. They can be useful during the sales process, clarifying what the buyer is buying and the seller, selling.

A Services Charter fulfils this need and might cover the following areas:




Client Involvement

  • Limitations
  • Client Engagement
  • Communication

Working Practices

  • Working Time

Working Conditions

  • Safety
  • Refreshments and Meals
  • Interruptions
  • Environment
  • Standards of Behaviour
  • Standards of Appearance

Commercial Issues

  • Expenses
  • Travel Time
  • Account Management
  • Cancellations
  • Commercial Issues
  • Issues Arising from Non-Payment

Project Issues

  • Projects (Scoped Fixed Price / Time and Materials / Etc.)
  • Scoped Fixed Price projects
  • Time and Materials projects
  • Time-Hire Projects
  • Outsource ‘Functional’ Work
  • Training
  • Acceptance
  • Project Management



Let’s start with the first three sections of such a Charter:


This document sets out the principles and assumptions that underlie the provision of services by the PSO to a client. It is not a contractual document, but the signature of both parties indicates acceptance that this charter governs day-to-day relations between the parties.


Independence and neutrality

A client should expect honest, impartial, objective advice and guidance from professional staff, who, from the moment of engagement, must have the client’s best interests in mind, whatever the commercial implications for the PSO.

Where the PSO is represented by a team of consultants, advice must be seen as collective, and must be formed in a disciplined and methodical manner, led by a senior member of the team, a project manager or services manager responsible for the assignment or project. Any professional staff holding a different view, must have the option to express this view through the team’s spokesman, but professional staff should not express, nor should a client foster, dissident views in a manner that undermines team work, and team responsibility.

Professional advice is given in good faith in the circumstances. These circumstances will reflect:

  •  Agreed needs of the client
  • Agreed priorities of the client
  • Financial limitations of the project or assignment
  • Deadlines
  • Skills available to the PSO
  • Skills available within the client’s organisation
  • Other factors

These may change, but a complete set of agreed, documented assumptions must always be at hand.It must also be understood that staff are fallible, and that whilst they accept responsibility for mistakes and the correction of those mistakes, they cannot on occasion avoid making them.

However, staff must always identify, admit and correct errors in their work or judgement. In some cases, mistakes and their correction should be seen as part of the working process (such as, in the joint development of systems), and because they are not surprising, plans must reflect the fact that they will occur.

The client will sometimes disagree with the judgement of professional advisers, even when all assumptions are agreed and there are no disagreements as to fact. In this case, whilst registering disagreement, a professional adviser should continue to advise the client and to accept the client’s judgement, though in some extreme cases the adviser may choose to withdraw from the project or assignment, if a reasonable case can be made for doing so.

In giving advice, staff do so against a background of stated assumptions.


By default, a professional adviser is never an executive within a client’s organisation, and should not take responsibility for the client’s staff or their work unless (as perhaps in the case of interim management) he has specific, published authority to do so.

A professional adviser is never the legal representative of the client and is not responsible for statements, verbal or financial, that have legal repercussions for the client.

A professional adviser advises, and does not act in the place of any of the client’s staff, unless this is specifically agreed.

Client Involvement

Client Engagement

Projects and assignments can go wrong if the client does not engage deeply with the project or assignment. A professional adviser does not work ‘for’ the client, but more often ‘with’, the idea being that knowledge will be transferred to the client. Where the appropriate level of engagement by the client is missing, and if this raises risks for the project or assignment, the PSO will notify the client.

At best, a PSO’s professional staff can play the role of energetic, persuasive advisers, but final responsibility for the success of a project or assignment will depend on the client.


It is essential that expectations of the project and assignment are synchronised not only between the PSO’s project team and the client’s project team, but in depth in the client’s organisation, especially when end-users’ opinions, reactions and acceptance are required.

It is particularly essential that in the case of training the client clarifies for all trainees the objectives of the project, the limits to its scope and the role of the PSO in the process of the project or assignment.

Communication should be in unambiguous written form whenever possible.


More next week.

Looking For a Professional Services Management System?


I’ve posted several blogs in the last few weeks about measurement in Professional Services Organisations (PSOs), but in a sense they’ve also been about systems, since it is rare that a PSO can obtain all the measurements it needs without systems of some kind of another.

By systems, I mean all the means of recording, communicating, aggregating, calculating and reporting that together constitute the technical and human aspects of the task. I don’t necessarily mean that computer-based software systems sit somewhere inside this network of media, but for all practical purposes we might as well assume that.

which way to go

So, what kind of software systems support the kinds of measurement that I have recommended?

Well, before I can answer that question I must confess bias. As the designer of a software system expressly devised to enable the measurements I’ve described, I’m bound to be describing characteristics of time@work, the system I’ve designed. However, I’ll try to do so in ways that are partially neutral, in that other software systems (and there are many competitors for time@work) may very well share some of these characteristics.

For more about time@work see www.systemsatwork.com.

I should also point out that to my mind, at least, there is a distinction to be made between a financial system, which provides statutory and management accounting information for companies and groups of companies, and Professional Services Management systems, which provide tools for the management of professional staff.

First, I’ll begin by introducing some more general requirements of a Professional Services Management system.

General Requirements


Some PSOs are very simple, but many, indeed perhaps most, are not. Sometimes even the smallest PSOs are complex. In my experience complexity is a more commonly found feature of PSOs than of comparably sized manufacturing or distribution companies, for whom products, prices, and methods of delivery are relatively standard.

If even a moderately complex PSO encounters financial performance problems and it becomes useful to analyse the organisation using such measures as those I’ve described in my posts, then it may well be useful to analyse them by a number of different criteria, chasing down problems by looking at these measures from a variety of different angles, slicing and dicing the data to get to the underlying problems.

For example, issues such as utilisation don’t always affect all business streams or geographies equally. In addition, issues such as realisation don’t always affect all your clients, or client types, or client sectors equally. The same goes for all the other measures.

Because of this it is essential that your system should be capable of analysing data (time, expenses, invoice values, forecasts, etc.) using a number of user-definable criteria. What could these be?


  • Date
  • Day of the Week
  • Week
  • Timesheet Period (usually a week)
  • Month
  • Accounting Period
  • Quarter
  • Year


  • Activity (e.g. Meeting, Researching, Consulting, etc
  • Location (e.g. At Home, At the Client, At the Office, etc.)
  • Role


  • Employee
  • Employee Department/Cost Centre
  • Employee Business Stream
  • Employee Company
  • Employee Grade
  • Employee Position
  • Employee Type (Internal/External/etc.)


  • Client
  • Client Department/Cost Centre
  • Client Business Stream
  • Client Sector
  • Client Type
  • Client Duration


  • Client
  • Project
  • Project Department/Cost Centre
  • Project Business Stream
  • Project Company
  • Project Location
  • Project Type
  • Project Duration
  • Project Sector


  • Task
  • Task Type

These are just some of the ways you may want to analyse data. In reality, every PSO is different and it is likely you can imagine dozens of other ways you might want to analyse your organisation’s performance. Your system must allow you to define these dimensions for yourself.

Multi Company

If your PSO isn’t already a multi-company organisation, consider very carefully whether it might become so. If it does, you would probably want to treat your entire team of professional staff as one group, one pool of resources. And if so, then the system you use should enable this in ways that are completely transparent to your staff, who should record time in their timesheets without being aware of any separation of companies, employees and projects.

This surface simplicity must in fact conceal some complexity. Multi-company means:

  • That each employee must belong to one and only one company, so that appropriate accounting transactions (for example, expenses for reimbursement) can be sent to the right accounting ledger
  • That each project must belong to one and only one company, so that appropriate accounting transactions (for example, invoices) can be sent to the right accounting ledger
  • That the system must be capable of holding multiple charts of accounts, one for each company whose data are held in the system
  • That the system must be capable of managing more than one base currency, potentially a different base currency for each company whose data are held in the system
  • That the system must be capable of detecting inter-company transactions (such as when an employee of one company records time on a project belonging to another), and of generating the appropriate accounting entriesMulti Currency

Even if your organisation is comprised of a single legal entity you will probably need to manage multiple currencies:

  • You will need to calculate values in the your company’s base accounting currency
  • You may need to calculate or record values in a separate transaction currency, such as fee currency if your fees are stated in a foreign currency, or expense currency if you incur expenses in a foreign currency
  • You may need to calculate values in your client’s invoice currency. For example, your client may wish always to be invoiced in EUR, and you may need to convert your fee values or the expenses you have incurred into EUR.
  • You may need to calculate values in your own corporate currency, which may differ from your accounting currency. Especially when your organisation comprises two or more companies with two or more different accounting currencies, you will probably want to report all values together in a common reporting currency.

Multi Language & Flexible Terminology

Consider whether you will want to deploy your system in more than one language. Not all systems do this easily. It is important that if they are capable of this they hold all linguistic terms (messages, labels, and other textual items) outside program code, so that they can be modified easily. Ideally, all terms should be available to you for editing so that you can make your own substitutions for Client, Project, Task, Employee, etc.


In my experience, PSOs are more likely to break their own rules than most kinds of company. Whether the motives for this are laudable – the need to be commercially creative – or whether they reflect disinclination in general to be bound by rules – more flexibility is needed in software for PSOs than for most other kinds of organisation. Your software, therefore, must be very flexible. This means that it must adapt itself to new procedures, or new analytical requirements (as well as changing statutory regulations) without too much difficulty.

There is no software in the world which will do this automatically, but you must make sure that yours is at least capable of change. It may do exactly what it says in the manual, and this may be exactly what you need and all that you need it to do now, but beware of the commercial creativity to come.

What kinds of flexibility should you look for?

  • The possibility of multiple workflows
  • The possibility of multiple document types with differing characteristics: timesheets, expense forms and other forms, and different types of each form
  • The possibility of additional analysis
  • The possibility of multiple rules for fee rates and costs in any number of currencies
  • The possibility of terminological change
  • The possibility of calculating new values and measures
  • The possibility of creating new reports easily
  • The possibility of designing multiple invoice and other document formats easily

No system is unlimited in what it can do. In fact, systems are implemented precisely in order to impose discipline and control, and to restrict creativity. They are sometimes as much about limiting freedom as offering it. The most flexible invoicing medium in the world is a blank sheet of paper, but this is no strong recommendation for Word as an invoicing system.

Bear in mind also that flexibility should not be achieved through program change, since this will make it hard for you to keep up with new versions of a system (and we are assuming throughout that any system you choose is a commercially available packaged software system). It is important that flexibility be achieved through configuration or parameterisation. 

Specific Requirements


Every PSO is different. Even PSOs within the same sector (be they lawyers, engineers, accountants, consultants, etc.) differ, sometimes markedly, from each another. They differ in the way in which they record time, the structures (clients, projects, tasks, activities) against which they record time, and they differ in the rules they apply when validating time entries and in the periods they divide their calendars into.

What sort of flexibility should you look for?

  • The possibility of specifying your own ‘unit’ of time entry. Lawyers traditionally divide time into six-minute units. Others report by quarter hours, or hours or even days.
  • The possibility of specifying your own timesheet periods. Some PSOs demand daily timesheets (though these are hard to chase), some weekly, some fortnightly and some monthly. Best practice for most PSOs is weekly, but whether you choose to start the week on a Monday or any other day must be within your realm of control. You also need to be sure that you can close an accounting period or month rapidly, splitting the final week of the month appropriately.
  • The possibility of recording time at Project level, or at Project and Task level, as required by the Project.
  • The possibility of defining (and switching on or off at least by Project) additional fields for free form or selective data entry. These might be used for any number of purposes such as Activity, or Location. It is an extra bonus if the values associated with these can also be limited by Employee or Project.
  • The possibility of including or excluding a field allowing staff and their line managers to specify whether work is chargeable or not.
  • The possibility of multiple calendars, defining, if necessary for each employee, the length of the working day so that the entry of standard working hours can be enforced, if this is a requirement.
  • The possibility of entering unlimited free form notes against time entries with selective enforcement of notes.
  • The possibility of validating time entries using various rules, to prevent incorrect entries or the entry of time beyond specified limits.
  • The possibility of limiting projects available to an employee so that he or she may select only from an approved list.
  • The provision of easy to use project search tools so that an employee can find his or her most recent projects and any other specific project easily.
  • The possibility of pre-filling a timesheet with confirmed diary entries.
  • Flexible workflow possibilities so that timesheets can be routed to line managers or other managers (conditionally) for authorisation.
  • The option to calculate multiple values for each entered timesheet cell. These might include Standard Fees, Actual Fees (local and/or foreign currency), Standard Working Cost, Standard Availability Cost, Standard Project Cost, Cross Charges, etc.
  • The option to approve time by Project view rather than Timesheet view, so that Project Managers can see all timesheet records that have been entered against their projects, irrespective of who has recorded the time.

Expense Forms may be simple, or complex, according to the activity of the PSO. A simple domestically oriented PSO needs far less complexity than a multi-national internationally oriented one.

Some will need some, and some will need all of the following features:

Expense Forms

  • The option to create a number of different forms with different characteristics, these including, different static data entry fields (Project, Task, Activity, etc.), and different value entry fields.
  • The option to specify validation rules for data entry, to enforce expense policy.
  • The option to specify different authorisation workflows for each form.
  • The option to make workflow conditional on aggregated or specific row values in a form.
  • The possibility of managing multiple tax rates (differing VAT rates, for example, for multi-national PSOs).
  • The possibility of specifying values in many currencies, whilst converting these into local currencies for reimbursement, and potentially further currencies for re-invoicing.
  • The possibility of automating, and overriding, the provision of an exchange rate.
  • The possibility of deriving account codes from static data fields without an employee having to be concerned with these.
  • The possibility of arranging pre-approval for travel expenses.
  • The option to specify whether an expense is rechargeable to a client or not.
  • The option to manage value-based expenses, per-diem (daily allowance) expenses and mileage-type expenses separately or on one form.
  • The option to import credit card statements in a variety of formats and present these as expense forms for completion by employees.
  • The option to import recharges to clients such as photocopier expenses, telephone expenses, etc.
  • The option to record supplier-invoiced expenses such as travel tickets.
  • The option to import expense data from suppliers such as travel agencies, online retailers, etc.
  • The option to attach scanned images and documents to expense forms
  • The option to calculate values such as ‘carbon footprint’ in respect of specific expense types

PSOs differ enormously from one to another in the way they handle invoicing. For some it is a simple matter of invoicing work in progress at full value, for others there is a need to record discounts and write-offs. Others invoice in advance, or based on milestones, or percentage completion, or invoice regular values every month or quarter or year. Some combine expense and time invoicing. Others don’t.

Your needs may also change from time to time. You may at some stage need some, if not all, of these options and possibilities.


  • The option to create time and materials invoices based on work in progress, with specified deferrals, additions, discounts and write offs.
  • The option to track discounts and write offs against original values for the purposes of management (realisation) reporting.
  • The option to combine time and expenses on a single invoice or to keep time and expense invoices separate.
  • The option to invoice in advance, and afterwards allocate work in progress to advance invoices.
  • The option to invoice based on percentage completion.
  • The option to invoice scheduled values periodically.
  • The option to reverse invoices of any kind, fully or partially.
  • The possibility of generating all accounting entries from the invoicing process.
  • The option to separate the booking of revenue from the booking of invoices.
  • The option to format invoices in a number of different ways, at a detailed or summary level.
  • The option to produce ad-hoc invoices and credit notes of any kind, without reference to time or expenses.
  • The option, in all invoice types, to amend any textual item.
  • The option, at invoicing time, to recalculate accounting or fee values based on latest specific exchange rates.
  • The possibility of invoice authorisation workflow.
  • The option for project managers (and sometimes customers) to approve time and expenses prior to invoicing.

I assume that full financial budgeting, including total forecast revenue, total budgeted staff and overhead cost, is managed in your Financial System.

Planning and Budgeting have both an active and a passive aspect. They can be used actively to achieve optimal utilisation through the intelligent scheduling of project work, using skills, availability, cost, and preferences as inputs to the process. In addition, they can be used passively for reporting actuals against plans, and for the determination of recognisable revenue.

These are some of the planning and budgeting options you might look for in a Professional Services Management system:

Planning & Budgeting

  • The option to hold anticipated time, expense, fees and costs for a project, optionally at project, task, activity, role and employee level, so that actual values may be compared with plan.
  • The option to import a plan from an external project management tool such as MS Project.
  • The option to hold multiple plans and revisions.
  • The option to hold skills, preferences, and other attributes, against employees so that staff may be scheduled appropriately for specific work.
  • The option also to review staff availability during scheduling.
  • The option to plan at possible as well as firm level.
  • The option to integrate planning with diary systems such as MS Outlook.
  • The possibility of publishing scheduled work and availability across the entire PSO.

Professional Services Organisations borrow staff from one team to use on another’s project. How should that be managed?

Efficient deployment of professional staff in a diverse PSO often means one company, business stream, department, or team borrowing from another if utilisation is to be kept high, and if clients are to be satisfied. Each team will inevitably staff a project from its own resources by preference, but if skills are in short supply, they must look elsewhere. This is one reason why visibility of availability, skills and experience across the entire organisation is important.

Conversely, a team with time on its hands will want to promote its professional staff and ‘sell’ them to others.

However, these issues create challenges in terms of revenue sharing, costing, and motivation. These need analysis.


A perennial issue in the management of PSOs is that of responsibility. There is the ‘line management’ responsibility of team leaders which includes:

  • Responsibility for the day-to-day deployment of a team of professional staff
  • Responsibility for the personal career development of the team
  • Responsibility for the profitability of the team

And there is ‘project’ responsibility:

  • Responsibility for the staffing of a project
  • Responsibility for the profitability of a project
  • Responsibility for all commercial decisions (invoicing, etc.) associated with a project

In most organisations, these responsibilities overlap, but they can also be in conflict unless there are clear rules for the resolution of issues with respect to inter-team charging. As PSOs become more commercially driven and team leaders and managers are rewarded according to the profitability of their team these conflicts can become serious.

Let’s look at an example:

Let’s suppose there are two teams, led by A and B. Each team leader employs a number of staff as follows:

  • A employs AA, AB and AC
  • B employs BA, BB and BC

In a simple world, each team executes and invoices projects using its own staff. Budgeting and forecasting are relatively simple, and there are no cross charges.

But what if B sells a project that requires the skills of AC?

In this case, he or she must borrow AC from A.

But how is this to work in terms of gross margin (on which the bonuses of A and B may partially depend)?

  • Should some of the revenue that belongs to B be passed back to A?
  • Alternatively, should some of the cost that belongs to A be passed on to B?

There are no entirely right answers here, but my own preference is for the second option, for several reasons:

  • In a commercial organisation it is the obtaining of revenue (or rather gross margin) that should be rewarded most clearly
  • In a commercial organisation it is the incurring of loss that should be penalised most clearly
  • People should not generally be rewarded or penalised for circumstances that lie outside their control

Let’s consider what would happen if our cross charging rule were that A should receive 85% of the revenue earned in respect of AC’s work on the project.

When B comes to A to tell him about the project, which hasn’t yet started, he’s optimistic:

‘You’re going to get good money for AC. I’ve negotiated a rate that’s higher than the usual. So you’ll probably end up getting more than you would if you’d sold him yourself. Sadly, I’ll only see a small part of that revenue myself, but, sadly, those are the rules.’

Of course, as in all cautionary tales, things don’t work out well. What B didn’t really tell A was that this is a fixed price project, and B has made some dodgy assumptions about the number of days the project will require. When it comes down to it, the revenue is spread more thinly than planned across the days that AC has given. When A receives his share of the revenue, it doesn’t even cover AC’s standard project cost.

‘I could have sold AC on some other projects and made more money,’ he complains.

However, this is just one of the problems. When A complains to B that he was expecting more revenue, he points out that the project has gone wrong through poor project management, and poor estimating. Why should he be penalised for that, since it was B’s team who were responsible?

B has to admit that some of this may be true, but he counters with a complaint that AC wasn’t actually as experienced and suitable as A had suggested, and so some of the problems were AC’s fault, not his team’s.

And so on.

Not all of these problems are resolved by looking at it another way, but some are. If A charged a fixed price for AC’s work, regardless of the revenue associated with the project, then at least the first kind of problem is averted. But what should that price be?

Full fee rate (B’s notional or actual fee rate for his project) would seem too high, since it would remove any incentive for B.On the other hand, standard project cost would seem too low (let’s suppose that AC has a standard project cost of 450), since it doesn’t provide much of an incentive for A, and provides him with no reward for the ‘risk’ of employing staff (and incurring overheads to do so).

In fact, assuming that appropriately skilled staff can generally be found in one team or another, a clever team leader wouldn’t bother to employ anyone at all. He would simply buy the time of his colleagues at standard project cost.

Of course, there are reasons why this would be a foolish policy. If you ‘own’ your own staff you may make your own decisions about how to deploy them, how to reward them, and you have a much greater chance of running successful projects if you have at least some influence over, and have earned the loyalty of the staff you deploy.Risk must bring rewards, and so the risk of running a team must be reflected in a margin to be charged to other teams when they need to borrow your staff. You should be rewarded for having recruited them, trained them and obtained their loyalty and for the risk that you face that they may be idle and unprofitable.

In the next post, I’ll address the question that arises from this: how should cross charges be calculated?