Running your studio on PWE Studio

00 · Before you start

Five screens, and three ideas that explain the rest

Your studio has its own address on the platform — a short URL name we call the slug, chosen when the studio is created. Everything below hangs off it. It is not permanent: ask us and we can change it, at most once a year. The old address keeps working forever as a redirect, because it is already on flyers and inside QR codes — and it is never given to another studio.

Three ideas worth five minutes now

1 · A credit is not a class

A credit is a prepaid unit of teaching time. A long class can consume more than one, which is why families are shown a credit balance rather than “classes left”. Credits are bought by top-up, deducted at check-in, and refundable. A “package” bundles credits for sale; the word plan is reserved for your subscription tier with us, and only the platform can change that.

2 · Families do not have accounts

There is no parent login. A family checks their own records with student name + registered phone + a six-digit access code your team hands them. The code is shown in plain text once, at the moment it is created, and never stored in a readable form. See section 08.

3 · Draft is not published

In Studio Admin, Save Draft changes nothing the public can see. Only Publish updates the public brand — and every publish keeps a version you can roll back to. Use the preview’s Draft / Live switch to compare your edit with the current site. After the write, the console checks the published version and every enabled public surface. A successful write that is still catching up is shown as Published, public pages still need verification; the saved content is safe and Recheck public pages retries the check.

01 · Day one

Put your website up before you put anyone in it

Everything on this screen is the owner’s. A manager who opens it is told to use the CMS instead — brand and public content are an owner boundary, enforced by the server rather than hidden in the interface.

1. Open /<slug>/studio-admin and sign in with the email and temporary password the platform gave you. Change the password immediately (minimum 8 characters).
2. Pick an industry preset. It fills slogan, hero copy, enquiry questions and FAQ, and marks one visual style as recommended. It does not select that style for you. Applying the preset overwrites the copy fields, so do it before you write. There is an Undo bar if you regret it.
3. Choose a visual style. Eight curated starting points plus Custom share the same palette and token engine. Arcade Lime is dark only; a mode a style does not offer is greyed out rather than approximated.
4. Fill in the studio details, hero, sections and enquiry questions. Space & Experience has its own panel for the place, atmosphere or online experience, separate from the principal biography. A section with no content stays hidden even when its switch is on.
5. Save Draft, preview, then Publish. The preview starts in the admin language, then its own language control can compare the portal and register page in either language, desktop or mobile.

1. The grouped workbench has twelve panels under four jobs: Brand & website, Admissions, Publish and Insights.
2. Draft previews the editor; Live loads the current published site. Compare either source in both languages and at desktop or phone width before publishing.
3. The save bar, always visible: apply a preset, open the site, save a draft, publish. It also tells you whether what you are looking at is public yet.

1. Family messages stay in Studio Admin, now under Admissions. They are staff copy templates, not an email or SMS sending system.
2. A stable URL such as ?view=messages opens the exact panel for a support handoff or a bookmarked operating step.

Publishing is gated on purpose

Publish runs three checks and will stop you: the studio name must be filled; the public essentials must be complete (hero title, enquiry title and intro, a phone number or email, and the principal’s name if that section is on — placeholder text is rejected too); and six contrast pairs across body text, secondary text and button labels must each reach 4.5:1.

Status colours follow the theme

The theme preview shows two groups: six theme colours (page, panel, accent, support, control boundary, focus ring) and three status colours (success, warning, danger) marked tuned to this theme. The eight curated styles carry 45 preset status values across their supported modes; Custom solves its values from the chosen accent. Success and warning stay readable and distinct from the accent. Changing style changes them. That is correct, not a bug.

02 · Enrolment

From an enquiry to a student record

Families submit from the portal or the standalone register page — same form, same queue. Both feed the CMS Pending tab, which carries a red count badge in the navigation.

1. Only the sections you filled in appear, in the order the template sets.
2. The visitor’s own language switch. Course names and work titles stay as your team typed them.

1. Your own questions, added in Studio Admin. Up to eight appear on the portal form.
2. The privacy tick is required, and the version of the notice in force is stored with the consent.

Each card shows name, contact, birthday, message, submission time, source (portal or quick register) and a status: pending, contacted, trial booked, following up, approved, enrolled, rejected, duplicate, lost, archived.

Approving creates the record

