Demonstration · invented data · no real person's record appears here About this demonstrationAbout
UYWI LDP

About this demonstration

This is a working sketch of the participant portal described in the UYWI Leadership Development Platform concept paper and technology stack, version 1.7. It shows what a custom-built portal could look like. Every person, organization, comment and number in it is invented.

What is working for real

  • Sign-in. Accounts are issued by an operator and passwords are stored securely, never in readable form. You are signed out after 12 hours without activity, or after 7 days.
  • Roles and restricted data. Participants see only their own record. Facilitators see only leaders in cohorts they facilitate, and never pulse check responses, care pause status or 360 inputs. Staff see everything, in sections labeled "Restricted: staff only".
  • The Credits ledger and caps. Credits are never edited or deleted: a correction is a new entry, and the balance is the sum of the entries. Rates and caps come from a table staff can change, the same activity cannot be credited twice, and the 24-month expiry is calculated (nothing is removed).
  • Application log approval. A leader submits, the cohort's facilitator or staff approves or declines with a note, and approval adds Credits unless two were already approved that calendar month.
  • Readiness flags and the queue. Progression, activation and care pause are worked out from the data using the thresholds in Settings. A care pause suppresses the activation flag and holds until staff clear it with a note, whatever later pulse checks say. The queue shows each criterion; a person makes every decision.
  • The no-sign-in 360 link. Staff create a single-use link for one named reviewer. It expires after 21 days, can be revoked, and shows the reviewer only the leader's name, the reviewer's own name and the questions.
  • The audit log. Every staff view of a restricted record and every decision is recorded and readable by staff.
  • Pulse checks, facilitator rubrics, Roadmap items, the HubSpot summary preview and the impact follow-up schedule all work on the data in this demonstration.

What is sample data standing in for bought tools

  • Thinkific: cohort enrollments, sessions, attendance, completed courses and certificates.
  • Circle: community contributions and "last active" dates.
  • The credential provider: course badges and certifications. A Leadership Journey Identity is a stage of development, not an award, so it is never shown as a badge.
  • HubSpot: nothing is sent. The preview page shows the values that would be allowed to leave.
  • The Leadership Journey Assessment: results are seeded. The instrument itself and its scoring are UYWI's and are not reproduced here.
  • The AI Leadership Guide: not connected. Its page shows a labeled sample conversation; the "Use it" capture beside it does work.

What is placeholder wording or a placeholder number

  • The eight pulse check statements, the four season words (thriving, steady, stretched, burnt out), the facilitator rubric items and the four 360 statements were written for this demonstration. They are not UYWI's instruments.
  • The concept paper has pulse items rotating across the four dimensions. This demonstration asks two per dimension every quarter.
  • The paper gives 80% attendance, three approved Application logs, Navigator, 90 days, 24 months and a yearly assessment. The Spirit and Behavior minimums, the size of a "sharp drop", the "stable" allowance, the "expiring soon" window and the 21-day link life are placeholders for UYWI to agree. Settings marks each one.
  • Three behaviors are choices made here and stated on the pages where they apply: a "not yet" decision returns a leader to the queue after 30 days; the readiness value for HubSpot falls back to none once staff approve a flag; and "stable or rising" compares only the last two pulse checks.

What is deliberately not built

  • Credit redemption, including the scholarship pool. The options the paper proposes are listed on the Credits page as planned. Gifting Credits to another leader is not listed or built.
  • Any live connection to Thinkific, Circle, HubSpot, a credential provider or an AI service.
  • Public sign-up, email of any kind, reminders and scheduled jobs.
  • The leader's own Community Impact follow-up form. Leadership Activation is worked from the staff side: staff record the invitation and the follow-up that comes back. A leader sees their invitations and where each follow-up stands on their Roadmap page.
  • Module reflections. The table is in the data model and holds a few sample rows, but no page collects or shows them.
  • Items that appear only on the concept deck's illustrative screen and have no rules behind them yet: My Community, prayer requests, "The Gospel At Work" and a coaching page.
  • Organization-facing dashboards, which the documents exclude permanently.

How this differs from the documents

  • The documents plan Version 1 on bought tools: Softr for the portal and its database, with Make moving data between systems, and they list a custom-built Passport application as out of scope for Version 1. This portal and its own database stand in for Softr to show the alternative. No Make automations run here.
  • The stack document says facilitator observations are visible only to authorized staff. Here a facilitator can also read back and correct the rubric entries they wrote themselves, and never anyone else's. This is worth confirming with UYWI.

Using it

Guide accounts have a "View as" switcher for three personas: Marcus Alvarez (a participant), Denise Carroway (a facilitator) and Renee Whitlock (staff). A good first walk-through: submit an Application log as Marcus, approve it as Denise, then look at Marcus's Credits. "Reset demonstration data" puts everything back.

Go to sign in