Development Agency
Contact Sign in Get a project quote

Service

Student accommodation software development

For operators of purpose-built student housing and university accommodation teams who need applications, allocation, tenancy agreements, instalments, arrivals and maintenance to run as one system built around the academic year rather than a letting CRM stretched to cover it.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

Student accommodation sells a bed for an academic year and does most of its work in two bursts: the application and allocation season through spring and summer, and arrivals weekend in September.

  • Applications arrive through a web form into a spreadsheet, preferences for flatmates, quiet floors and en-suite rooms are typed into a notes column, and allocation is done by the accommodation manager over several late nights with a printout of the room list.
  • A student who was offered a room and never replied holds it for weeks; a student on the waiting list is told there is nothing left while three rooms sit on expired offers.

Where it gets harder

Tenancy agreements are generated from a template, emailed as attachments and signed by scanning or by a separate e-signature account that nobody reconciles against the room list, so the manager cannot say which of four hundred rooms have a signed agreement, a guarantor and a first instalment paid.

  • Instalment dates are tied to term dates that differ by university and by course start, and the finance team chases late payments from a list that is already wrong.
  • On arrivals weekend every student turns up between ten and two on the same Saturday because nobody scheduled slots, keys are handed out from a clipboard, and inventory forms go missing.
  • Maintenance requests then arrive by email and group chat for the rest of the year with no record of which flat, which room or which contractor.

Scope of the service

What the build covers

A custom student accommodation build normally covers:

  • A building Flat and room register with room types and academic-year tenancy periods you define, including short and summer lets
  • An application form capturing course University, preferences and accessibility needs
  • Allocation tooling that proposes rooms from preferences and capacity With offers that expire and return the room to the pool, and a waiting list that is worked in order
  • Tenancy agreement generation From your templates with electronic signature and a signed copy against the tenancy
  • Guarantor records with their own signature step
  • Instalment schedules aligned to the term dates of each university or course with payment recording and reminders
  • Arrivals scheduling With time slots per building and a check-in checklist with inventory and key issue
  • Maintenance requests from students with status Contractor assignment and completion notes
  • Room swap requests with approval

How discovery works

Discovery walks through the year with you: when applications open and close, how allocation decisions are made and who approves them, which agreement templates and guarantor rules apply to which room types, how instalment dates are set per university, how arrivals are staffed, how maintenance is triaged and whether a university system sends nominations or receives occupancy data. Each becomes a named stage in the scope document: apply, allocate, sign, pay by instalment, arrive, request maintenance, swap, check out.

Deliberately out of scope

  • The finance ledger itself, access control hardware beyond recording key or fob issue, pastoral case management and wellbeing records, which stay in their own systems with integration where it earns its place. Deposit protection and tenancy law are handled as records, documents and dates in the system
  • The system does not claim to make the operator compliant

When the scope grows

Scoping scenario

An operator with three buildings and nine hundred beds serving two universities with different term dates, a nomination agreement with one of them, four agreement templates and a summer-let business needs allocation across buildings and instalment plans that differ per university. That is a different build from a single eighty-bed hall with one template, and the scope document will say so.

Deliverables

