Skip to content
Guides

Before you add a website feature: write a one-page brief

“Add online bookings” sounds like one request. It could mean a simple enquiry form, a calendar with available appointments, or a paid reservation system with cancellations. Those are different projects, even if the button on the homepage says the same thing.

Before asking an AI editor to build a feature, write a short brief that explains the visitor’s job, what information is needed, and what a successful result looks like. You do not need a technical specification. You need enough clarity to prevent a convincing-looking interface from hiding an incomplete workflow.

1. Name the visitor’s task, not just the feature

Start with a sentence: “A visitor needs to ___ so they can ___.” For example: “A visitor needs to request a consultation so our team can confirm a suitable time.” That sentence makes it clear that submitting a request is not the same as securing an appointment.

Then define the smallest useful version. A consultation request might need a service choice, contact details, and a preferred day. Live availability, payment, customer accounts, and automated reminders can remain outside the first version. These are planning examples, not a claim that every workflow is available as a ready-made OffPress feature.

2. Decide whether this is content or a workflow

A list of services may only need an editable page. A large directory may need consistent records that can be filtered. An application process needs somewhere to receive submissions and someone responsible for handling them. Describe how often information changes and who will maintain it; do not prescribe a complex system before establishing the need.

In OffPress, the workspace guide distinguishes Site Design, where you change layouts and site behaviour, from Content Admin, where you manage posts, media, forms, and installed site features. It also explains that optional features are not all enabled automatically. Check Plugins for what is available rather than assuming that a requested feature is already installed.

3. Specify who can see each piece of information

Make a short inventory of the information the feature uses. For every item, state who supplies it, who can read it, and why it is needed. In a consultation request, the service description may be public, while the visitor’s email and message should be visible only to the team handling the enquiry.

Do not rely on a field being absent from the page as proof that it is private. Put the access requirement in the brief and ask for it to be verified. If personal accounts are involved, explicitly require that one customer cannot read another customer’s records. Collect only what the workflow needs, and decide who will handle correction or deletion requests.

4. Write down what happens after the click

Follow the request beyond the success message. Where is it saved? Who checks it? Is a notification required? What should the visitor do if no reply arrives? If the feature depends on an email connection, payment service, or calendar, identify that dependency and confirm whether it is configured before describing the workflow as ready.

Keep interface wording honest. “Your request has been received; we will confirm availability” is different from “Your appointment is booked.” For a deeper look at checking the handoff, use our contact-form testing checklist.

5. Turn “it works” into observable tests

Choose a handful of checks before implementation. For a request form, you might require that an empty required field shows a useful error, a valid submission is saved once, the team can find it, and the visitor receives accurate next-step wording. Also check keyboard access and a narrow mobile screen. Use fictitious test details rather than a real customer’s information.

Include one failure case and one access check. For example, what happens if delivery fails, and can a signed-out visitor see private submissions? Ask for unresolved dependencies to be reported plainly. A screenshot can show that a button exists; it cannot establish that the entire workflow succeeds.

A reusable brief for your next AI request

Copy this outline and replace the brackets with your own decisions:

  • Visitor task: [Who needs to do what, and why?]
  • First version: [What is included? What is explicitly excluded?]
  • Information and access: [What is stored, who supplies it, and who may read it?]
  • Handoff: [Where does the result go, who handles it, and what does the visitor hear?]
  • Dependencies: [Which connections, permissions, or owner decisions are required?]
  • Acceptance checks: [How will we verify success, failure handling, privacy, and mobile use?]

Finish the request with: “Preserve unrelated content and design. Check existing features before adding anything new. Do not invent service connections or mark an untested dependency complete. Report what was verified and what still requires my input.”

Keep launch and ongoing ownership separate

The OffPress workspace guide describes Publish as releasing the current design and code to the public website. Treat that release as a distinct step, not as proof that notifications, permissions, or external connections have been tested. After release, repeat the critical visitor journey on the public site and assign someone to maintain the information and handle incoming requests.

A useful feature brief is not the longest one. It is the one that lets you say, with evidence, what visitors can do, what your team must do next, and what is deliberately not part of the first release.

← All articlesRebuild my site — free →