Lesson 122 · The Grant Architect

122. Final Assembly & QA

30 min

By the end you'll be able to

  • Run a comprehensive pre-submission QA pass against a written checklist.
  • Catch the most common disqualifiers (pagination, fonts, file names, page limits, missing sections, broken cross-references).
  • Assign QA as a named deliverable with an owner and a sign-off.
  • Defend the assembly window against last-minute content edits that destabilize the package.

Final assembly is where months of work get disqualified by a single broken cross-reference, a misnamed file, or a font that did not embed in the PDF. This lesson gives you a systematic quality assurance checklist so the last twenty-four hours before submission are about verification, not panic. You will treat assembly as its own deliverable, with its own owner and its own sign-off, instead of a clerical afterthought.

You will walk through the QA checks that catch the most common disqualifiers: pagination continuity across merged documents, PDF conversion fidelity with embedded fonts, file naming that follows the funder's exact conventions, page limits measured against the funder's rules (not your word processor's defaults), required sections present in the required order, and internal cross-references that still point to the right page after the final edit. Each check has a verification method, not just a yes or no question.

By the end you should be able to run a pre-submission QA pass on any proposal in under two hours and produce a signed checklist that your authorized organizational representative can rely on. The goal is simple: nothing in this package fails for a reason a checklist could have caught.

Common mistakes

These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.

  • Doing QA on the Word draft instead of the final PDF.

    Pagination, font embedding, and page-count rules apply to the submitted PDF. Checking the Word file proves nothing about what the funder will see.

  • Treating QA as a checkbox instead of a verification.

    Asking "is pagination correct?" is not a check. The check is: open the PDF, scroll through every page, confirm the numbers run continuously.

Practice problems

Try each on paper first. Click Show solution only after you've made a real attempt.

  1. Problem 1
    Draft a five-item final assembly checklist for a federal proposal due in seventy-two hours.
    Show solution
    1. Page limits verified against the NOFO page-count rule (count pages in the final merged PDF, not the Word draft). 2) Fonts embedded (open File > Properties > Fonts in Adobe and confirm every font shows Embedded Subset). 3) File names match funder conventions exactly (compare to the NOFO appendix list). 4) Required sections present in required order (compare table of contents to the NOFO outline). 5) Internal cross-references resolve correctly (click each page reference in the PDF and confirm it lands on the right page). Owner: Grants Manager, sign-off due forty-eight hours before deadline.

Practice quiz

  1. Question 1
    Which of the following is the most common preventable disqualifier in final assembly?
  2. Question 2
    Why does the lesson recommend treating final assembly as its own deliverable with a named owner?
  3. Reflection 3
    Name three QA checks that should appear on a final assembly checklist and the verification method for each.

Lesson 122 recap

Final assembly is a deliverable with its own owner, its own checklist, and its own sign-off. Most disqualifications happen here, and almost all of them are preventable.

Coming next: Lesson 123 — Submission Timing

Next, we cover submission timing, the forty-eight-hour rule, and why deadline-day submission is professional malpractice.

Saved in your browser only — no account, no server.