Skip to content
Back to the blog

By FormatStack Author

How to Estimate InDesign Revision Work from an Annotated PDF

Before quoting an InDesign revision round, turn the marked-up PDF into a list of approved edits, layout changes, and open decisions. A worked example shows how to estimate the time.

Two catalogue proofs with 24 comments each. One shows small text corrections. The other shows text reflow across pages and a replacement photo.

Two marked-up PDFs come back with 24 comments each. One mostly contains short wording corrections. The other includes a longer paragraph that pushes text across a spread, two image swaps, and conflicting instructions about a caption. If you quote both jobs by comment count, you miss the work that makes the second one harder to schedule.

Before you give a client a price or commit your desktop publishing team to a deadline, estimate the work behind the annotations. Start with the approved changes, check what they do to the layout, and set aside time to verify the new proof.

1 Count the changes your team can actually make

Open the annotated PDF alongside the matching InDesign source. Confirm which proof was reviewed, which source file should be updated, and what the client expects back. One revision round might include an updated InDesign file and a review PDF. A request for a separate print-ready PDF or a second proof after further feedback changes what you need to schedule.

Read the annotations with a simple question in mind. Can a production operator make this change with the files and instructions they have today?

  • Count repeated requests for the same change once. Record every location if the request applies in more than one place.
  • Keep questions and conflicting instructions separate from approved edits. Assign someone to obtain a decision.
  • Identify missing assets or copy. “Use the new photo” is a pending item until you have the approved file.

In our example, four of the 24 comments repeat requests already on the list. Two need client decisions. That leaves 18 approved requests you can estimate now. If comments arrived in several files, start with our guide to merging PDF comments from multiple reviewers.

2 Check how far each change reaches

A price correction that fits in its existing text frame is usually a local edit. A replacement paragraph in a threaded story can affect later pages, even if the reviewer left a single comment. An image swap can be straightforward if the approved asset has the same proportions. A different crop may require more work around the caption and nearby text.

Group the approved requests by what they require:

  • Local text edits. Short replacements, insertions, or deletions that fit the existing layout.
  • Edits that affect layout. Longer copy, tighter table cells, changes to threaded text, or one instruction that affects several placements.
  • Asset changes. Replace approved images or graphics and check their crop, placement, and relationship to nearby text.

Scan the affected pages before assigning an edit to a group. The same copy change can fit easily in body text and require layout work in a narrow table cell. If one instruction applies to five separate placements, estimate the work to update and check all five.

3 Add setup and final proofing to the estimate

Start with time records from a similar job if you have them. If you don’t, time a few representative edits on a working copy. Include finding the right passage, applying the correction, and checking its immediate effect. Sample the awkward edits as well as the easy ones.

Then add work you do once per round. Intake includes confirming the files and reviewing the comments. Final QA includes checking the revised layout, exporting a fresh PDF, and opening that export. InDesign’s Preflight panel can report issues such as overset text under the active profile. The exported PDF still needs a visual check. See Adobe’s Preflight instructions and our InDesign revision checklist.

Here’s one way to estimate the 18 approved requests. The timings are illustrative. Substitute your own when you quote a job.

  • Intake and file check. 15 minutes once per round.
  • Local text edits. 12 edits at 1–2 minutes each, for 12–24 minutes.
  • Edits that affect layout. 4 edits at 4–7 minutes each, for 16–28 minutes.
  • Asset replacements. 2 replacements at 5–10 minutes each, for 10–20 minutes with approved files available.
  • Final layout check and PDF export. 20–30 minutes once per round.

Total production time for 18 approved requests is 73–117 minutes.

This gives the team roughly 1¼ to 2 hours of production work. If you need to price the job, use the rate or pricing method you already apply to revisions. Keep any extra allowance tied to a specific uncertainty, such as a page that may need to be rebuilt after the new copy arrives.

4 State what can change the quote or delivery date

Production time and turnaround are separate. Two hours of editing and QA may fit comfortably in a day. A caption decision due tomorrow can still hold up the finished proof. Tell the client which work can proceed and which items need an answer before delivery.

A short handoff note is often enough:

We estimate 75 to 120 minutes of production time for the 18 approved changes, including one revised InDesign file and one proof PDF. Two comments are awaiting your decision. We’ll confirm their effect on the estimate and delivery date once we have your instructions.

After the round, record the actual time spent on intake, editing, and QA. If the job ran over, note what caused it. A set of late asset swaps tells you more about what to allow for next time than the total comment count.

Where FormatStack fits

We’re building FormatStack to apply annotated PDF feedback to the matching source file automatically, starting with InDesign. If your team regularly estimates revision work, request a FormatStack walkthrough and bring a representative marked-up PDF and its source file. We can discuss where the work goes today and where the automated workflow could fit.

Keep reading