Every document.
A clear next step.

This demo uses made-up projects and sample files. Start with a project assigned to you. See which documents are needed and who acts next.

Open the energy assessment and add the two sample files. They are saved as a draft. Choose Submit when they are ready for the reviewer.

The reviewer asks for a clearer improvement schedule. Read the reason beside version one, then upload the corrected files. The earlier files stay in history.

Submit version two so the reviewer can check it. The status now says Submitted. You can still see the earlier feedback.

Once the required files are ready, ask for a generated or custom application. Only the internal reviewer can prepare or replace the official unsigned PDF, approve it and release it to you.

Download the current application for signing outside the portal. Here, use a sample signed copy for that same release. Upload it, then choose Submit. No real signature is collected.

The reviewer checks and accepts the signed copy for release one. A new release needs its own signed copy and decision. Acceptance here is a document check, not a lending decision.

This demo uses made-up projects and sample files. Your review list shows what needs attention. Documents, application requests and signed copies are separate tasks.

Choose Start review before deciding. If something needs correcting, explain what to change so the lender knows what to do next.

Check version two against the requested correction. Keep version one in history. Conditional approval still has follow-up work. It is different from full approval.

Review the application request and explain your approval. This approval comes before release. It does not accept a signed copy.

Prepare and release the official application PDF. This saves the approved information for that version, so later changes do not rewrite the released copy.

Check that the signed copy belongs to the current release. Then accept it as a separate step. The decision applies to this copy only.

Explain why a new application version is needed, then create release two. Keep the earlier signed copy and acceptance in history. The old signed copy cannot be used for the new release.

For the custom route, the internal reviewer prepares the official PDF before approval and release. This accepted custom version has its own signed copy. Earlier generated applications remain in history.

This demo uses made-up records and example settings. Start with the program checklist. Program requirements are separate from the lender and each project’s submitted documents.

Download a blank assessment template or the program guide. Downloading a reference file does not submit a project document or change its status.

Add a requirement, then edit that same item. Changing its name or instructions does not create a duplicate or erase earlier project work.

Choose when the item is needed, where it appears and whether it is required. Choose whether lenders should see it. These controls illustrate checklist settings, not real access protection.

Check the lender view to see the result. Optional items do not stop the next stage. Internal-only items stay out of the lender checklist and download package.

Choose whether this example requires full approval or also allows conditional approval. The screen shows which insurance item would block progress. This is an example rule, not a confirmed client policy.

This demo uses made-up records. See project assignments, outstanding reviews and application status together. The lender and reviewer use the same project information.

Remove the lender’s assignment to Juniper Commons. Their other project, Meridian Works, stays assigned. Being in the lender organization alone does not give access to every project.

Switch to the lender view. Only Meridian Works is listed. This previews assignment changes. It does not change real accounts or permissions.

Remove the remaining assignment and check the empty project list. No other projects appear automatically. Restore the two demo assignments when you are ready.

Choose the example with no recipients, then preview a reminder. The activity records the attempt without saying it was delivered. No email is sent.

Uploads and downloads are recorded without a message preview. Review and conversation events show who would be notified. Use the activity list to see who acted, what changed and which project or file was involved.