Enter a starting credit balance (zero is fine) and press Approve. The student record is created and the credits are posted in one step. Rejecting simply removes the card from the list.

1. Source and status on every card — at a glance, which came from the portal and which from the register page.
2. Set a follow-up date, or move the lead along: contacted, trial booked, still following up.
3. Approve with a starting credit balance and the student record is created in the same step.
4. One inbox, two tabs. The second holds booking requests from the public timetable — section 04.

What the family consented to is recorded

The enquiry form requires a privacy consent tick, and the consent is stored together with the version number of the privacy notice in force at that moment. Publication consent for student work is optional at this stage and recorded the same way. Both are append-only: a withdrawal is a new event, never an edit to the old one.

03 · Every day

The roster, and the two minutes at the start of class

Weekly classes are set up once — name, weekday, start time, length, capacity, students — and appear on that day’s list automatically from then on. You can also drop a student into a single day by hand. The default start time for new manual entries is a studio setting; changing it does not touch anything already saved.

1. Open Daily roster. It opens on today.
2. Check students in as they arrive. Each check-in deducts the credits for that class and writes a ledger entry. Batch check-in skips anyone already checked in or out of credits, and says so.
3. Checked in the wrong person? Reverse it. The credits go back, the attendance is marked reversed, and the ledger keeps a matching correcting entry. Nothing is erased.

A student with no credits left is stopped at check-in, with a prompt — not discovered at the end of the month. Birthdays live on the dashboard, under 「本周生日」: one tap copies a birthday message with the student’s and studio’s name already filled in. (Until v10.13 the same list also sat on top of the roster; it was the same students twice, and it pushed the register itself below the fold.)

1. Recurring classes. These drop into the day list on their own; editing and deleting them is an owner or manager job.
2. The week strip — student counts per day, so the shape of the week is visible before you open it.
3. The two calendar exports live here — see the warning above before forwarding either.

1. A teacher sees the class list and can check students in; adding or editing a class is not their job and the buttons are not there.
2. Check-in deducts the credits and writes the ledger entry in one action.

1. The course catalogue owns course names, age ranges, durations and prices; recurring class times still belong in the roster.
2. The help panel explains which changes affect future references and which do not rewrite saved attendance.

04 · Public timetable

The timetable a family can read, and the request they can send

The roster in section 03 is internal. This is its public counterpart: a page at /<slug>/timetable, linked from the portal, listing the classes you chose to publish for the weeks ahead. It has its own address rather than another band on the home page, because a family reading a timetable is comparing rows against a calendar — and because a timetable is a thing people forward to each other.

Being scheduled does not make a class public. Two decisions have to agree: the class itself must be ticked Show this class on the public timetable in the CMS, and the page must be switched on in Studio Admin → Brand & Website → Public timetable.

1. Switch on Public timetable page, and choose how many weeks to show — 1 to 4, two by default.
2. Write the page eyebrow and lead in both languages, the way you write any other public section.
3. Decide what each class shows: teacher, room, age range, finish time, places left, price. Teacher, room, age range and places left start on; finish time and price start off.
4. In the CMS, tick the classes you want on the page. A class left unticked stays invisible there no matter how it is scheduled.
5. Optionally switch on Accept booking requests. Only then does a class carry a button a visitor can press.

1. Brand & Website → Public timetable is where the page switch, booking switch and display window live.
2. Public timetable and Accept booking requests are separate decisions: publish the page first, then allow requests only if the studio wants them.
3. The weeks setting is also the booking window. In this example, two weeks are visible and bookable.

1. The public page shows only classes selected in CMS; the Request button belongs to a specific class.
2. The form asks for a full name, mobile number and optional message — no account or password.
3. Sending the form creates a request, not a seat. The studio reviews it in Pending and checks capacity when approving.

A field switch is a ceiling, not an instruction. Switched on, it shows the field when there is something behind it — a class with no room recorded never prints an empty “Room”. Turning everything on does not produce a page of blank labels.

A booking request is a request, not a seat

A visitor gives a full name and a phone number — no account, no password — plus an optional message. The request arrives in the CMS under Pending → Booking requests, and an email goes to the studio’s notification address. Nothing is held. Capacity is re-checked at the moment you approve, because a request nobody has looked at yet must not lock out a family who would actually turn up. What the visitor is told instead is how many requests are already waiting on that class — so a class with one place left and five requests does not disappoint four people by surprise.

