In crisis? Call or text988

How it works

INTREPID is a community-edited psychosocial resource platform. Content is proposed by Contributing Users, fact-checked by Domain Practice Coordinators, and published through a workflow that records who wrote and who approved every change.

Each of the 10 workflows below is drawn from the definition the platform actually runs, so what you read here is what the system does.

WF-1 · Applying to become a Contributing User

A prospective contributor submits an application. The Editorial Team reviews it and either approves, rejects, or asks for more information.

  1. PUBLICApplication submitted through the public form

    Public visitorPLAN §9

    • Open for reviewEditorial Team reads the qualifications and references

  2. ETEditorial Team reads the qualifications and references

    Editorial TeamPLAN §9

    • ApproveApplication approved — onboarding begins
    • RejectApplication declined, with reasons recorded
    • Request more informationApplicant is asked to supply more detail

  3. ETApplication approved — onboarding begins

    Editorial TeamPLAN §9

  4. ETApplication declined, with reasons recorded

    Editorial TeamPLAN §9

  5. CUApplicant is asked to supply more detail

    Contributing UserPLAN §9

    • ResubmitApplicant returns the additional detail

  6. CUApplicant returns the additional detail

    Contributing UserPLAN §9

    • Open for reviewEditorial Team reads the qualifications and references

WF-2 · Onboarding an approved contributor

Approval triggers a single-use, time-limited link. The contributor sets a password and the account becomes active.

  1. SYSTEMApproval received from WF-1

    SystemPLAN §9

    • AutomaticOne-time set-password link emailed to the contributor

  2. SYSTEMOne-time set-password link emailed to the contributor

    SystemPLAN §9

    • Set passwordPassword set — the account is now active
    • Link expiresLink expired unused; a new one must be issued

  3. CUPassword set — the account is now active

    Contributing UserPLAN §9

  4. SYSTEMLink expired unused; a new one must be issued

    SystemPLAN §9

WF-3 · Proposing new content (CARN1)

A contributor proposes a new topic or listing. The Editorial Team decides whether it belongs on the platform.

  1. CUProposal drafted in the contributor’s sandbox

    Contributing UserPLAN §13

    • SubmitProposal submitted to the Editorial Team

  2. CUProposal submitted to the Editorial Team

    Contributing UserPLAN §13

    • Open for reviewEditorial Team assesses scope and duplication

  3. ETEditorial Team assesses scope and duplication

    Editorial TeamPLAN §13

    • ApproveProposal accepted; routing to a coordinator begins
    • RejectProposal declined, with reasons recorded
    • Park for laterHeld for later — revisited without a fresh submission

  4. ETProposal accepted; routing to a coordinator begins

    Editorial TeamPLAN §13

  5. ETProposal declined, with reasons recorded

    Editorial TeamPLAN §13

  6. ETHeld for later — revisited without a fresh submission

    Editorial TeamPLAN §13

    • Resume reviewEditorial Team assesses scope and duplication

WF-4 · Assigning a Domain Practice Coordinator

An approved proposal is matched to the coordinator whose expertise and country focus fit it best.

  1. ETProposal waiting for a coordinator match

    Editorial TeamPLAN §13

    • Assign coordinatorCoordinator assigned to the proposal

  2. ETCoordinator assigned to the proposal

    Editorial TeamPLAN §13

    • Notify contributorContributor told who will review their work

  3. SYSTEMContributor told who will review their work

    SystemPLAN §13

WF-5 · Linking content to the Wellness Mapping Matrix

Each topic is tied to one or more matrix categories so visitors can find it by need rather than by title.

  1. ETTopic exists but is not yet placed in the matrix

    Editorial TeamPLAN §15

    • Begin linkingMatrix categories being selected for the topic

  2. ETMatrix categories being selected for the topic

    Editorial TeamPLAN §15

    • Link confirmedTopic discoverable through the matrix
    • Linking abandonedTopic exists but is not yet placed in the matrix

  3. ETTopic discoverable through the matrix

    Editorial TeamPLAN §15

WF-6 · Authoring content (CARN2)

