FTS commercial lane
Project work · Scoping starts immediately
03

Assessment AI

Assessment AI becomes the first separately scoped project under the new FTS and White Tower relationship, with scoping commencing immediately.

Relationship
Project work
Phase
Scoping now
Maintenance hours
0 hours used
Delivery
After project approval
Executive summary

Assessment AI is the first project to move into active scoping. The immediate work is to turn the eight candidate capabilities into a focused pilot scope, success criteria, delivery approach and separate project proposal.

Signal
8Capabilities to scope
Signal
1First project
Signal
0hMaintenance hours used
01 · Current state

What is currently there.

The evidence and boundaries that define this lane today.

In place

Scope inputs are available

FTS has supplied the initial capability list and the platform already contains the projects, documents and RFI workflows needed for discovery.

  • Eight candidate capabilities supplied by FTS
  • Existing project, document and RFI workflows
  • Operator patterns available as a technical reference
  • AI scoping can commence immediately
Boundary

Scoping defines the project

Implementation remains separate from Platform Maintenance and starts only after the project scope is approved.

  • Pilot problem and users to confirm
  • Data, security and integration constraints to map
  • Success measures and evaluation to define
  • Team, timing and investment to approve
02 · Project scoping

What will be scoped first.

The first project scope will define a narrow pilot, delivery controls and the path to approval.

01

Assessment workflow and pilot

  • Map the current assessment workflow
  • Identify the first high-value assessment problem
  • Select real or redacted pilot jobs
  • Define measurable success criteria
1
02

Eight candidate capabilities

  • Site constraints and siting requirements
  • Planning and building compliance
  • Design guidelines and overlays
  • Setbacks, height, site coverage and overlooking
  • Missing information or documentation
  • Potential approval risks
  • Recommended design changes
  • Review whether further information satisfies an existing request
2
03

Technical architecture

  • Project, document and RFI data access
  • Read-only tools and permission boundaries
  • Audit trail and evidence citations
  • Integration and hosting approach
3
04

Safeguards and evaluation

  • Human remains the decision-maker
  • Claims cite evidence or state what is missing
  • Writes remain off or confirmation-gated
  • Evaluation covers grounding, leakage, latency and cost
4
05

Project definition

  • Prioritised pilot capability list
  • Inclusions, exclusions and dependencies
  • Project team and responsibilities
  • Timeline and investment
  • Separate project scope and approval gate
5
03 · Value

What the first project could deliver.

The project scope will test value before FTS commits to implementation.

01

Faster assessment

Reduce time spent finding documents and repeatedly reviewing RFI packs.

02

Fewer avoidable misses

Use structured completeness and risk prompts to support professional review.

03

Auditable assistance

Trace material claims back to project evidence while keeping people responsible for decisions.

04 · Next steps

What happens next.

A short sequence with an owner and a clear outcome.

Start the scoping workshop

Nominate FTS participants and confirm the first session.

FTS

Map the assessment workflow

Document the current process, data and integration points.

White Tower team

Prioritise the pilot

Choose the first capability set and success measures.

FTS

Prepare the project scope

Define team, timing, investment, safeguards and delivery plan.

White Tower team

Approve delivery separately

Implementation starts only after FTS approves the project scope.

FTS

Project next step

Confirm the immediate Assessment AI scoping kickoff and nominate the FTS participants.

Scoping · Start now