A website brief for an NGO, foundation or public programme should explain the purpose, audiences, required actions, content, responsibilities and delivery constraints. It should also distinguish the public information website from any application, payment or private record-management system.
The brief gives the organisation and provider a shared basis for scope, proposals and review. It does not need to prescribe every technical detail before discovery, but it should make the real requirements and unresolved decisions visible.
For programmes involving several partners, the approval process deserves particular attention. A website can be technically ready while the information it needs remains unconfirmed.
1. Describe the organisation and the programme
Identify the commissioning organisation, programme purpose, intended beneficiaries, location or delivery area and relevant dates. Name the authorised project contact and explain the relationship between the institution and the specific initiative.
Separate confirmed details from proposals. If an activity, partner role or date remains provisional, mark it clearly in the working brief and identify who can resolve it.
Include the organisation’s relevant commissioning and approval requirements. Its responsible team should define those processes rather than expecting the website provider to infer them.
2. Map the audiences to practical tasks
A programme website may serve applicants, confirmed participants, partners, the media and the general public. Each group needs a clear route.
| Audience | Task to support | Requirement to clarify |
|---|---|---|
| Prospective applicants | Assess suitability and apply | Eligibility, dates, preparation and application route |
| Participants | Find instructions and current updates | Schedule, venue, preparation and support contact |
| Partners | Understand the programme and collaboration route | Approved role descriptions and responsible contact |
| Media | Find accurate background and request information | Approved announcements, assets and media contact |
| Public and stakeholders | Understand activities and inspect available reports | Verified records with dates and context |
Use only the audiences that matter to your programme. The table is a planning example, not a mandatory site structure.
3. Define the boundaries of the system
State whether the website will publish information, direct people to an approved external form or include a registration system. Those are different deliverables.
If the brief includes accounts, uploads, review queues or notifications, describe the workflow and staff roles. If payments are involved, identify the actual process and external service responsibilities.
A public enquiry route should not silently become a large beneficiary database. Agree what information is needed, where it belongs and who manages it.
My website development and portal and web application services can be scoped separately where the programme needs both layers.
4. Prepare the content and evidence inventory
List available text, approved programme information, photographs, logos, videos, reports and resources. Record what needs writing, checking or permission before use.
Identify the source for material claims. Intended reach, registrations, attendance, completed participation and demonstrated outcomes should remain distinct. Do not ask a provider to turn an unverified ambition into a published result.
For each content item, assign an owner and approver. Keep private records and restricted materials out of general proposal packs.
A practical reference: ARISE Youth Skills Week
My ARISE Youth Skills Week case study describes a website connecting programme information, participation routes, partner visibility and media destinations. My role recorded there is website design and development.
For a new brief, this suggests useful questions: which audiences need separate routes, who owns the information and which actions depend on systems outside the public website? The programme’s delivery and participant outcomes remain the responsibility of its organisers and partners.
5. Agree a workable approval process
Identify who can approve content, partner references, design, technical scope and launch. Where several institutions contribute, decide how feedback will be consolidated and how conflicting instructions will be resolved.
Record approval dependencies in the schedule. A provider should know whether one contact can sign off or whether a formal review stage is required.
Keep versioned review material and a clear decision record. This helps the team understand which wording and design were agreed, particularly when programme details change.
6. Prioritise a useful first phase
List essential launch requirements separately from later ideas. A focused first phase might include an accurate overview, eligibility, participation instructions, approved partner information and a working contact route.
More complex systems should follow a defined operational need and the team’s ability to manage them. A feature is not ready for the brief simply because it appears on another organisation’s website.
Describe the task, the responsible people and the expected result. The technical approach should follow that requirement.
7. Include accessibility and information handling
Explain the audience’s likely devices, connectivity and language needs. Agree requirements for readable mobile pages, meaningful image descriptions and appropriate alternatives for important media.
Where a formal accessibility standard or specific information-handling requirement applies, name it in the brief and assign the relevant specialist review. A responsive layout alone does not establish compliance with every requirement.
For application records, document the intended access and retention process with the responsible organisational team. The technical provider needs approved requirements and a clear point of contact.
8. State budget, timing and dependencies
Provide a realistic budget range where possible and identify what it must cover. Content writing, photography, registration systems, hosting, training and ongoing care may be separate work.
State the dates that matter and why. A public launch deadline should account for content preparation, approvals, development, testing and corrections.
Ask providers to identify assumptions and dependencies in their proposals. This makes quotations easier to compare than asking each supplier to guess an undefined scope.
9. Define acceptance through useful checks
- The approved programme details appear accurately.
- Visitors can find the relevant participation route.
- Authorised test submissions reach the intended destination.
- Confirmation messages describe the actual process.
- Important pages and documents work on representative devices.
- Staff can perform agreed update tasks.
- Access, recovery and support arrangements are documented.
Adapt the checks to the system. A review of the visual design is only one part of accepting the work.
10. Plan handover and the programme archive
Agree account ownership or management, renewals, documentation, training and the support route. Identify who keeps dates and contact details current.
Also define what happens when the programme closes. Registration may need relabelling, while reports and permitted resources remain useful. A recurring programme needs a clear distinction between editions.
A short brief you can adapt
Our organisation needs a website that explains the programme, helps the intended audience assess participation and provides current instructions. Please propose a structure based on the audiences and tasks in this brief.
The public website and any private application workflow should be identified as separate scope components. We will supply or approve programme requirements, partner information and permitted assets. Please list missing inputs and dependencies.
Your proposal should describe deliverables, exclusions, content responsibilities, review stages, testing, handover, recurring costs and support. The first phase should prioritise the confirmed launch needs, with later functions priced separately.
This is illustrative planning text, not a complete procurement or contractual document. Add the actual programme details and the organisation’s requirements before using it.
Explore my government and NGO programme services, content development, consultation and selected projects for relevant support.
Frequently asked questions
Do we need a full technical specification before requesting proposals?
Not always. Describe the users, tasks, constraints and unresolved decisions. Ask the provider to clarify technical implications.
Should the provider write the programme’s outcome claims?
They can help explain approved evidence, but the responsible organisation needs to verify and approve the claims.
Can several partners contribute to the brief?
Yes. Agree a coordinator and a clear approval route so that the provider receives consistent decisions.
Discuss your website or digital project
Send me your current website, the problem you want to solve and the people you need to serve. We can review the requirement and agree a practical scope, timing and quotation.
- WhatsApp: Start a conversation on WhatsApp.
- Contact page: Send a project enquiry.
- Email: [email protected].
- Phone: +234 703 799 7791.
Based in Uyo, Akwa Ibom State, Nigeria. Remote working arrangements can be discussed.





