<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Set-Check guides</title>
    <link>https://set-check.com/guides</link>
    <description>Answers to the questions that come up before a civil plan set is submitted, each cited to the published document that settles it.</description>
    <language>en-us</language>
    <atom:link href="https://set-check.com/guides/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Electronic plan submittal requirements, and how much they differ</title>
      <link>https://set-check.com/guides/electronic-plan-submittal-requirements</link>
      <guid isPermaLink="true">https://set-check.com/guides/electronic-plan-submittal-requirements</guid>
      <pubDate>Sat, 19 Sep 2026 12:00:00 GMT</pubDate>
      <description>What jurisdictions require of a submitted plan set PDF: format, one file or many, layers, file naming, sheet size and seals, and where the rules contradict.</description>
    </item>
    <item>
      <title>A pre-submittal checklist for a civil engineering plan set</title>
      <link>https://set-check.com/guides/pre-submittal-plan-set-checklist</link>
      <guid isPermaLink="true">https://set-check.com/guides/pre-submittal-plan-set-checklist</guid>
      <pubDate>Sat, 19 Sep 2026 12:00:00 GMT</pubDate>
      <description>A checklist to work through before a civil plan set is submitted: sheets and the index, scale, north arrow, legend, and the seal with the date beside it.</description>
    </item>
    <item>
      <title>How plan review and resubmittals work, wherever you submit</title>
      <link>https://set-check.com/guides/plan-review-timelines-and-resubmittals</link>
      <guid isPermaLink="true">https://set-check.com/guides/plan-review-timelines-and-resubmittals</guid>
      <pubDate>Sat, 19 Sep 2026 12:00:00 GMT</pubDate>
      <description>What happens after a civil plan set is submitted: the completeness screen, published review windows, and why every resubmittal answers comments in writing.</description>
    </item>
  </channel>
</rss>
