Submit a permit package to the authority

Gather the drawings, calculations, reports and forms the submission needs, and check each one is current before it goes into the package.

Why: A missing report or an outdated drawing is the single most common reason a package bounces back unread. Sorting the set first means the build step starts from documents that are actually complete.

Create the submission, attach the document set, and run the built-in validation so missing items, wrong formats and unsigned pages surface before anyone outside the team sees them.

Why: Catching a gap here costs minutes. Catching the same gap after the authority has opened the file costs the whole review cycle again.

Generate the package in the format the authority accepts, with a consistent file structure and a cover index so a reviewer can find every item without asking.

Why: A clean, indexed package reads as a competent submission before the reviewer has opened a single drawing. A loose pile of files invites the kind of scrutiny that slows everything down.

Send the package to the authority and track its status, review comments and decision date in one place instead of a side email thread.

Why: A submission that only lives in someone's inbox is a submission the rest of the team cannot plan around. Tracking it against the record keeps the programme honest about when approval will actually land.