Returning Submittals

Now that you’ve created and reviewed your submittal, the next step is returning it to the team! Only prime consultant's have the ability to return submittals.

Pro Tip: Before you start returning submittals, make sure your distribution groups are set up. This way, your distribution list will auto-populate on every submittal — saving you time and keeping things consistent.


How to Return a Submittal

Step 1: Once you're sure that everyone has responded, click the blue Return button in the header. (Note that only individuals with the Prime Consultant role on the project can return the document.)

Step 2: You'll be led to the return flow page, that looks like this:

Here you'll find:

  • Files: On the left hand nav, you can select which files you want to return as part of your official response. Don't want to include a cover page? No problem! Simply deselect!
  • Cover Page: take a look at the cover page details to make sure you're happy with it before returning!
  • Distribution List: Double check the distribution list to make sure the right people are receiving the doc. They'll get an email notification with a direct download link, as well as a link to view in Part3.
  • Distribution Message: Add an optional distribution message to your team, that will be included in the email, to provide a little more context!

Step 3: When you're ready, click the blue Return submittal button in the top right.

Step 4: The submittal status will change to Returned.


Revise or Re-Open a Returned Submittal


Once the submittal has been issued, if you need to reopen it to edit you have the flexibility to do this by clicking the +reopen next to the Revise button.


If you need to revise a submittal (in the case where a submittal was returned as revise & resubmit), click revise.


From here, follow the above steps again to return the submittal!

As always, if you have any questions or see any issues with this article, please reach out to support@part3.io

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.