Updated November 8, 2026
A website brief should describe what a visitor needs to accomplish. “Modern, premium and mobile-friendly” gives a design team very little to test. “A business owner can understand our three services, choose French or English and send a relevant enquiry from a phone” is a more useful starting point.
For companies serving Montreal alongside Miami or Beverly Hills, the work includes content ownership and language decisions as well as layout. Use the sequence below to organize those decisions before production starts.
Map the visitor’s questions before drawing pages
List what someone needs to know before contacting you: what you offer, whether it suits their situation, where you work, how the process starts and what information to prepare. Give each important question a home in the sitemap.
A compact service business might need a homepage, individual service pages, an about page, accurate location information, a contact route and a small set of helpful guides. Add pages because they answer distinct questions. A menu with many similar labels can make the choice harder.
For each page, write four items: intended reader, question answered, evidence or explanation provided, and next action. If two pages have the same four items, consider whether they should be one page.
Plan bilingual content as a production task
Decide which pages need French and English versions, who writes them and who approves terminology. A Montreal service explanation may require an adaptation of the message, not a word-for-word conversion. Allow enough room for both versions in navigation, buttons and forms.
- Maintain a list of page pairs and their publication status.
- Keep names, service terms and product descriptions in a shared terminology sheet.
- Review links, form instructions, error messages and confirmation text in both languages.
- Make the language switch lead to the corresponding page whenever one exists.
- Decide who updates the other language when a service changes.
The English material can support Miami and Beverly Hills readers without making assumptions about every visitor’s preferred language. Build the language plan around the actual people the business serves.
Design a contact journey with a clear finish
Decide what happens when someone submits or prepares an enquiry. A form submission, an email-app draft and a booked appointment are different outcomes. The button label and confirmation message should describe the actual action.
Ask only for information needed to respond. A first enquiry may need a name, reply address, service and short description. Requesting detailed financial or confidential project material at this stage can create unnecessary friction. Provide a suitable private route if such information becomes necessary later.
Test a realistic scenario: a Montreal owner opens the French service page on a phone, reads the scope, sends a question and receives the expected response instructions. Then test the English route from a Miami service page. Record any point where the next step becomes unclear.
Review a real page before approving a design system
Use approved copy and actual images in the first representative page. Placeholder text hides problems with line length, hierarchy and missing information. Test the longest realistic heading and a French paragraph before approving the layout.
Use meaningful headings that describe the sections beneath them. The W3C’s heading guidance explains how heading structure supports navigation, including assistive technology. Your review should also include readable contrast, labelled controls, keyboard navigation and visible focus.
Ask the team to demonstrate the page with a narrow viewport and enlarged text. A page can fit a phone screen while still being difficult to read or use. Test menus, consent controls and any sticky button together, since they can compete for the same space.
What is responsive web design, and how do you review it?
Responsive web design adjusts a page’s layout to the space available. It can move columns, resize media and change navigation so the same information remains usable at different widths. Shrinking a desktop screenshot is not enough. The reader still needs a clear order, readable content and controls that work.
Test a customer task, not just a screen size
For a fictional bilingual service business, use one task in each language: find the relevant service, understand its limits and reach the appropriate enquiry route. Start on the service page rather than assuming every visitor enters through the homepage. Use approved, realistic copy, including the longer language version and a plausible validation error.
Agree several review widths with the design team. For example, a desktop, a tablet-sized layout and a narrow phone view can reveal different problems. These are project review examples, not proof of accessibility conformance or coverage of every device.
- Reading order: when columns stack, the heading, explanation and next action still follow a sensible sequence. Important service limits should not move below a large unrelated picture.
- Navigation: open and close the menu, select a service and use the language switch. Confirm that a sticky banner or consent control does not cover the choice.
- Text and media: enlarge the text and inspect the longest heading. Paragraphs should remain readable; essential words in a graphic must not disappear in a crop.
- Forms: find the labels, read the instructions and correct an invalid entry. Check that the error remains near the relevant field and that the button describes the actual action.
- Next step: a contact link, submitted message and confirmed appointment are different outcomes. Verify the promised result through an agreed test rather than inferring it from the layout.
Record a defect so the team can fix it
Write the exact public URL, language, viewport, task, observed problem and expected behaviour. For example: “At the agreed narrow width, the French service menu opens behind the contact banner, so the second item cannot be selected.” Attach an approved screenshot without customer information and name the person who will retest the repair. “Mobile looks wrong” gives the developer much less to work with.
The W3C’s reflow explanation describes keeping information and functionality available when content is enlarged. Its forms tutorial covers labels, instructions and feedback. A visual phone check addresses only part of that work; keyboard and assistive-technology testing need their own agreed scope.
Repeat the affected task after a repair and check the other language for the same issue. Record the actual result before closing the defect. Our web design service can be scoped around a representative page first, with a wider review agreed when the evidence calls for it.
Separate public evidence from private material
Create an approval column in your content inventory. Mark each photo, testimonial, project description or document as approved for public use, restricted to a private review or awaiting confirmation. A filename is not proof that an image can be published.
Where a portfolio is private, test the page while signed out and check the underlying media protections with your website team. Hiding a project from the menu is not an access control. The public website can still explain your services through methods, deliverables and approved illustrations.
A launch checklist with named owners
- Content: every page has approved copy, correct contact details and working internal links.
- Languages: French and English journeys are complete, with an owner for future changes.
- Images: approved rights, useful descriptions, appropriate file sizes and clear mobile crops.
- Contact: enquiry routes tested, recipient checked and confirmation wording accurate.
- Search: public pages have suitable titles, preferred URLs and sitemap inclusion; restricted material stays excluded.
- Measurement: distinguish interest actions from received enquiries and sales.
- Handover: confirm ownership, editor access, backups, maintenance responsibilities and the process for urgent corrections.
What belongs in the proposal?
Ask the agency to state page scope, languages, content responsibilities, revision stages, integrations, testing and ongoing costs separately. Clarify whether writing, translation, photography, hosting and maintenance are included. A lower initial figure can cover a smaller scope.
You should be able to read the proposal and explain who supplies each item, who approves it and what counts as completion. That shared understanding is the foundation for a website your team can maintain after launch.
Plan your next step
Explore The Gate Agency’s services in Miami, Montreal (Montréal en français) and Beverly Hills. Use our project brief checklist to organize a first conversation, or tell us about your project. Private work can be discussed through an appropriate private portfolio review.

