ARRCARRC AGENCYCONSULTING · ENGINEERING · DELIVERY
Discuss a Project ↗
Working process · project delivery

A clear route from brief to handover.

Each stage has a review point and a visible output. The proposal and project agreement define the actual deliverables, timing, payment terms, revision allowance and acceptance criteria.

Four-stage workflow

Every stage should produce something reviewable.

These are typical deliverables. A smaller fix may use a lightweight version; a larger application may require more detailed documentation and approvals.

01 / DISCOVER

Understand the brief

Clarify business goals, target users, references, constraints, available assets and success criteria.

Key deliverablesProject brief · Requirements summary
02 / PLAN

Define the scope

Confirm agreed features, exclusions, technical assumptions, dependencies, milestones and review responsibilities.

Key deliverablesScope of work · Timeline · Milestone plan
03 / CREATE

Design & build

Implement in reviewable stages, share a review version and validate the user flows and technical checks that are in scope.

Key deliverablesDesign or working build · Review version · In-scope test results
04 / DELIVER

Review & hand over

Complete the agreed revisions, evaluate the acceptance criteria, record any agreed outstanding items and transfer the listed assets.

Key deliverablesFinal files or deployment · Documentation · Access handover where included
Approval points

Scope and commercial terms are confirmed before work begins. Where appropriate, the proposal defines review milestones and what constitutes acceptance. Requested changes outside the agreed scope are assessed for impact before implementation.

Commercial clarity

Process & project FAQ

These answers describe general working principles. The written proposal and signed agreement take precedence for a specific project.

When does development begin?

Work begins after the scope, commercial terms, required initial payment (if any), access and client-supplied materials are confirmed in writing. A discussion or submitted form does not reserve capacity or confirm a start date.

How are changes handled after the scope is agreed?

A request outside the agreed scope is reviewed for effort, dependencies, cost and schedule impact. Work starts on that change only after the updated scope or quote is approved.

What counts as project completion?

Completion is assessed against the deliverables and acceptance criteria written into the proposal or agreement. Any remaining items are documented and handled according to that agreement.

Which payment and revision terms apply?

The proposal or contract states the initial payment, milestone schedule, included revision rounds, additional-work rates, late-payment treatment and cancellation terms. No single payment percentage or revision allowance is assumed for every project.

What is included in handover?

Handover may include source files, assets, deployment notes, configuration guidance, documentation and agreed access transfer. Only the items explicitly listed in the written scope are included. Secret keys should be transferred through an agreed secure channel, not general enquiry forms.

Does a build automatically include maintenance or a warranty?

No. Bug-fix windows, maintenance hours, monitoring, support response times, hosting, backups and third-party costs are separate unless explicitly included in the contract.

Ready to scope a project?

Start with the outcome and must-have requirements. Exact price and delivery milestones are confirmed after review.

Build a project brief ↗Start a Project ↗
01 / SCOPE

Requirements & scope control

Work starts with a shared understanding of the intended outcome.

  • Objectives, deliverables and exclusions documented
  • Dependencies and client-supplied materials identified
  • Change requests assessed before additional work
  • Acceptance criteria agreed where appropriate
02 / IMPLEMENTATION

Build in reviewable stages

Where project size allows, work is divided into milestones that make progress easier to inspect.

  • Progress updates at agreed review points
  • Version control and sensible file organisation where applicable
  • Third-party services and dependencies identified
  • Scope changes discussed before implementation
03 / QUALITY

Testing & issue review

Testing is matched to the project's agreed scope and risk.

  • Key user flows and form validation checked
  • Responsive layouts reviewed on agreed breakpoints
  • Errors and known limitations documented
  • Production security, load and compliance testing quoted separately when needed
04 / HANDOVER

Delivery & documentation

Handover contents are agreed in advance rather than assumed.

  • Source code and assets included when agreed
  • Deployment and environment notes where applicable
  • Setup or usage documentation appropriate to scope
  • Ownership and third-party licence conditions documented
05 / COMMERCIALS

Payment & changes

Commercial details are confirmed in writing before commencement.

  • Project fees, currency and payment milestones
  • Included revisions and additional revision rates
  • Cancellation, refund and late-payment terms
  • Transfer fees and exchange-rate handling
06 / PRIVACY

Information handling

Share only the information needed to assess or deliver a project.

  • Do not send passwords or secret API keys through general forms
  • Client data and access requirements discussed before integration
  • Confidentiality terms can be agreed for eligible projects
  • See the published Privacy Notice for website enquiries
These are general working principles, not a guarantee that every listed activity is included in every engagement. Actual deliverables, service levels, testing depth, maintenance and response times depend on the written scope and agreement. No unverified certifications, customer results or uptime guarantees are claimed.
Need a clear delivery plan?

Send a project brief and we can confirm the appropriate scope, milestones, handover and commercial terms.

Create a project brief ↗Discuss requirements ↗
DELIVERY RESOURCES / ILLUSTRATIVE

See the structure of the documents used to control a project.

These are openly labelled sample templates, not records of past client work or automatically included contract deliverables. Actual documents, approval stages and support duties are selected in the signed scope.

Scope of Work

Deliverables, acceptance criteria, exclusions, dependencies and change boundaries.

Download sample SOW ↗