Tracking work that is tracked elsewhere
I'm a consultant. I work with a number of different clients, on a number of different projects. Each client will have its own set of tools for tracking progress on various tasks. This might be a wiki, a spreadsheet, a ticketing system, or a kanban or other card board.
To take a real example, I have a client with whom I have the commitment to write the interface code that talks to another application, replacing dummy code that is already written. This is a task which is tracked on their kanban board, and will be reviewed daily by them, and every day that I work for the client.
It seems to me that in order to be fully aware of all my options whenever I have discretionary time, I need to see the next action on this as an option. So I track it, and the many hundred other open loops for all my clients.
The trouble is this is quite a lot of open loops, and it's also duplication because I need to keep the client's system up to date too. So there's double entry of data, which seems inefficient.
However, this is work against which I have made a commitment, and if I'm not with a given client for a few days or weeks I need to see this information in my own system. So I persevere. It just feels a bit clumsy.
The problem is that as a consultant I might come up with thirty or more projects in half a day's work. Some of these will be picked up by the client, but I need to keep track of them. Having a project in my own GTD implementation for each of these for each client is a vast amount of data. Maybe that just models the amount of stuff I have to manage on a day to day basis?
Any ideas? Do you think I'm going about this the right way?