What you receive

  • Discovery notes from a walk-through of the accommodation year, including allocation rules and the current agreement templates
  • A written scope document naming each stage from application to check-out, the universities and templates in scope and what is excluded
  • Design of the application form, the allocation board, the tenancy record and the arrivals check-in on phone, tablet and desktop
  • The build, deployed to your hosting or ours
  • Migration of the room register, current tenancies, guarantors and open maintenance requests from your spreadsheets or system, where relevant
  • Agreement templates set up for generation and signature with a test signing run
  • Training for accommodation managers, finance staff and the maintenance team, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to the room list, current application data, agreement templates, instalment schedules and any university nomination files; contacts named for allocation, finance and maintenance.

    Project stage: Onboarding

  2. Planning

    Discovery with the accommodation manager, a finance contact and the maintenance lead; allocation rules, templates and the scope document are agreed with milestones timed around the application season.

    Project stage: Planning

  3. Design

    Clickable designs of the application flow, the allocation board, the tenancy record with signature and instalment status, and the arrivals check-in on a tablet.

    Project stage: Design

  4. Development

    Built in stages: register and applications first, then allocation, agreements and guarantors, then instalments, arrivals and maintenance.

    Project stage: Development

  5. Client review

    The team runs a mock allocation on last year's applications, signs test agreements and walks a mock arrivals morning, telling us where the rules differ from practice.

    Project stage: Client review

  6. Revisions

    Allocation logic, template fields, instalment rules and check-in steps are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Rooms and current tenancies migrated, signature and payment reminders tested on addresses you control, arrivals slots published, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The next application season runs on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Electronic signature services for tenancy agreements and guarantor forms
  • Card payment and direct debit providers for instalments and booking fees
  • University accommodation and nomination systems that send applicants or receive occupancy data
  • Finance and accounting systems for instalment reconciliation and arrears
  • Email and SMS providers for offers, reminders and arrivals information
  • Access control and fob systems for recording key and fob issue
  • Document storage for inventories, signed agreements and certificates
  • Student identity verification or right-to-rent check providers the operator already uses

How we would approach it

Worked example

Concept demo

A three-building operator serving two universities

In this scoping scenario, an operator with nine hundred beds across three buildings allocated rooms from spreadsheets each summer, held offers open indefinitely and ran instalments on a single date pattern that did not match either university's term dates. The scope we would propose: one register across the buildings with room types and tenancy periods per university, an allocation board that proposes rooms from preferences and flags accessibility needs first, offers that expire after a set number of days and release the room to the waiting list automatically, agreement generation from four templates with signature tracked against the tenancy, guarantor signature as its own step, instalment plans per university with reminders, and arrivals slots per building so Saturday is spread across the day.

The reason this needs a custom build is that nominations, templates and instalment dates differ by university, which a letting CRM models as a single process for a single landlord.

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of buildings, flats and beds, and how many room types and tenancy periods exist
  • Allocation rules, preference weighting and whether a waiting list is worked automatically
  • Number of agreement templates and whether guarantors sign separately
  • Instalment plans per university or course and the payment providers involved
  • University nomination or occupancy data exchange and its format
  • Arrivals scheduling and the check-in checklist with inventory
  • Maintenance requests, contractor assignment and room swaps in scope
  • Hosting choice: your own hosting or ours

Start from a package

Student accommodation package

Applications, allocation with expiring offers and a waiting list, e-signed tenancies, term instalments, guarantors, arrivals slots and maintenance requests for student housing.

Custom build
View the package

FAQ

Frequently asked questions

How do you decide between a custom build and the package?

Discovery compares your accommodation year with what the student accommodation package does through configuration. A single hall or a small portfolio with one university, one or two templates and standard instalments usually fits the package. Nominations from a university system, allocation rules that span buildings or several instalment calendars point to custom work, and we say which before anything is quoted.

Can the system exchange data with the university?

Where the university can send nominations or receive occupancy data in an agreed format, we build the import and export and name the format in the scope document. The university controls its side, so we test with sample files first and treat each exchange as its own piece of work.

How are tenancy agreements and guarantors handled?

Agreements are generated from your templates with the tenancy details filled in, sent for electronic signature and stored signed against the tenancy, with the guarantor completing their own signature step. The content of the templates and whether they meet the law is yours and your advisers'; the system tracks who has signed what and when.

What about deposits?

Deposit amounts, where they are held, references and return dates are recorded against the tenancy with reminders to the team, and deductions at check-out are logged with the inventory evidence. The system keeps the record; which scheme and process you use remains your decision.

Who owns the system afterwards?

You do. Source code and data are handed over at delivery, and your signature, payment and university accounts stay in your name. Hosting and maintenance are optional and separately agreed.

Get a project quote for student accommodation software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences