A little help.
One clear step at a time.

1. Open Catering & Food Safety and enable the separate section only if the club offers catering.
2. Have the responsible operator approve the club-specific food-safety plan, hazards, controls, limits where applicable, monitoring and verification.
3. Add the plan reference, catering area and agreed procedure to each record.
4. Enter the observation or reading with its units/time and a club-assessed result. Record corrective action for anything outside the agreed control.
5. Keep unresolved actions visible; record the responsible reviewer and review date before marking Reviewed.
6. Export catering CSV or print working records as needed; confirm their completeness and secure handling.
7. Use the applicable local Safe Catering guidance and complete production validation before relying on the system for live food-safety management.

Check before you finish: The record matches the club’s approved procedure; an entered result is not an automatic safety determination.

Optional saved record pilot; off by default and restricted to the club owner. Sensors, automatic alerts, full retention/recovery, immutable records and an independently validated live HACCP workflow are not complete.

1. Choose Keep existing till, supported tablet POS or a separate customer self-service kiosk.
2. List the exact iPad/tablet model, operating-system version, country, provider, stand, reader and printer requirements.
3. Try the fictional venue screens, then test the intended live journey with approved provider hardware in a sandbox.
4. Use staff accounts for operations; a guest kiosk needs a separate restricted session, basket reset and a staff-help route.
5. Confirm charging, mounting, accessibility, networking, printer routing and how staff will handle outages. Offline operation is not assumed.
6. Keep card entry inside the approved payment provider flow; do not treat a browser demo as a certified payment terminal.
7. Agree hardware purchase, provider subscriptions, processing, setup and support costs separately before rollout.

Check before you finish: Each screen has a clear role, tested compatibility and an agreed failure/help route.

Venue demonstrations and setup guidance available. Our production kiosk, guest/session isolation, device-management rollout, live payment/printer integration and offline workflow are not complete.

1. Agree which club operations are enabled and who is responsible for each.
2. Give existing authorised accounts only the supported module or task/news access they need.
3. Use Club Office for saved tasks and private news; review open work before meetings.
4. Review sponsor commitments, recorded receipts and funding purposes separately from verified accounting balances.
5. Use the working report with its stated coverage; record unresolved actions and responsible people.
6. Keep policy reviews and committee handover information current. Review access when roles change.
7. Use available exports, Ask Sid and the support/build workflow when changes are needed.

Check before you finish: Responsibilities, supported access and the source of every report are clear.

Task/news and selected module pilots exist. A fully connected committee finance/operations dashboard and broader role-based handbook remain to complete.

1. Enable the optional Media section for the club.
2. In Sponsor Management choose Add a media-partner opportunity. Choose Club TV, Media partner or Podcast and record the term, cash agreement or in-kind services, renewal and promised benefits.
3. Agree exact content quantities, sponsor placements and reporting periods; keep Match Centre rights separate.
4. Move the agreement to Agreed or Active only when accepted.
5. In Media Centre plan each item and link the agreed partner from this club. Check guest permissions, content rights and any league publication restrictions.
6. Approve only a ready external link for the supporter hub. Record delivery evidence and tick benefits after fulfilment.
7. Use a budget to see whether actual sponsorship income after delivery costs can fund the Club OS fee. Do not count in-kind services as cash receipts.

Check before you finish: The contract, content, sponsor acknowledgement and delivery evidence agree; audience figures have a source, date range and metric.

Saved sponsor/editorial-link pilot. Automated filming, editing, analytics, invoicing, sponsor-report generation and social publishing remain to connect.

1. Use your own account; never share passwords or use demo PINs for real staff.
2. Check the selected business and grant only the minimum supported role to authorised people.
3. A platform admin role no longer automatically grants access through the shared business-workspace or Club Office checks.
4. Share only the information needed when you submit a support ticket; the support team can read your ticket.
5. The planned support-access process must allow customer approval, purpose, expiry, revocation and access history before any private operational access.
6. Use available scoped exports and agree retention and secure transfer before moving or closing an account.
7. Treat all public venue demonstrations as fictional. Wait for launch acceptance before entering confidential operational records.

Check before you finish: You understand what the application prevents and what has not yet been independently verified.

