Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

What Should You Include in a Web Application Brief Before Development Begins?

What Should You Include in a Web Application Brief Before Development Begins?

The practical answer

A useful web application brief explains the problem, users, essential workflows, data, integrations, responsibilities and acceptance checks. It separates launch requirements from later ideas and records the decisions that still need to be made.

“We need a portal like this one” can start a conversation, but it is not enough to define a development project. Two applications may have similar dashboards while handling completely different responsibilities, payment rules and approval processes.

A web application development brief gives the project a shared starting point. It helps you compare proposals, recognise missing work and decide whether the delivered system does what your organisation actually needs.

You do not need to describe the database or choose a programming framework before talking to a developer. You do need to explain the work. My web application and portal service starts with understanding those operational requirements.

Describe the present problem in observable terms

Explain what happens today, where it becomes difficult and who experiences the difficulty. “Our process is manual” is a starting point. “Staff copy payment references from three spreadsheets and cannot reliably match them to applications” is a more useful description.

Include the volume where it is known, the busy periods and the consequences of an error. Distinguish measured facts from estimates. If the organisation does not yet know how many applications arrive each month, state that instead of filling the gap with an impressive number.

Define the desired change as a task or outcome within the application’s control. A system may help staff review submissions consistently. It cannot guarantee that every applicant completes a form or that a business reaches a revenue target.

Identify users and decision makers

List the people who submit information, review it, approve decisions, maintain records and provide support. Name the organisation’s project owner and the person who can resolve a disagreement between departments.

For each user group, describe what it needs to accomplish. Record whether people use shared office computers, personal phones or both. Consider connectivity, accessibility and the amount of help a first-time user may require.

A sponsor who approves the budget is not always the same person who uses the system every day. Both perspectives should inform the brief. Otherwise, a project can satisfy a management presentation while creating extra work for the operating team.

Write the main workflow from beginning to end

Follow one ordinary record through the process. For an application portal, that could mean account creation, form completion, payment, submission, review, a decision and notification.

Then describe exceptions. What happens if payment succeeds but the applicant closes the page? Can a submitted form be corrected? Who handles a duplicate record? How does the user learn that more information is needed?

Use the following structure for each important workflow:

Part of the workflow Question the brief should answer
Starting point Who starts the process, and with what information?
Main steps What must happen before the next step becomes available?
Decision Who can approve, decline or return the record?
Exception What happens when the normal path fails?
Completion What does the user receive or see afterwards?

Write these answers before arguing about the colour of the dashboard. They determine much of the work behind the screen.

Separate launch scope from later improvements

Divide requirements into essential for launch, useful after launch and unresolved. Explain why an essential item is essential. A feature that supports a mandatory operating step has a stronger claim than a feature copied from an unrelated platform.

Avoid using “and anything else required” as a substitute for scope. It makes proposals difficult to compare and can turn small changes into disputes. Record how additional requirements will be estimated, approved and scheduled.

Dependencies also matter. A payment workflow may depend on a verified payment account. Email notifications depend on an agreed sender and working delivery. Content may depend on a department supplying accurate instructions. Identify who provides each dependency.

Explain data and external connections

List the information the system must collect and the reason for collecting it. Identify existing spreadsheets or records to import, their condition and who will check the imported result.

For integrations, name the service, the account owner and the actions required. “Connect payments” may include collecting money, verifying the transaction, matching it to a record and handling failures. Those are separate responsibilities.

Record whether the application needs to exchange data with an existing school system, accounting tool or email service. Ask the developer to confirm access and technical feasibility before treating an integration as settled.

Include access, privacy and operational expectations

State who may see, edit, approve and export each type of record. Describe sensitive information and the organisation’s requirements for access, retention and correction. Your developer can advise on implementation, while the organisation remains responsible for deciding its operating rules.

Also discuss backups, recovery, support hours and incident reporting. Avoid promises such as “the system must never go down” without defining a realistic service arrangement. Ask what is included, what depends on hosting and what needs separate ongoing support.

The guide to choosing a school website developer provides related questions about ownership, support and project handover.

Define how you will accept the work

Replace vague requirements with observable checks. Instead of “the dashboard must be user-friendly”, describe a task: an authorised reviewer can find an assigned application, see its submitted documents and record a review without assistance.

Agree who supplies test records, who performs acceptance checks and how issues are classified. Distinguish a defect against agreed requirements from a new request. Decide how fixes are verified before sign-off.

Include the devices and browsers that matter to your audience. Ask for a demonstration of failure paths as well as the successful route. A polished demonstration using perfect data should not be the only launch check.

Set out ownership and handover

The brief should identify the expected ownership of the domain, hosting, application code, designs, data and third-party accounts. The final agreement should make the actual rights and responsibilities clear.

Ask what documentation, training and access will be handed over. Clarify who handles maintenance, whether support is time-limited and how the organisation can continue operating if the original developer is unavailable.

Provide a realistic target date and explain what drives it. If a registration window cannot move, the team may need a smaller launch scope. A deadline is easier to plan around when its reason and dependencies are visible.

Frequently asked questions

Must the brief be a long technical document?

No. A concise, accurate brief with workflows, priorities and open questions is more useful than a long list of technical terms copied from another project. Complex applications will need more discovery after the initial brief.

Should I choose the technology before requesting proposals?

Only where an existing system, team capability or other real constraint requires it. Otherwise, ask developers to explain their recommendation, maintenance implications and trade-offs.

Can requirements change after development starts?

Yes. Agree a change process that records the request, its effect on cost and timing, and the decision to proceed. The objective is to make change manageable rather than pretend it will never occur.

Start with a brief you can discuss

Bring your current process, a few representative records, the users’ responsibilities and the decisions you have not resolved. That gives a developer something concrete to investigate and gives you a stronger basis for judging the proposed solution.

Further reading

Reference addresses are provided as plain text for copying.

  • https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html

Discuss your next step

Have a portal or web application idea? Send a short account of the current process, the users involved and the outcome you need. I can help turn it into a scope that is easier to estimate and review.

Explore web applications and portals

  1. Start on WhatsApp
  2. Send an enquiry through the contact page
  3. Email [email protected]
  4. Call +234 703 799 7791
Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.