DRKNYT
MenuClose
← DRKNYT Advocacy

Community Builds

Make something
possible.

Start with what you need to be able to do.
A rough idea is enough.

Try the practice journey

Real requests are closed. The practice journey sends nothing.

Check a request in your Profile

A useful first step

Tell us the need.
We can work out the tool.

You do not need a technical proposal. The answer could be a clearer resource, a simpler process, an existing tool or a carefully scoped build.

Requests are for private review. Scope, funding, ownership, ongoing costs and support are agreed separately before any work begins.

Preparing the first invitation-only review.

We are preparing a small first round of invited requests: up to five requests over no more than 14 days, starting with one invited request. These are reviews, not funded build places. Any work, costs and ongoing support will be agreed separately.

Try the practice journey

What a useful change could look like

Small enough to finish.
Useful enough to matter.

01

Make information reachable

A community service needs clear opening times and a contact page people can use on a phone.

02

Make coordination easier

A volunteer group needs a manageable way to organize a rota and hand the work to someone else.

03

Make a task manageable

Someone needs a simple way to organize information and prepare a clear message or next step.

From a need to a next step

Understand it.
Agree it.
Make it useful.

A request may lead to a question, a simpler existing option, a possible scope or a clear explanation that we cannot support it.

  1. 01

    Describe the task

    What do you need to do, who would use the result and where does the task get stuck?

  2. 02

    Review a possible next step

    A person reviews practical benefit, barriers to access, feasibility and the resources the work would need. Writing polish and a public story are not selection criteria.

  3. 03

    Agree the whole arrangement

    Before a build: the result, how you will check it, costs and funding, information access, ownership, export and support.

  4. 04

    Check it with the person who will use it

    A finished page is only a step. The test is what someone can now do—and whether they can keep doing it after handoff.

Your information and choices

Help without
giving up control.

The first request asks what you need to do, who would benefit, a name you would like us to use and a safe email address. Group details, a useful first improvement, barriers and constraints are optional. It does not ask for attachments, passwords, account numbers, medical or legal records, or proof of hardship.

Permission to review a request and reply is separate from permission to publish a story, testimonial or reusable work. Political agreement is not a condition of help.

Before real requests open, we will name who reviews them, the reply route, how long information is kept and how to correct or withdraw a request.

Community Builds supports technology and practical methods. A request does not provide emergency help, legal representation or clinical care.

Community Builds privacy and choices

Explore the working journey

See both sides
of a useful request.

Walk through a fictional request, then use the practice review desk to prepare a clear next step.

Open the practice workspace