Password hashing, lockout, protected sessions and the changed ownership checks are present. MFA/passkeys, full module audit, customer-approved temporary support access and owner-inaccessible encryption are not complete. This is not a claim of zero-access storage.

1. Choose the correct signed-in business and module.
2. Save changes before exporting; a saved-record export excludes unsaved edits.
3. Use the Club Office working-report CSV or Hospitality Growth Office JSON and campaign CSV where available.
4. Review the export coverage, workspace, revision, dates, counts and any missing records.
5. For a full exit, agree remaining modules, documents, consent evidence and balances through a private support request.
6. Store downloaded files securely and test that the receiving system can interpret identifiers, dates, money and relationships.
7. Approve the final export, retention arrangements and account closure separately. Exporting never deletes records or cancels a subscription.

Check before you finish: The files cover the agreed scope; partial exports are not treated as full backups.

Partial module downloads available. Whole-account archives, full-suite extraction, bulk document bundles and self-service deletion remain unbuilt.

1. List your current systems, contracts, record types, future commitments and provider accounts.
2. Start a private build brief and request migration assessment; do not upload sensitive exports to a public demo or ordinary support message.
3. Agree source export rights, secure transfer, destination modules, mapping, deduplication and quoted work.
4. Preserve proven consent and withdrawals; unknown permissions do not become marketing permission.
5. Once the required import tooling is approved, review a test batch, rejected rows, record counts, totals and relationships.
6. Train staff, reconcile bookings, orders and outstanding balances, then agree the final freeze and switch.
7. Approve cutover only when the rollback plan and first-live checks are clear; retain or close the old service by agreement.

Check before you finish: The owner has accepted the migration report, exceptions and cutover plan.

Planning guide available. Source-specific importers, automated transfers, provider portability and live migration acceptance still require implementation and testing.

1. Open Venue demo and start a fictional session.
2. Choose Staff and a fictional employee, then use the displayed demo PIN to clock in or out.
3. Review the weekly rota, shift hours and sample wage-cost calculation.
4. Explore the fictional staff-lift panel; it sends no messages and confirms no journey.
5. Before live use, agree authenticated employee and manager access, durable records, rota rules and payroll boundaries.

Check before you finish: Demo hours and costs are understood as samples, not payroll or verified attendance.

Shared demonstration with clock actions and a sample rota display. Rota editing, leave, shift swaps, production staff records and payroll integration are not implemented.

1. Choose a new branded website, a full operational package or selected website widgets for your existing site.
2. Review menus, booking and ordering destinations so guests can take the next step.
3. Use the table and kitchen demo with fictional records; follow the separate food-safety guide.
4. Plan return visits in Customer Growth Office; save and review each campaign.
5. Confirm staff access, provider setup, support scope and readiness before live use.
6. Use Ask Sid, searchable guides and private tickets whenever a task is unclear.

Check before you finish: You know which tools are demonstrations, saved pilots or planned connections.

The commercial hub and guides are available. A complete live connected venue needs further rollout work.

1. Open the fictional demo to practise, or sign in to an authorised pilot business workspace.
2. Choose a template and write the audience brief, message and reviewed HTTPS destination.
3. Set expiry and any planned review time; check current capacity where relevant.
4. Save the draft, then mark reviewed after completing the checks. Editing resets review.
5. Use Pause when the offer should stop; save communication preferences separately.
6. Treat consent totals as recorded preferences, not a campaign recipient list.

Check before you finish: The intended business, saved revision, expiry and review status are correct.

Saved planning pilot. No messages are sent or automatically scheduled. Live audience matching, availability triggers and delivery controls remain unconnected.

1. Browse the Hospitality OS widget store.
2. Open the existing App Store listing or pilot and check its stage and scope.
3. Agree whether the website uses a button to a hosted service or a supported embed.
4. Confirm the venue, branding, licence and destination; the curated listing creates no extra subscription.
5. Test the complete mobile journey before adding it to the live site.

Check before you finish: The destination works and the feature has been approved for this venue.

Curated catalogue. Installation and readiness vary by tool; a universal embed is not available.

