Skip to content
The first pages of the Pull Request Checklist template

Pull Request Checklist

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Difficulty
Beginner
Updated
November 6, 2026

Every page (3)

Overview

Code reviews slow down when nobody agrees what must be checked, and they go soft when reviewers rubber-stamp a 2,000-line change. This code review guidelines template sets one short standard for pull requests: the principles, what authors check before opening a change, what reviewers check, how comments should read, and how disagreements are settled. Each rule is specific enough to verify.

The sample is for Dovecote Systems, a fictional software team, with a size target of 400 changed lines, a four-hour first review and a security section for risky paths. Replace the principles, targets, checklists and examples with your own team's agreements, and trim anything your build already enforces. Keep the checklist to one page, because a long checklist is skipped.

Useful for

  • A pull request template that every author pastes into a new change
  • A review standard for a team that is growing from three to ten engineers
  • An onboarding page that shows new engineers how reviews work here

What's included

  • Title block with the standard's owner, version and scope
  • Stats strip with the defect cost, resolution rate and coverage target
  • Usage notes with the size, turnaround and approval rules
  • Security, docs and screenshots policy with a key rule
  • Make-it-yours guide with five steps to adopt the checklist

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the principles and targets with your team's agreed standards, then check each one.

  3. 3

    Trim the checklists to items your CI does not already enforce, and add the list to the template.

  4. 4

    Name the tie-breaker and the escalation route, and add them to the last page.

  5. 5

    Delete the guide page, then share the checklist with the team or present it from Google Docs.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Are Dovecote Systems, its engineers and targets real?

No. Dovecote Systems, its staff, the defect costs, review times, coverage targets and the example comments are fictional sample data. Replace them with your team's own measures before you adopt the checklist.

What size should a pull request be?

Under 400 changed lines, and ideally under 200. Larger work should be split into a series of changes that each stand on their own, so reviewers can give each one real attention.

How do we settle a disagreement in review?

The author and reviewer talk first, then bring in the code owner for the area. If the matter is still open after a day, the tech lead decides and records the reason, so the rule is clear next time.

  • #code-review-checklist
  • #pull-request-template
  • #code-review-guidelines
  • #engineering-standards
  • #developer-workflow

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…