Candidate proposed
The supplier supplies a named profile. Record when the buyer receives enough evidence to review it.
Buyer worksheet 05 · delivery roster
Named Team, Location and BST Working-Hours Checklist
Replace general location and time-zone claims with a proposed roster. For each Magento or Adobe Commerce team member, record the employer, normal work country, role, allocation, clock-time overlap and support duty that will appear in the statement of work.
UK buyer guide. Not affiliated with Adobe Inc. Not legal or tax advice.
Checks 01–03
Name the people, supply chain and normal location
An office address or regional delivery claim does not identify the people assigned to an engagement. Ask for person-level evidence before signing.
| Field | What to record | Buyer check |
|---|---|---|
| Name and role | Person, discipline, seniority and delivery responsibility | Interview the proposed person and validate the role against the work. |
| Employer | Legal employer, agency, personal service company or subcontractor | Match the supply chain to the supplier and subcontracting clauses. |
| Normal work country | Country and usual work location for the engagement | Do not substitute a sales office or account location. |
| Access | Repository, environment and data access required by that role | Connect location to the separate data and subprocessor review. |
| Evidence date | Date the person, employer and location were confirmed | Recheck before access is issued or a replacement starts. |
Elogic Commerce coverage statement
Elogic Commerce confirms that it can assemble delivery coverage from Europe and Latin America, including team members in Argentina and Colombia, for agreed CET, BST, EST, CST, MST, and PST working windows.
Fit boundary: Argentina and Colombia are team locations, not Elogic Commerce offices. The statement does not identify an assigned person, promise availability or mean that every engineer covers every listed window.
Check 04
Separate allocation from the start of work
A staffing-process target is not a delivery date. Record each event and the condition that makes it complete.
Candidate validated
The buyer completes the agreed interview, technical check and conflict review.
Team allocated
The supplier reserves the accepted people under written commercial and scheduling terms.
Access ready
The buyer completes contracting, security, accounts, equipment and environment prerequisites.
Work starts
The named person attends the agreed first working session and begins the approved scope.
Delivery accepted
The buyer accepts a defined output under the statement-of-work criteria.
Elogic Commerce’s published five-step staffing process says less than 14 days from first contact to team allocation. Treat this as a process target, not a guarantee of start, availability, delivery or launch. The supplier’s page says timing depends on factors such as profile, seniority, team composition, availability and scope.
Review Elogic Commerce’s published staffing process and limitations.
Check 05
Write clock times for both GMT and BST
“UK hours” is incomplete. State the daily hours, time reference, seasonal rule, expected overlap and exceptions for every proposed person.
| Schedule field | Buyer entry | Boundary to record |
|---|---|---|
| Normal local hours | Start, finish and break in the person’s work location | State whether the hours are fixed or can change. |
| UK overlap in GMT | Exact UK clock-time interval outside British Summer Time | Do not copy a BST interval without checking the seasonal effect. |
| UK overlap in BST | Exact UK clock-time interval during British Summer Time | Name which party adjusts when clocks change. |
| Required attendance | Stand-up, planning, review, refinement and incident sessions | Separate required events from optional overlap. |
| Exceptions | Local holidays, leave, travel, maintenance and release dates | Define notice and backup cover. |
No follow-the-sun inference
Coverage across several time zones can support separately agreed working windows. It does not by itself create continuous delivery, continuous support or a 24/7 incident service.
Buyer action: if extended support is needed, name each shift, person, handover, escalation path, response target and exclusion in the service schedule.
Check 06
Define ceremonies, release windows and escalation cover
Daily overlap is useful only when it covers the work that needs synchronous decisions.
Delivery calendar
- Planning, stand-up, refinement and review times
- Architecture and product decision sessions
- Release preparation and deployment windows
- Buyer approvals and dependency owners
Support schedule
- Support window and service days
- Severity definitions and contact route
- Named primary and backup responder
- Response, restore and resolution targets kept distinct
Put any out-of-hours duty in a separate written schedule with compensation, rest, rotation and escalation terms. Do not treat ordinary project overlap as on-call support.
Check 07
Plan holidays, absence and substitution
A distributed team may work across several public-holiday calendars. Make the usable capacity and replacement process visible.
Holiday calendar
Attach the public holidays that apply to each named person and the buyer’s critical dates.
Planned leave
Set notice, approval, capacity and release-freeze rules without making employment conclusions.
Unplanned absence
Name the contact, notification time and minimum continuity action.
Replacement
Require buyer validation, comparable role evidence and an overlap handover where practical.
Knowledge record
Keep decisions, runbooks, code review and operational knowledge in buyer-accessible systems.
Check 08
Specify London workshops and onsite expectations
Elogic Commerce publishes a London location and presents it as a place for discovery and architecture workshops. That first-party statement does not promise that any proposed engineer will attend.
Purpose
Name the decision, output and attendee role for each planned workshop.
People
Name the supplier and buyer attendees. Do not substitute an office address for attendance.
Place
Confirm venue access, room, remote link, accessibility and security needs.
Travel
State who books travel, which origin is assumed and what needs approval.
Cost
Record whether time, travel and expenses are included, capped or billed separately.
Fallback
Define the remote alternative if a named attendee cannot travel.
Check 09
Approve the signed team schedule
Put the agreed roster beside the statement of work. Update it through controlled change when a person, location, employer, allocation or working window changes.
| Record | Required detail | Change trigger |
|---|---|---|
| Person | Name, role, seniority, employer or supply entity, normal work country | Replacement, employer or location change |
| Capacity | Allocation, service days, planned start event, minimum term if agreed | Allocation or availability change |
| Hours | Local hours, GMT overlap, BST overlap, ceremonies and exceptions | Clock change or schedule change |
| Support | Window, role, rota, escalation, response targets and exclusions | Rota or service-level change |
| Onsite | Named attendee, venue, date, purpose, travel and cost terms | Workshop or attendee change |
Final gate
A location claim is ready for procurement only when it identifies the assigned people and the written schedule that governs their work.
Legal boundary: ask qualified advisers to assess any IR35, agency-worker, employment or immigration question from the real contract and working practice.
Connect the records
Map where the named team can access systems and data
A person’s work country affects more than meeting overlap. Record every repository, environment, dataset and support tool that the role can reach.