1. Open Venue demo, start a fictional session and select Food safety.
2. Choose a demo staff name and the opening, during-service or closing check.
3. Enter a temperature reading or record the checklist task.
4. For an out-of-range temperature, record the corrective action before saving.
5. Review the log, outstanding checks and printable sample report.
6. For real operations, use the venue’s approved food-safety plan and have the controls, staff responsibility, verification and record retention reviewed before rollout.

Check before you finish: Fictional readings, actions and outstanding checks are visible; a sample report is not a live compliance record.

Temporary shared venue demonstration only. A venue-specific hazard analysis, approved critical limits, durable authenticated records and full HACCP rollout are not completed.

1. Record the current provider, exact model and location in Growth Office settings.
2. Choose Keep existing or Consider an integrated option.
3. Have the team verify provider access and the data the connection can actually exchange.
4. Agree menu ownership, sales/refund reconciliation and failure handling.
5. Test in a provider sandbox before any live checkout or kitchen routing.

Check before you finish: Hardware, processing, integration and support charges are separately understood.

Till planning only. Square is the first proposed integration candidate; no provider connection or certified partnership is active.

1. Sign in and open My System Build.
2. Add your business information and save the private brief.
3. Submit the brief for the operator to prepare a customer-owned draft.
4. Review the exact saved version when the team requests approval.
5. Approve the design or request changes. A later edit requires fresh approval.

Check before you finish: The saved website revision matches the requested review revision.

Private build handoff is implemented and tested. Approval does not publish, activate billing or certify tools.

1. Use the Club OS page to explore the system and existing club layouts.
2. Treat Newry shop, ticket and pitch examples as browser pilots.
3. Use the protected funding tool for saved funding-role and audit records.
4. Confirm the club workspace, roles, approved targets and merchant dependencies before live use.

Check before you finish: Sample orders and pledges are not counted as verified club receipts.

Private task/news storage, scoped roles, saved working reports, private news staging and guardian links are tested pilots. Shop, ticket, pitch and paid journeys remain in development. Goal notifications are deferred.

1. Sign in and open private Club Office from My System Build after the club draft is prepared.
2. Check the selected club, add tasks or news drafts and choose Save club records.
3. Wait for the saved revision and reload to confirm the record.
4. If another person saved first, keep your changes separately, then use Discard & reload to get the latest version.
5. For an empty workspace, review browser import; only tasks and news are copied, and news remains private.
6. Review revision history and confirm an earlier snapshot only when you intend to restore it.

Check before you finish: The selected club and saved revision are correct; nothing is public or sent.

Scoped task/news roles, reviewed import/restore and private news staging are tested. Other operational modules and public release are still being connected.

1. The club owner opens Club Office access.
2. Use the person's existing customer-account email and review the intended club and role.
3. Choose Viewer for read-only, Media for news, Committee for tasks, or Editor for both.
4. Confirm the scoped grant. No invitation is sent.
5. Review and confirm revocation when access should end. Saved access history remains.
6. Use separate guardian links for parents; a staff role does not grant junior-record access.

Check before you finish: The person's role allows only the intended task/news actions.

Scoped role and revocation pilot tested. Named-user package allowances, invitations and permissions for other modules remain to confirm.

1. Save the Club Office news text first.
2. The owner or managed operator selects the saved drafts under Review news for your website.
3. Check the source Club Office and target website revisions.
4. Review the selected text and confirm private staging.
5. Request fresh design approval; staging revokes the old approval.
6. If the news page was independently edited, review it in Website Studio before replacement.

Check before you finish: The saved private news page matches the selected source; public content is unchanged.

Private news projection and save/stage races tested. Publication and full installation remain gated.

1. Ask the programme owner to check the correct existing account and registration link.
2. Sign in to Family Portal with your own account.
3. For a pending link, confirm its reference with the owner before affirming your authority.
4. After confirmation, review the linked registration and programme status.
5. Optional programme-update preferences start off and are separate from marketing.
6. Review withdrawal when you no longer need access. You cannot self-link or reactivate a revoked relationship.

Check before you finish: Only your confirmed linked registration is visible; no Club Office access is granted.

Guardian relationship and isolation pilot tested. Sessions, attendance, fees, message delivery and production family onboarding are not connected.

