Frequently Asked Questions

Select "Forgot Password?" on the sign-in page. Enter your account email, then use the PIN sent to that address to complete the reset. If the email does not arrive, check your junk folder and confirm that you entered the address used for your LiveArch account.

Project access may not have been added, may have expired, or may not yet be reflected in your current session. Refresh the page, sign out and back in, and then contact your project administrator, or open a support ticket if the project is still missing. See Troubleshooting: Missing Project for a full checklist.

It depends on the project. Some projects use LiveArch as a standalone platform of record. Others use Procore as the construction manager's record and LiveArch for design-team coordination. Follow the project's written communication protocol and contract requirements — the comparison on Platform Overview shows how the two modes differ.

If your project uses LiveArch as the platform of record, yes. An email alone may not create an official, tracked record. Create the item in the required platform unless the project team has documented another procedure.

Once an item has been distributed, its submitted content is generally locked. For a Submittal, create the next revision of the existing Submittal. For an RFI, close or withdraw the incorrect item as directed and create a new RFI. If an item has not yet been distributed, contact the project team about withdrawing it.

Use searchable electronic PDFs unless the project or upload form permits another format. Submittals should generally be one combined PDF containing the transmittal, required stamps, and all review content. RFIs may include multiple clearly named supporting files when the form permits them.

Follow the project protocol. In the documented GC workflow, the construction manager or general contractor reviews subcontractor questions and submits the RFI; subcontractors do not submit directly to the architect.

Open the record and review its distribution or reviewer list. The current reviewer or "ball-in-court" party is the person or company expected to act — see Who does what on the RFIs page for how assignee, reviewer, ball-in-court, and distribution list differ. List views may also highlight items assigned to your company.

Use the completed, returned, or closed view shown in the module. Open the record to read the final response and download any returned PDF or markups.

Yes. The Drawings and Specifications modules show the latest revision by default and retain older versions. Filter or select the records you need, then use the available download or export action.

No. Drawings and specifications added through an ASI are folded into the conformed set. A revised sheet attached only to an RFI response must be handled separately according to the project's document-control procedure.

The most common causes are that LiveArch is only on the distribution list rather than assigned as the current reviewer or assignee, required Procore fields are incomplete, a Submittal lacks a sent date or complete number, or the integration was not granted access to the project. See Troubleshooting: Procore Syncing — the sync diagram there shows exactly where each kind of change stops.

No. A distribution-list entry or CC may notify someone, but it does not give LiveArch responsibility for the record. The LiveArch integration user must be the current reviewer for a Submittal or current assignee for an RFI.

Avoid RFI revisions for connected workflows. LiveArch expects an "asked and answered" record. Submit a follow-up question as a new RFI so each question has a clear response and its own tracking history — see Procore-Connected RFIs.

Open a support ticket for technical support. Questions about contractual process, formal response language, or whether a document should be issued as an ASI, RFI response, or another instrument should go to the project leadership and applicable CA leadership.