Stakeholders agree once
Sessions surface competing priorities while they are still cheap to reconcile, not after a design has been drawn to one of them.
Check the school’s publishing and admissions systems before specifying a build.
Discovery examines the public website, content ownership and the systems behind calendars or admissions handoffs. The output distinguishes verified requirements from assumptions and keeps student records outside the default website review.
A few clients we’ve worked with
What we do
Website discovery for schools: Content inventory, Workflow review, System requirements.
Decisions that shape the work.
Where are current calendar and programme records maintained?
Which external system controls applications?
What discovery settles before design starts.
A project can be ready for discovery before it is ready for design. Finding the unresolved questions early is what keeps the build from pausing.
Dependencies appear early
Technical constraints and the systems the website has to live with are identified before they become a mid-build surprise.
The next stage can be scoped
A brief naming the decisions and open questions lets design, content and development be quoted against something real.
Website discovery: scope of work.
The brief records the website scope, approved source material and responsibilities for review.
Content inventory
List programmes, departments, policies and public files with their owners.
Workflow review
Follow routine publishing and enquiry tasks using documentation and synthetic examples.
System requirements
Verify supported handoffs and access needs before defining integration work.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
What you receive.
The agreed engagement produces the following artifacts.
- 01
A page and document inventory.
- 02
A publishing and enquiry workflow map.
- 03
A requirements and dependency register.
Our process
How the work runs.
Inspect public content
Record existing pages and their source systems.
[ 01 ]
Trace staff tasks
Review how information is approved and updated when the main editor is unavailable.
[ 02 ]
Define the build
Assign unresolved provider and content questions before implementation.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedWebsite discovery for schools: questions.
Do you need student records?
Public website discovery can use documentation and synthetic examples. Access to student records is not part of this default scope.
Will every admissions platform integrate directly?
No. Its supported interfaces, account permissions and intended actions must be verified first.
Website 2.0 combines strategy, design, development and launch in one engagement.