STUDIO
Northstar ServicesNorthstar Workspace
Example

Your product so far

Built from your saved answers. Your current draft stays in the conversation.

LIVE CANVASYour product direction
YOUR PRODUCT, TAKING SHAPE

Northstar Workspace

From the first request to the final sign-off. One calm workspace for your coordinators, a focused mobile companion for technicians, and a clear view of progress for every customer.

Commercial property managersFacilities teams
Connected workflowsFrom conversation to product
THE WAY WORK FLOWS

Every step, connected.

2 journeys
JOURNEY 01

A request becomes a resolved job

Coordinators and technicians

  1. Receive request
  2. Assign a technician
  3. Complete the work
  4. Customer sign-off
What this journey needs to get right

A coordinator can assign a request, the assigned technician can update it from a phone, and the customer sees the new status.

JOURNEY 02

A confident first day

New technicians

  1. Accept invitation
  2. Practice an update
  3. Find first assignment
  4. Complete first job
What this journey needs to get right

A new technician can find and update their own assignment using the in-app guidance without accessing another technician’s work.

PLACES TO GET THINGS DONE

Your future workspace.

4 screens
Coordinators

Overview

See what needs attention and keep every request moving.

JobCustomerAssigned toStatus
New requestAssign work
What this screen needs to get right

Unassigned and overdue requests are visible without opening individual jobs.

Coordinators

Job board

Move work from a new request to a completed visit.

New requestsScheduledIn progressCompleted
New requestSchedule visit
What this screen needs to get right

Changing a job’s stage updates its status and preserves the change history.

Technicians

Job details

Everything needed to complete one assignment, in one place.

ActivityCustomerVisit details
Add updateComplete job
What this screen needs to get right

Only the assigned technician and authorised coordinators can update the job.

New technicians

First-day guide

Build confidence with one small, useful action at a time.

Meet your workspaceTry a practice updateFind your first job
Start guided practiceView my jobs
What this screen needs to get right

Practice is clearly labelled and cannot change a real customer job.

THE DIFFERENCE IT MAKES

What better looks like.

Every incoming request has an owner and a next step.

Technicians complete their first job update without assistance.

Customers can check progress without calling the office.

SECURITY & TRUST

Your protection plan

Planned

We’ve included a security foundation in your blueprint, with checks the build team must complete before release.

For your future product · Implementation and testing evidence is pending.

View protection details

Planned → Implemented → Tested. Each step needs supporting evidence. External compliance assessment is recorded separately.

Access that follows responsibilityPlanned · Build team

Enforce least privilege on the server, with stronger verification for privileged actions.

How we’ll verify it

Test each role, denied actions, expired sessions and attempts to elevate access.

Build team: implement and attach verification evidence before release.

Information stays within its boundaryPlanned · Build team

Keep each customer or organization’s records isolated, including exports, search and file access.

How we’ll verify it

Try to read and change another organization’s records through every data entry point.

Build team: implement and attach verification evidence before release.

Protected information and secretsPlanned · Build team

Use encryption in transit and appropriate encryption at rest. Keep secrets out of browsers, logs and exports.

How we’ll verify it

Inspect transport and storage configuration; scan shipped assets and logs for secrets.

Build team: implement and attach verification evidence before release.

Secure sign-in and sessionsPlanned · Build team

Use maintained identity services, secure cookies, revocation and appropriate reauthentication.

How we’ll verify it

Test sign-out, revoked access, session expiry and sensitive-action verification.

Build team: implement and attach verification evidence before release.

A record of important changesPlanned · Build team

Record sensitive access and important changes with actor and time; restrict log access and avoid unnecessary sensitive content.

How we’ll verify it

Verify audit events, restricted access, retention settings and redaction.

Build team: implement and attach verification evidence before release.

A tested way to recoverPlanned · Build team

Define backups, recovery targets and incident response appropriate to the product.

How we’ll verify it

Restore a backup in an isolated environment and record the recovery result.

Operating team: agree recovery targets and incident ownership.

Collect only what is neededPlanned · Build team

Limit sensitive data collection, define retention and deletion, and assess vendor data flows including AI.

How we’ll verify it

Trace data through vendors, logs and exports; test deletion against the agreed retention policy.

Product owner: confirm material retention and data-use obligations.

Security checks before releasePlanned · Build team

Map relevant OWASP ASVS requirements to the build, review dependencies and address material findings before launch.

How we’ll verify it

Record applicable requirements, test results, unresolved findings and release-owner acceptance.

Build team: implement and attach verification evidence before release.

These are proposed protections for the product being designed. Implementation and testing evidence has not been recorded. Autolace and hosting-provider assurances are separate.

Our verification reference: OWASP ASVS
Your projectsHelp
You’re exploring a fictional business. Preview actions use sample data; changes last for this visit.

Shape the product

Your product0 saved answers · Proposal up to date
LIVE CANVAS

Your latest product direction. Keep answering — this canvas grows with you.

YOUR PRODUCT, TAKING SHAPE

Northstar Workspace

From the first request to the final sign-off. One calm workspace for your coordinators, a focused mobile companion for technicians, and a clear view of progress for every customer.

Commercial property managersFacilities teams
Connected workflowsFrom conversation to product
THE WAY WORK FLOWS

Every step, connected.

2 journeys
JOURNEY 01

A request becomes a resolved job

Coordinators and technicians

  1. Receive request
  2. Assign a technician
  3. Complete the work
  4. Customer sign-off
What this journey needs to get right

A coordinator can assign a request, the assigned technician can update it from a phone, and the customer sees the new status.

JOURNEY 02

A confident first day

New technicians

  1. Accept invitation
  2. Practice an update
  3. Find first assignment
  4. Complete first job
What this journey needs to get right

A new technician can find and update their own assignment using the in-app guidance without accessing another technician’s work.

PLACES TO GET THINGS DONE

Your future workspace.

4 screens
Coordinators

Overview

See what needs attention and keep every request moving.

JobCustomerAssigned toStatus
New requestAssign work
What this screen needs to get right

Unassigned and overdue requests are visible without opening individual jobs.

Coordinators

Job board

Move work from a new request to a completed visit.

New requestsScheduledIn progressCompleted
New requestSchedule visit
What this screen needs to get right

Changing a job’s stage updates its status and preserves the change history.

Technicians

Job details

Everything needed to complete one assignment, in one place.

ActivityCustomerVisit details
Add updateComplete job
What this screen needs to get right

Only the assigned technician and authorised coordinators can update the job.

New technicians

First-day guide

Build confidence with one small, useful action at a time.

Meet your workspaceTry a practice updateFind your first job
Start guided practiceView my jobs
What this screen needs to get right

Practice is clearly labelled and cannot change a real customer job.

THE DIFFERENCE IT MAKES

What better looks like.

Every incoming request has an owner and a next step.

Technicians complete their first job update without assistance.

Customers can check progress without calling the office.