1. Open the selected club's Committee working report.
2. Check its source revision and generation time.
3. Review open tasks, currently completed tasks, private drafts and saved changes.
4. Use a baseline comparison only when an earlier snapshot exists.
5. Read Not connected coverage before interpreting financial or operational activity.
6. Download the saved-record CSV if needed; it contains private tasks and should be shared only with authorised people.

Check before you finish: Unknown or disconnected information is not counted as zero revenue or completed work.

Saved task/news report and guarded CSV tested. Full funding, shop/ticket/pitch/member reporting remains unconnected.

1. Open the class booking pilot and use fictional details.
2. Check the selected class, dates, capacity and term rules.
3. Review cancellation and waiting-list behaviour.
4. Keep guardian permissions and fee activation separate from a timetable demonstration.

Check before you finish: A saved pilot is not proof of live parent access or fee collection.

Class pilot exists; customer installation and payment dependencies require further verification.

1. Choose your system and describe the task without passwords or private records.
2. Read the matching guide, its current stage and next steps.
3. If the guide does not solve the problem, prepare a ticket.
4. Review the summary, add what you expected and send it from your account.
5. Follow replies in My Support Tickets.

Check before you finish: Only you decide when the prepared ticket is sent.

Sid uses guide matching and approved owner knowledge. Live AI conversation and email notifications are not connected.

1. Choose your type of business on the home page.
2. Open its master operating system and compare Basic, Pro and Gold.
3. Current proposed monthly totals include the website and hosting; exact package tools and Gold scope remain to confirm.
4. Try the business panel using sample information before choosing a package.

Check before you finish: You can explain which plan and website option you need, and its total price.

Available to explore. Choosing a package starts no billing.

1. Open the dashboard preview and select your sector and plan.
2. Start at Overview to see the sample diary and relevant totals.
3. Use the menu for customers, diary, reports and enabled tools.
4. Use Help & setup guides whenever a step is unclear.

Check before you finish: You can find the next task without opening every tool.

Preview with sample records. It does not connect to live account data.

1. Choose a sector prototype from Testing.
2. Add an example record at an unused time.
3. Try Complete, Cancel and Restore, and check the totals.
4. Select Reset to return to the original examples.

Check before you finish: The example moves to the expected status and totals change.

Local samples reset when you leave or reload.

1. Open Set up & update my website from your dashboard.
2. Choose your master OS, business template and package; answer the short questions for your business.
3. Tick tools within your package and add approved business photos. Save your progress before uploading.
4. Submit your information, then choose a favourite from three reviewed prepared looks.
5. Review the final saved version separately and approve or request changes.
6. Use Update my website for contact details, services, photos, news and social links; updates remain private until reviewed and released.

Check before you finish: Your chosen look and approved saved version are clear; no live preview appears during setup.

Guided brief, template-based three-choice handoff and restricted information editor sandbox-tested. Live AI generation, full upload/browser acceptance and launch certification remain unverified.

1. Choose a clear business photo you have permission to use; do not upload private customer or child records.
2. Save your business details, then add the logo, main photo and supporting photos in Your photos.
3. Use a JPG, PNG or WebP up to 1 MB.
4. The team fits the photos into your three prepared looks.
5. Ask for a framing change when reviewing those looks; later use Update my website to replace photos.

Check before you finish: The subject is clear, and the page does not feel cluttered.

Photo tools are available in the website pilot; uploads need an authorised account.

1. Compare Shop Basic, up to 25 products, and Shop Pro, up to 100.
2. For an existing saved website, use Add an online shop in the builder.
3. Add product photos, descriptions, prices and stock.
4. Complete delivery, collection, dispatch and returns information.
5. Check the basket and review the full page before approving publication.

Check before you finish: Every product has a clear price and fulfilment details.

Current pilot provides a catalogue and enquiry basket. It does not take payments or create paid orders.

1. Keep your current site if it serves your business well.
2. Choose the Ask Dougie tools you need separately.
3. Before launch, plan links such as Book now, Buy tickets or Buy a voucher.
4. If you want a new site on your own domain, agree the domain connection and mailbox needs.

Check before you finish: You know where customers will land when they click.

Custom domain requests do not connect DNS or activate a domain in the current pilot.

1. Open Customers in the dashboard preview.
2. Review the example history and its separate booking, buyer and recipient roles.
3. Check recorded contact preferences before planning an offer.
4. In a future live account, search existing records before adding duplicates.