Approving does one of two things, and it decides by itself. If the name and phone match exactly one student on file, the approval puts that student on that day’s roster. If they match nobody — or match two people equally well — it becomes a new enquiry in the Pending queue instead, so a first-time family is counted once, in the funnel they actually came through. Declining closes the request. Owner, Manager and Front Desk can make that call; see section 09.

The reply a visitor gets is identical whether or not that phone number belongs to an existing student. That is deliberate: a form answering differently would be a way to ask “is this person enrolled here?” about anyone. The match is made, but it goes into the record rather than into the reply.

05 · Money

The ledger is the balance. Nobody types over it.

A student’s balance is the sum of its entries, not a number stored somewhere and edited. Every movement records who did it, when, and why. That is what makes “how many classes are left?” answerable without anyone’s memory being involved.

Taking a payment

1. Search and select the student. Their photo, current balance and last three movements appear — check them before you touch anything.
2. Pick a package to fill in credits and amount, or type both by hand.
3. Choose the payment method, add a note if useful, and confirm. A ready-to-send confirmation message can be copied in one tap.

1. The student’s photo, current balance and last three movements — check them before you touch anything.
2. Packages fill in the credits and the amount; both can still be typed by hand.
3. Payment method and an optional note. The note is what makes the ledger readable a year later.

Refunds are a different permission

The refund mode is visible only to the owner and manager. It needs the number of classes to return, the amount, the method, and a mandatory reason. The confirmation dialogue shows the resulting balance before anything is written. The refund posts as a negative amount against revenue and the credits come straight off the balance.

Everything shows up in the operation log

Thirty kinds of action are recorded with a plain-language name and a one-line summary: new student, archive, roster changes, class changes, uploads, share links, access codes, courses and packages, exports, publishing, team changes. Filter by student, type or date range. Owners and managers can export CSV. Records are kept for two years, then cleared automatically — export if you need longer.

1. Filter by student, by action type, or by date range.
2. Every row names the person. That is the point of it — for you, and for them.

06 · Student work and consent

Private by default, published only on a recorded decision

This chapter is about student work. The studio’s own selected work is a separate public section — see section 07.

Teachers, managers and owners can upload to a student’s portfolio: photo, title, date, note. JPEG, PNG or WebP, up to 30 megapixels per image — larger files are refused with a message rather than failing silently.

A piece of work reaches the public gallery only if that student has a valid publication consent from the family. Withdraw the consent and every piece returns to private immediately — you do not have to hunt for them.

Share links are temporary by design

A share link is a login-free page for one student’s work, for sending to relatives or using in recruitment. Owners and managers create them; the expiry is 1 to 90 days, 30 by default, and the link is shown once. Revoking is deliberately easier than creating — anyone who can edit the portfolio, including teachers, can kill a link. Cutting off something that escaped should never wait for a manager.

1. Balance and recent movements sit with the record, so nobody is guessing about credits while a parent is waiting.
2. The portfolio. Uploading is a teacher’s job; publishing to the public gallery needs the family’s recorded consent.

1. The workspace answers how many works exist, how many are public and which students have work — without replacing the student record as the editing home.
2. A teacher can see the work queue and continue uploading from the linked student record; Front Desk has no portfolio entry.

07 · Selected Work

Show the work that represents your studio

Studio showcase is a curated portfolio for work owned by the studio or its principal. It gives visitors evidence of your practice, standards and point of view. It is not the student gallery: student work stays in the CMS and follows family publication consent.

Keep the two galleries separate

1. Open /<slug>/studio-admin → Brand & Website → Selected work. This tab belongs to the Owner; student records remain in the CMS.
2. Write the section eyebrow, title and lead in both languages. This copy introduces the collection; each work gets its own title and caption.
3. Create each work with a photo, a recognised video link, or both. Add a bilingual title, caption and optional category. A record with neither a photo nor a recognised video is not kept when saved.
4. Set an optional Featured rank on the work card. Lower numbers appear first; ranks 1–6 become the home-page preview, while blank ranks follow the existing order. The ranking is studio-wide, not separate per category.
5. Use Up and Down only for fallback order, then create up to eight categories. The standalone archive is available at /<slug>/showcase; each category can be shared with its own URL.
6. Choose Active, Draft or Archived. Active is eligible for public display within your plan; Draft is saved but private; Archived stays in the board but is not shown. When the Active quota is full, a new upload starts as Draft.
7. Save Draft → Preview → Publish. Save Draft leaves the public portal unchanged; Publish is the step that makes the selected work live.

1. The Selected work tab is under Brand & Website and is separate from student operations.
2. The board shows the plan’s public count and the photo upload route; saved records remain in this board.
3. Paste a YouTube, Vimeo or Bilibili link in the optional Video link field; the provider is identified before you save.

1. When the section is enabled and at least one Active item exists, Selected Work renders on the public page and in its navigation. The same ready check is shared by the portal, archive, timetable and registration footer, so an empty or withdrawn surface does not leave a dead link.
2. The home page shows the first six published works and links to the standalone archive; the archive uses the same ranking and stays separate from the student gallery.
3. The archive loads up to 12 eligible items per request. Scrolling loads the next page automatically, with a Load more button as a fallback. This page size is not the plan quota.

1. The page carries its own eyebrow, title and lead — the ones you wrote in Studio Admin. It is a page a family can bookmark and forward, which is why it has an address rather than a scroll position.
2. The published count is stated. It counts what a visitor can actually see, so it is the fastest way to check that a publish did what you expected.
3. Category filters appear only once two or more categories have work behind them. A filter that opens onto nothing is worse than no filter.

Know the limits before you publish

The quota controls how many Active works are shown, not whether your records are safe. Featured ranks are applied before the quota, so a downgrade may hide lower-ranked work without deleting it; an upgrade makes the remaining Active works eligible again in the saved order.

Photos are uploaded; videos are linked

Photos are compressed in the browser to a longest edge of 2,400 px before upload. JPEG, PNG and WebP are supported, and you can drag in a batch or choose several files at once. For video, paste a watch or share link from YouTube, Vimeo or Bilibili into the work card. The console identifies the provider immediately; it stores the validated provider and video ID, not the raw URL. A cover image is optional. If you add one, only that image uses media storage — the video file is never uploaded. On the public page, the player loads only after a visitor presses play.

08 · For families

The student area, and the code that opens it

This section is the one to read out loud to a parent. There is no account, no password and nothing to install.

A family touches two things without signing in anywhere: the student area below, which shows their own records and needs the access code; and the public timetable in section 04, which needs nothing at all and is where they can ask for a place in a class. Keep the two apart when you explain them — one is private and permanent, the other is public and open to anybody.

1. The student must have a phone number on file first — without one the system refuses to issue a code.
2. Open the student record, find Student area, press Generate. The six digits appear once. Copy them and hand them over in person or by private message.
3. The family enters name, registered phone and the code on the portal’s student area. They see credits left, next class, attendance history and their own work.

A lookup session lasts one hour, then asks for the three details again. Too many wrong attempts locks the code temporarily and says how long to wait. Regenerate invalidates the old code instantly and signs out anyone using it; disable closes self-service for that student entirely.

1. Name and phone must match the record exactly. Nearly every “it doesn’t work” starts here.
2. Six digits, shown as dots. Too many wrong tries locks it and says how long to wait.

Consent records are permanent. Session data is cleared after 30 days, but a family’s publication consent and any withdrawal of it are never deleted — they are the proof of what was agreed and when.

09 · Your team

Five roles, enforced in the backend

Only the owner adds, disables or re-roles a member (CMS → settings → team). Managers see the list and nothing more. Send temporary passwords over a channel you trust, and have people change them at first sign-in. Member count is capped by your subscription.

1. Account, team, operational defaults, maintenance and workspace links are sections of one settings page, not competing modal dialogs.
2. Courses and packages have moved to their functional workspaces, while Studio Admin remains the home for public brand and portal settings.

Front desk can approve or decline a class-booking request (section 04). Reception already handles incoming enquiries, and a booking request is an enquiry wearing a different hat — a role that can approve one but not the other is a rule nobody can explain at the counter. The permission stops exactly there: courses, capacity and the schedule itself remain Owner and Manager only.

Staff is a legacy general-purpose role, close to manager but without refunds, reports, export or share links. For new hires prefer the specific roles — a job title that matches the screen is easier to train.

10 · Invoicing

Before you can invoice anyone, tell us who you are

