Portal Agent v2: Full DDQ Imports, Approved Answers Written Back
Portal Agent v2 is an AI agent in your Chrome side panel that imports the whole questionnaire from DiligenceVault, Dasseti and the other portals it is tested on into AutoRFP.ai, then writes your approved, source-cited answers back into the portal fields.
- Published
- Reading time
- 7 min
If you manage DDQs at an asset manager, the end of a quarter tends to bring the same message: an investor has opened this year’s questionnaire in DiligenceVault, and the deadline sits where the calendar has no room for it. Getting the questionnaire out of the portal is where it falls apart. The Word or Excel download flattens multiple choice into plain text, breaks tables across cells that no longer line up, and drops the follow-up questions that only appear after a Yes. The week starts by rebuilding a questionnaire that already exists on screen, and it ends by copying approved answers back into the portal, one box at a time.
As one private markets DDQ lead described it, DiligenceVault is the “platform where a lot of the investors will use to request the completion of DDQs.” The portal is where the work begins and where it ends. Another DDQ manager put the export in fewer words: “we’d have to export it first. Seems like a lot of steps.” Each of those steps is a place a question can go missing, on a document investors read line by line.
AutoRFP.ai is the accuracy-first, AI-native platform for RFPs, security questionnaires, and DDQs: every answer is written from content your team has approved, and shows the sources behind it. Asset managers use Portal Agent v2 to carry that drafting into DiligenceVault and Dasseti, the portals where due diligence questionnaires in finance actually get requested.
The questionnaire stays whole on the way in
Portal Agent v2 sits in a Chrome side panel beside the portal. It works through the questionnaire and chooses its own next step. You do not have to map fields or click through every section while it reads. What arrives in AutoRFP.ai is the DDQ the investor built. Question numbers and sections stay in the order the portal shows them. Radios, checkboxes, and dropdowns stay as real choices. Follow-up questions the export would have dropped come across too. Answers already saved in the portal arrive attached to those questions.
A questionnaire that still follows DDQ best practices keeps the investor’s structure, choices, and follow-ups. The import also becomes a project you can bring in again. When next year’s DDQ opens in DiligenceVault or Dasseti, the new version refreshes the project you already have, and the DDQ response carries forward into that project.
How the agent reads a portal
Portal Agent v2 reads a portal page the way a person does. It looks at what is on the screen and works out which lines are questions, which are instructions, and which choices belong to which question.
From there it works as an agent. It decides what to do next, moves through the sections, and carries on until the import is done. That is how one agent can work through an investor DDQ in DiligenceVault and a control assessment in CyberGRX.
When it finishes, and before anything becomes a project, you look over the imported questionnaire and decide whether to create a new project or add the questions to one you already have. That review is where accuracy starts. A clean import means each later answer is attached to the question it was meant for, so reviewers can check how a DDQ answer is structured against the question that actually arrived.
An import you can leave and come back to
Long DDQs span many portal pages. Clicking to another tab in the middle of an import used to mean starting again. Portal Agent v2 saves its progress as it works. You can navigate away, refresh the page, or close the tab, and when you come back to the portal the import picks up where it left off.
Completeness gets the same attention. A user of an earlier scraper told us, “I noticed that I had to manually check if it missed.” That line-by-line audit is the job the chat panel shortens. If the agent misses a section or reads a question wrong, you tell it in plain language. It fixes, moves, or removes the imported questions. It edits those questions, and your answers stay as they are until you change them. Any removal waits for your confirmation before it happens. When you re-import into an existing project, it previews which questions are new, reworded, or removed before anything changes, so the decision stays with you.
Every answer starts from content you already approved
Once the DDQ is in, AutoRFP.ai drafts each response from your approved fund, firm, and policy material, cites the passages it used, and attaches a Trust Score so reviewers know which answers deserve a second look before an investor sees them. On AutoRFP.ai, 63% of AI-generated answers go out with no edits. The guide to AI for DDQ responses walks through how that drafting works across due diligence.
The last mile, back into the portal
The final step is the one DDQ teams ask about. One investment team put the question plainly: “Then repopulating it, repopulating our answers in, is that a manual copy-paste.” Another described the goal as the ability to stop filling those portal questionnaires by hand.
Other response tools offer portal write-back too. With Portal Agent v2, approved answers are written into the portal’s fields straight from AutoRFP.ai. The loop closes on answers that came from a complete import and were written from approved, cited content. The agent fills each field within the limits the portal sets and checks that each answer is in place. It never submits the questionnaire, so the decision to submit stays with you. If a stakeholder wants a document for sign-off, you can export the questionnaire, answers included, to a Word template.
The hours that used to go into rebuilding and re-keying go back to the questions that need a person.
Built for the portals your investors and customers use
Portal Agent v2 is tested on DiligenceVault, Dasseti, OneTrust, UpGuard, and CyberGRX. That set covers the investor DDQ portals asset manager buyers name most, and the security questionnaire portals their colleagues in risk and IT already work in. One security questionnaire customer told us that with a previous UpGuard import, “sometimes like the hierarchy is not working correctly.” Import, review, and write-back work the same way on UpGuard, OneTrust, and CyberGRX. Teams that answer those portals every week can follow the same path into security questionnaire automation.
Portal Agent v2 is part of our DDQ response software. Our roundup of the best DDQ software compares the wider category.
See it on your next DDQ
Bring a real DiligenceVault or Dasseti questionnaire. Portal Agent v2 can import it, let you check it, and write approved answers back into the portal.
About the author
Technical Account Manager at AutoRFP.ai. Writes about DDQs and security questionnaire response.
LinkedIn
