How can I see my team's progress on a proof?
If you are managing a project, it is very useful to know when they have finished work and how the team is getting on with their work - so that you can control your schedule and budget effectively, but also so that you know when you can start specific jobs like collating markup.
Futureproofs provides a simple way to see, for every proof, how your team is doing. On your dashboard, hover over your project in the list and click the Details button. (You will only see this button if you have the Owner role!)
The details will automatically show your proofs, with the most-recent proof already expanded as shown here.
There are five columns of data.
- Last page
This is the last page of the book that each team member viewed, and shows you how far through their work they are. However, remember that some people go through a project twice or even more often before they are done!
This shows how many corrections this user has entered for this proof, and may help you establish how much work will be needed by your designer before you can see a new proof set.
This shows how many queries this user has on this proof that contain unread messages.
- Time spent
This is the time each team member has spent working on this proof. (This will not be the same as the billable hours for freelancers because of separate tasks like reference checking, but does give an indication of how they are getting on.)
Indicates whether or not each team member has marked this proof as complete using the checkbox in the markup tool. (If you have the Proofreader role on a project, this will be the only column that you see - so that you know when to start collating markup onto the master proof if you've been asked to do this job.)
What does it mean that a proof is 'done'?
In this report, Done means that that team member has checked the Complete box in the markup tool. Ideally, this would mean that they have read through the entire proof and made any necessary corrections.
However, they might not have actually read every page. In some cases, there may be sections that a particular team member need not check (e.g. in multi-author works). In other cases, they may prefer to read the whole project through once before going back through and making corrections. In both these cases, simply showing whether they have read every page would not be the same as being 'finished'.