An Australian tax invoice has to carry the ABN of the business issuing it. Without it your family's accountant cannot claim the GST, so the document comes straight back to you. Settings has an Invoice details tab: legal entity, trading name, ABN, whether you are registered for GST, your address, and how you would like to be paid. Until it is filled in, invoices will not issue at all — and if an invoice charges GST while the ABN is blank, we refuse it rather than send something your customer has to ask you to redo.

1. Tick GST registered and the ABN becomes required — the database refuses to save the pair without it.
2. Bank details and the payment note print on every invoice, so nobody retypes them per document.

Invoices, and the money against them

You invoice the payer, not the student: a family with three children is one invoice, a school booking a workshop is a payer with no students attached. New invoice creates a draft — issuing is a separate press, because that is the moment the number is allocated, the due date is set from the payer's terms, and the figures stop being editable by anyone, including us. Corrections go the way they do on paper: a credit note that reverses the charge and leaves both records standing.

1. Filter by state, by payer or invoice number, and by issue date. The counts tell you whether a filter is worth clicking.
2. Overdue is worked out from the due date every time it is displayed, so it is never a day stale.
3. An issued invoice has no edit control anywhere on this screen. That is deliberate.

Chasing money, and proving a month

Since v10.8.0 the dashboard opens with a receivables card — what is unpaid, and how much of it is overdue — and every invoice that still carries a balance has a Record reminder button. A reminder is a bookkeeping fact, not a message: nothing is sent to the family, it simply lands in the invoice's history with a note ("called Friday, transfer promised"), so whoever picks up the phone next knows where the conversation stands. When a family asks "what did we actually pay this term", open their payer and press Statement: opening balance, every invoice, payment, credit and refund of the month in order, closing balance — printable like an invoice, and the closing figure is the same number the account shows as outstanding. Each student's record also carries a timeline that merges enrolment, credits, invoices and progress reports into one stream, so the front desk answers "what happened with this child" from one screen.

Teachers see their own hours and what they add up to, and confirm them at the end of a period — nobody else's hours, and no view of what families owe. Pick the period with the date range or one of the presets, search for a teacher by name, and the sessions behind every figure are one click away. We produce the amount and the list; paying it stays with whoever runs your payroll, because withholding and superannuation belong to your accountant and not to your scheduling software.

1. This month, last month, or any two dates. The period is a filter, not a fixed month.
2. Contractor or employee decides what may happen to the total next — a contractor's can become a payable bill in Xero, an employee's must not.

One-to-one lessons, and the three questions an absence asks

A private lesson is set once and repeats weekly, skipping your closures and any weeks you pause. When a lesson does not happen, recording it answers three separate questions — is the family still charged, is the teacher still paid, and is a make-up owed — because those genuinely have different answers. A student cancelling an hour before is normally charged and the teacher normally paid; a studio closing for a public holiday charges nobody and pays everybody. You set the rule once in plain words and the system applies it, then tells you what it decided.

1. Cancelling asks who called it off. Notice is measured against the studio clock, never the browser's.
2. Charged and paid are shown separately, because collapsing them into one word loses the point.
3. Make-up credits expire on a date, and expiry is worked out when you look, not by an overnight job.

11 · Reports

What the numbers are actually telling you

Owners and managers get a reporting tab: lifetime revenue, students enrolled, credits consumed, and the pool of credits still owed. Below it, twelve months of revenue and consumption, a six-month summary, a filterable financial detail report, and per-student spend.

1. Lifetime revenue, students enrolled, credits consumed, and the credits you still owe.
2. Twelve months of revenue against consumption. The gap between the two is the liability.

Exports (student CSV, operation log CSV) need the export permission and are recorded in the audit trail. Your subscription also gates the feature — if it is not enabled, the interface says so and points you at us.

12 · Us

What we can do inside your studio, and what stops us

We run the platform: creating studios, subscriptions and quotas, monitoring, backups, releases. We do not run yours.

We cannot simply open your CMS. Every request into a studio is refused until a support session for that specific studio has been started with a written reason. Starting and ending a session, and everything done during it, is written to your audit trail — visible to the owner under Studio Admin → Analytics → Audit Trail, reason included. The session covers one studio; it does not carry over to another, and access is withdrawn the moment it ends.

Isolation between studios is verified before every release: over 200 tenant-isolation checks must all pass or the release does not ship.

