A project framework designed to make scope and responsibility visible.

The sequence below explains a typical engagement. Actual stages, timing and documentation depend on the accepted proposal.

Stage 1

Discovery and qualification.

The initial enquiry is reviewed to understand the business objective, intended users, current systems, expected deliverables, available content, integrations, target market and any fixed constraints.

Discovery does not automatically create a contract. Workforce Infotech may request additional information before confirming whether the project is suitable.

Useful discovery inputs

Current website or application links
Feature and page requirements
User types and intended actions
Content, product and brand readiness
Third-party systems and access
Desired launch window

What the proposal should clarify

Deliverables and exclusions
Dependencies and assumptions
Client and provider responsibilities
Revision and approval process
Fees, taxes and third-party costs
Indicative schedule and milestones
Payment and cancellation terms
Handover and support terms

Stage 2

Scope and commercial agreement.

A proposal, estimate or agreement translates the discovery information into a defined scope. Any item not included should not be assumed to be part of the project.

Work should begin only after the applicable commercial terms and start requirements have been accepted.

Stages 3–5

Design, implementation and release.

Design and planning

Site structure, user journeys, visual direction, content placement and technical architecture are prepared in line with the scope. Review comments should be consolidated and supplied by the authorised decision-maker.

Development and testing

The approved direction is implemented. Functional checks, responsive testing and agreed integrations are completed. Clients may need to provide accounts, keys, content or test data.

Launch and handover

Deployment is coordinated after required approvals and access are available. Handover may include administrator credentials, approved files, documentation or a separate support arrangement.

Change control

What happens when requirements change.

Digital projects often evolve. A request that changes pages, features, integrations, content volume, user roles, creative direction or delivery assumptions may require a scope adjustment. Workforce Infotech should explain any effect on fees, timing or dependencies before undertaking material out-of-scope work.

Silence or informal discussion should not be treated as automatic acceptance of additional work. Important changes should be documented in writing.