Take end-to-end ownership of the SharePoint pilot, covering the following areas:
· Homepage build: Deliver a modern communication site homepage from approved designs - layout, theming, navigation, native web parts, and any custom components the design genuinely requires.
· First use case: Scope and build one client use case end to end, chosen with the engagement lead once the homepage lands.
· Scope discipline: Push back when a request adds custom code for cosmetic gain. Out of the box wins unless there is a real reason it cannot.
2. Build and Hand Over Across a Tenant Boundary
· Mirror environment: Stand up and maintain a working replica of the client’s site structure in our tenant, populated with synthetic content only.
· Portable artefacts: Package every deliverable so it survives the move - PnP provisioning templates, .sppkg files, site scripts, theme JSON, design assets.
· Runbooks: Write deployment instructions precise enough for a non-technical person to follow unsupervised, including rollback steps.
· Drift management: Anticipate where the client’s real tenant will differ from ours - policies, existing branding, permissions, retention - and design around it rather than discovering it on deployment day.
· Design fidelity: Turn mockups into working pages that match the spec on spacing, type scale, states and behavior. Raise conflicts with the designer early rather than approximating.
· Responsive and accessible: Every page works on mobile and meets WCAG 2.1 AA. That is a requirement, not a stretch goal.
· Supported customization: Achieve the look through themes, site designs and SPFx. No CSS injection hacks that break at the next Microsoft release.
· Performance: Keep page load sensible and watch what your web parts do to first render.
· Paired deployment: Run screenshare sessions where the client’s maintainer drives and you navigate. Deploy through them, not around them.
· Practical teaching: Explain what you built in terms the maintainer can act on. Assume no coding background and no appetite for jargon.
· Documentation that lasts: Leave behind material the client can still use after the engagement ends.
· Estimation: Give honest effort estimates for the remaining use cases based on what the pilot actually taught you.
· Reusability: Build the homepage so its components and patterns carry into later phases instead of being rewritten.
· Risk flagging: Tell the engagement lead early when something will not work, will cost more than quoted, or depends on a client decision nobody has made.