Doden Legacy Office Pilot [📲𝙋𝙧𝙤𝙙𝙪𝙘𝙩]

7. DLO Relational Questionnaire.docx - Google Docs

2. DLO Internal Phase Gates Strategic Discovery Process (SDP) (1).docx - Google Docs

Red Regarding the "Create a digital version of the relational questionnaire in Lovable" subtask...

• Questionnaire: 7. DLO Relational Questionnaire.docx - Google Docs
• Built it in Lovable - follow best practices for form
  • Should feel guided, almost like a Typeform or the OHA
  • Follow the brand guidelines of Daryle.ai (I recommend copying or referencing a current Daryle.ai project)
  • USE a different project from the current Daryle AI project
• Make it feel interactive, guided, and engaging
• Build in an auto-save feature and save now and finish later.

Justin I have some questions regarding this task:

• For the relational form — should it share the same Supabase project as the main Daryle AI platform so we can link form responses to user data later, or should it be a standalone Supabase project with no connection to the platform?
• Is it Daryle "himself" appearing as the one asking the questions? We can change the UI if yes — we can derive from behavior in Daryle AI chat to add more personality to the questions.
• What happens at the very end? Like for OHA it gives a company health score/report. Does this form simply end with a thank you screen, a summary of their answers, or something else?
  
  cc Brandon

Different Supabase Red

It’s not Daryle asking the questions.

No analysis after it submits, just summits Red

Justin Thank you for the answers, planning is done. Will begin with vibe coding.

Justin

The project has been created and I'm doing QA for it right now. But I do have some additional questions so I can further polish the UI/UX for both our side, the ones collecting answers and those who we send the forms to.

It's a bit extensive so maybe a loom video will be good to answer the questions.

cc Brandon

Relational Questionnaire — Open Questions

Distribution / Access

• How will respondents receive the form? A single public link anyone can use, or unique invite links per person?
• Should there be any access control (password, invite-only), or is an open link fine?
• Do we need to track who was invited vs. who actually completed it?

After Submission

• Should respondents be able to start a new questionnaire from the thank-you screen, or is one submission per person the expectation?
• Do respondents get a confirmation email after submitting?
• Should they receive a copy of their own answers?

Admin / Results Access

• Who needs to view submissions — just Daryle, a small team, or a broader group?
• What do they need to see: a list of respondents, full answers per person, or exportable data (CSV)?
• Do we need search, filters, or completion stats, or is a simple list enough for now?
• Should the admin view be password protected, or is a hidden URL acceptable for now?
• Should admins get notified when a new submission comes in?

Data

• How long should incomplete/abandoned sessions be kept before cleanup?
• Any data retention or privacy requirements we should build in from the start?

Red , ( Justin Ann CC )

For this first version, please use the following defaults unless Justin or Ignite121 gives us a different direction:

Distribution / Access

• Use unique invite links for each respondent rather than one public link.
• Make the questionnaire invite-only for now.
• Track who was invited, who started, and who completed it.
• Do not rely on a hidden URL as security.

Because the questionnaire asks about personal history, setbacks, values, trust, humility, and personal growth, we should treat responses as sensitive.

After Submission

• One completed questionnaire per invite link.
• The thank-you screen should confirm that the response was received, but should not automatically start another questionnaire.
• Send a simple confirmation email.
• Do not automatically email respondents a full copy of their answers. We can add that later if Ignite121 wants it.

Admin / Results

• Initial access should be limited to Ignite121 and anyone they specifically designate.
• Admins should be able to see:
  • respondent name and status;
  • completion date;
  • full answers for each respondent;
  • basic completion statistics;
  • search and filtering;
  • CSV export.
• The admin area should be password-protected with role-based access.
• Notify the designated Ignite121 administrators when a new questionnaire is completed.

Data / Privacy

• Keep abandoned sessions for 30 days, but flag them so Ignite121 can decide whether to follow up with those respondents before cleanup.
• Keep completed responses while they are needed for the Ignite121 engagement, with a configurable retention period rather than hard-coding a permanent policy.
• Include a short privacy statement explaining who can access the responses and how they are used.
• Do not expose answers in URLs, browser titles, email subject lines, or analytics logs.
• Build this so access and retention can be tightened later without rebuilding the product.

Pilot scope

Please keep the first version focused on:

1. Secure invitation and completion flow.
2. The relational questionnaire itself.
3. Thank-you and confirmation email.
4. Admin list and individual response view.
5. Search, filters, completion status, and CSV export.
6. Basic notifications and access control.

We do not need a complex reporting engine, AI analysis, respondent self-service portal, or broad organizational dashboard for this first version. Those can come after we validate the process with Ignite121.

The only items that truly need Ignite121’s confirmation are:

• Who besides the initial Ignite121 administrators should have access?
• How long should completed responses be retained?
• Whether respondents should eventually receive a copy of their answers.
• Whether Ignite121 wants this to remain invite-only or support public links later.

You can proceed with the defaults above and flag those four items for confirmation.