Skip to content
Work in progress. This site is a prototype. Programs, dates and company details are provisional and may change.

Update your company

For companies

Update your company

Your company's page is built from your company's own Google spreadsheet. Edit the spreadsheet and the page updates itself — you never need to ask anyone to edit a web page.

  1. 1

    The program team creates your spreadsheet

    Every company gets its own Google Drive folder and spreadsheet. Google emails your company's owners an invitation to edit it. Only your company can edit it, and you cannot edit anyone else's.

  2. 2

    You fill it in

    Start with the Start here tab. Every column heading has a note saying what it wants — hover over it. Put logos and photos in your company folder and paste their link.

  3. 3

    The program team publishes it

    Nothing appears on this site until your company is published. After that, your edits go live on their own within a few minutes.

No spreadsheet yet, or lost the link? Ask your program coordinator. It is in the Google Drive of whoever was listed as your company's owner.

What is in the spreadsheet

TabWhat it is for
CompanyWho you are: tagline, mission, vision, strategy, brand colours and logo. One answer per row.
Required: Company name, One-line tagline, Primary sector, Mission statement, Vision statement, Company strategy, Primary brand colour, Page background style
PeopleYour board, leadership team and mentors. One row per person.
Required: Full name, Role title, Where should this person appear?
DepartmentsHow the company is organised, with starting and target headcount. One row per team.
Required: Department or team name
RolesThe positions students can apply for, and the skills that help. One row per role.
Required: Role title, Open to, What the role involves
ProjectsConcrete examples of what students would work on, written as an A3: the problem, the current state, the plan, and the technology and roles involved. One row per project.
Required: Project name, Project summary, Status, Problem statement

Writing a project

Projects are what students read most closely, so they are the part worth getting right. Describe at least two. Keep the summary to two or three sentences, then use the A3 columns for the detail — only the problem is required, but a student deciding where to apply will read all of it.

Problem statement *
What problem does this solve, and for whom? One or two sentences a student can understand.
Background
The context: why this matters now, and anything a newcomer needs to know first.
Current state analysis
How things work today and what is wrong with that. Facts and numbers where you have them.
Drivers
What is pushing this forward: client need, regulation, cost, opportunity.
Plan / target state
What done looks like, and the major steps to get there.
Technical architecture
The intended shape of the solution: the main components, where they run and how they talk to each other.
Languages, frameworks and tools
Comma separated, e.g. Python, FastAPI, PostgreSQL, React, AWS. Shown to students as the skills they would use.
Implementation approach
How the work will be done: method, stages, testing, and how students join and hand over.
Roles this project needs
Comma separated role titles from your Roles tab, e.g. Backend Engineer, Data Analyst. Links the project to those roles on the website.

Please do not

  • Rename, reorder or delete the column headings. The site finds your data by them. Adding your own columns at the far right is fine; they are ignored.
  • Change your company name in the spreadsheet. It is part of your web address, so the program team changes it for you.
  • Share the spreadsheet more widely than your company. Anyone with edit access can change your public page.

See exactly how this site is built →