The contributor writes the content in a private sandbox. Work is saved automatically, and the draft locks once submitted so it cannot change mid-review.

  1. CUSandbox opened for the approved proposal

    Contributing UserPLAN §43

    • Start draftingContributor writes and edits the draft

  2. CUContributor writes and edits the draft

    Contributing UserPLAN §43

    • AutosaveDraft saved automatically while writing
    • Submit for reviewDraft submitted for review

  3. SYSTEMDraft saved automatically while writing

    SystemPLAN §43

    • Autosave completeContributor writes and edits the draft

  4. CUDraft submitted for review

    Contributing UserPLAN §43

    • Returned for reworkContributor writes and edits the draft
    • After a delayDraft locked so it cannot change during review

  5. SYSTEMDraft locked so it cannot change during review

    SystemPLAN §43

    • Returned for reworkContributor writes and edits the draft

WF-7 · Routing a submission to review

A submitted draft is routed to the coordinator responsible for that topic, automatically where possible and by hand where not.

  1. CUEditing session opened against an existing page

    Contributing UserPLAN §13

    • Start draftingChanges drafted against the live page

  2. CUChanges drafted against the live page

    Contributing UserPLAN §13

    • SubmitChanges submitted for routing

  3. CUChanges submitted for routing

    Contributing UserPLAN §13

    • Route automaticallySubmission delivered to the coordinator’s queue
    • Route by handSubmission delivered to the coordinator’s queue

  4. SYSTEMSubmission delivered to the coordinator’s queue

    SystemPLAN §13

WF-8 · Editing existing content (CARE)

Edits to a published page are drafted, previewed exactly as they will appear, and then submitted.

  1. CUContributor edits the existing page

    Contributing UserPLAN §21

    • AutosaveEdit saved automatically while working
    • PreviewContributor previews the page as readers will see it

  2. SYSTEMEdit saved automatically while working

    SystemPLAN §21

    • Autosave completeContributor edits the existing page
    • PreviewContributor previews the page as readers will see it

  3. CUContributor previews the page as readers will see it

    Contributing UserPLAN §21

    • Back to editingContributor edits the existing page
    • Submit for reviewEdit submitted for review

  4. CUEdit submitted for review

    Contributing UserPLAN §21

WF-9 · Fact-checking and publishing

The coordinator fact-checks the submission against its sources, then publishes, edits, returns it, or escalates to the advisory board.

  1. DPCSubmission waiting in the coordinator’s queue

    Domain Practice CoordinatorPLAN §31

    • Begin fact-checkCoordinator checks claims against the cited sources

  2. DPCCoordinator checks claims against the cited sources

    Domain Practice CoordinatorPLAN §31

    • Approve and publishContent published; the previous version is archived
    • Approve with editsCoordinator’s corrections applied before publishing
    • Return for reworkReturned to the contributor with review comments
    • Escalate to advisory boardEscalated to the advisory board for a final decision

  3. SYSTEMContent published; the previous version is archived

    SystemPLAN §31

  4. DPCCoordinator’s corrections applied before publishing

    Domain Practice CoordinatorPLAN §31

    • Publish edited versionContent published; the previous version is archived

  5. CUReturned to the contributor with review comments

    Contributing UserPLAN §31

    • ResubmitContributor resubmits after rework

  6. LEABEscalated to the advisory board for a final decision

    Library Editorial Advisory BoardPLAN §31

  7. CUContributor resubmits after rework

    Contributing UserPLAN §31

    • Begin fact-checkCoordinator checks claims against the cited sources

WF-10 · Multi-step approval

Some content needs more than one sign-off. The configured approval tree is walked one step at a time; the last approval publishes.

  1. SYSTEMWaiting on the approver for the current step

    SystemPLAN §32

    • Approve this stepAdvancing to the next approver in the tree
    • Approve this stepFinal approval reached — content published
    • RejectAn approver rejected; the chain stops here

  2. SYSTEMAdvancing to the next approver in the tree

    SystemPLAN §32

    • AutomaticWaiting on the approver for the current step

  3. SYSTEMFinal approval reached — content published

    SystemPLAN §32

  4. SYSTEMAn approver rejected; the chain stops here

    SystemPLAN §32