Check before you finish: Buying a gift or ticket has not automatically subscribed someone to marketing.

Sample customer history is available; full customer workflows vary by tool.

1. Open the voucher demo for a supported sector.
2. Create a sample voucher using made-up purchaser and recipient details.
3. Review its reference, value and remaining balance.
4. Try a sample redemption and review the balance history.

Check before you finish: The balance is correct and purchaser and recipient remain separate.

Demo vouchers have no monetary value. Live checkout and delivery are not activated.

1. Open Events preview and choose or create a sample event.
2. Add its title, date, venue, capacity, price and programme.
3. Choose your own internal ticket route or an external seller link for the event.
4. Review the public event page and sample attendee records.
5. Try individual ticket check-in and confirm a second scan does not admit the same ticket again.

Check before you finish: The date, capacity and ticket destination are right.

Trial tickets are test-only. Live Stripe checkout and ticket email delivery remain disconnected.

1. In Events preview, open the event promotion tools.
2. Review the event link, artwork and platform wording.
3. Download the image or copy the text and link for each platform.
4. Open the available share option, or paste into the platform yourself.
5. Check the ticket destination before you publish the post.

Check before you finish: Each post contains the correct event date and a working destination link.

Sharing tools prepare assets and open supported composers. Automatic posting to every platform is not connected.

1. Open Newsletter preview and add your headline and update.
2. Keep the message focused on one offer or piece of news.
3. Check dates, prices and the call-to-action link.
4. Export the draft and review it before any later sending.

Check before you finish: Recipients will understand what to do next.

Drafting and export are available. Selecting recipients and sending need connection.

1. Open the performer business panel and Social audience.
2. Review each platform, its follower count, update time and connection status.
3. Record a manual snapshot when an automatic connection is unavailable.
4. Use automatic refresh only after a supported account has been authorised.

Check before you finish: A missing connection is not mistaken for a live reading.

Manual tracking is available. TikTok and YouTube adapters require account setup; other channels may need manual updates.

1. Open the performer preview and add made-up booking details.
2. Record the fee and change the enquiry status as you confirm the work.
3. Add the agreed date to the diary.
4. Prepare a sample invoice and review the customer, amount and date.

Check before you finish: The invoice matches the agreed work and fee.

Generated preview invoices are marked SAMPLE. Payment collection and live business invoicing require launch setup.

1. Choose your sector on Prices.
2. Open the current sector package page and review its proposed prices.
3. Separate monthly subscription, optional setup, applicable VAT and provider charges; scope varies by sector.
4. Package scope, support allowances, domains and mailboxes need separate confirmation. No billing is activated.

Check before you finish: You can separate subscription, optional setup and provider costs.

Proposed pricing only. No payments or subscriptions start in the preview.

1. Confirm the package’s approved named-user allowance; older pilot limits are not a final commercial promise.
2. List who needs access and the work they need to do.
3. Plan permissions so staff see only the records they need.
4. Review access when someone changes role or leaves.

Check before you finish: You have a clear list of staff and their responsibilities.

Scoped Club Office roles can be granted to existing accounts by the club owner. New team-account invitations and permissions for other modules remain planned.

1. Choose the reminder channels your customers need.
2. Review provider accounts, prices and permissions before connecting.
3. Use your business's own payment or messaging account where supported.
4. Test the complete customer journey before using it with real customers.

Check before you finish: You know who bills for each service and what a customer will receive.

Live SMS, WhatsApp, email sending and merchant payments are not activated.

1. Check the page says Preview, Test tool or Planned.
2. Local sample workflows reset when you leave; an edited draft is not necessarily saved.
3. For a saved pilot, check you are signed into the authorised account and wait for Save to finish.
4. If Save reports a conflict, keep your text separately before reloading the latest version.
5. Report the page, task, message and approximate time without customer details.

Check before you finish: You can describe the exact step that failed.

Product feedback is available during testing.

1. Open Log in and enter your registered email.
2. If needed, choose Forgot password and follow the reset instructions.
3. Do not share passwords or use the owner's account to test.
4. If new signup is unavailable, use the public previews.

Check before you finish: You are in the right account and have the right access.

Signup availability depends on launch setup. Reset delivery also needs its configured service.