Changing your public address is ours to do, and deliberately slow. Ask, and we move the studio to a new slug — at most once a year. The old address is not deleted: it keeps redirecting to the new one for good, because it is already printed on flyers and encoded into QR codes, and a rename that broke those would be a rename that cost you enquiries. No address is ever handed to a different studio, even after a studio closes — its address is kept as a tombstone rather than reissued, so old printed material can never lead somebody to a business that is not yours.

Your subscription tier, its quotas and your billing dates are managed by us; they are read-only in your own screens. Ask and we will change them.

13 · Getting help

Check three things, then call us

1. Which screen and which account? Most “it disappeared” reports are a permission boundary working correctly — check section 09 first.
2. Draft or published? If it is about the public website, confirm you pressed Publish and not just Save Draft.
3. What does the operation log say? It records who did what and when, which usually answers the question faster than we can.

Still stuck: get in touch from the website. Migrating from spreadsheets? Start from the import template — CSV or Excel.

Our commitments and their limits are written down rather than implied: the support policy, the privacy policy and the terms of service.

14 · Questions

The ones we are actually asked

I saved, but the website hasn’t changed.

Save Draft only stores a draft. Press Publish. If the console says Published, public pages still need verification, the write already succeeded: wait briefly or press Recheck public pages. If the image is the thing that did not change, also force-refresh your browser.

I published something wrong. Can I undo it?

Yes. Preview / Publish → Publication history → Restore to Draft on the version you want, preview it, publish. Unpublished draft edits cannot be recovered this way.

Can I give a course an English name as well?

No, and it is deliberate. Course names and work titles are operating data, stored once and shown as typed. Section headings — “Courses & Classes” and so on — are the bilingual part, set in Studio Admin.

A parent wants to log in with an email and password.

Families cannot sign in to the CMS; the attempt is refused. Self-service is the student area with an access code — section 08.

Can we change our studio’s web address?

Yes. Ask us and we move you to a new one, at most once a year. Nothing you have already printed stops working: the old address redirects to the new one permanently, and it is never reissued to another studio. Your QR codes, flyers and search results all keep leading to you.

Can families book a class themselves?

Yes, once you switch it on. Publish the public timetable, tick the classes you want to appear on it, then switch on Accept booking requests. A visitor gives only a name and a phone number. The request does not hold a place — it waits in the CMS until someone approves it, and capacity is checked at that moment. See section 04.

I ticked the class as public, but it is not on the timetable.

Three things have to line up, and the ticked class is only the first. Check that the timetable page itself is switched on in Studio Admin, and that the class falls inside the number of weeks the page shows — one to four, and anything beyond that horizon is simply not on the page yet. A class cancelled for that date is shown as cancelled rather than hidden.

Will my teachers’ names show on the public timetable?

Only for the ones who have agreed. Two things must both be true: the Teacher field is switched on for the page, and that person has their own name switched on individually in CMS → Settings → Team. Turning the field on does not name anyone who has not agreed — those classes publish without a teacher.

Uploads keep failing.

Check the format (JPEG, PNG, WebP) and the size — one image may not exceed 30 megapixels, roughly 6000 × 5000. Both limits are reported, never silent.

What is the difference between selected work and the student gallery?

Who owns the work, and what makes it public. Selected work belongs to the studio or its principal; the owner curates it in Studio Admin, and it goes public within the plan quota. The student gallery is work from a student record; it goes public only on that family’s recorded consent, and it comes straight back down if the consent is withdrawn. Never move a student’s work into selected work — that would be routing around the consent, not satisfying it.

If I move to a smaller plan, do I lose the selected work I published?

No. The plan quota limits how many Active works are shown publicly, never how many are stored. Every record and its Featured rank stays in the board — up to 500 of them. A downgrade may hide work beyond the new quota, but an upgrade makes it eligible again in the same saved order, with nothing to re-enter.

Can I see whether a staff member issued a refund?

Owners can: Studio Admin → Analytics → Audit Trail, filtered by action. Refunds, exports, share links and our support sessions are all there, each with the person and the time.

Two applications from the same phone number.

Both cards carry the amber duplicate badge. Call before approving — see section 02.

Questions about hosting, backups, data location, multi-factor authentication or availability commitments are answered in the service FAQ — that one is written for the person signing the contract, this one for the person running the studio.