Raffles Consulting Services
Handle a WDG(JR+) milestone dispute using agreed acceptance criteria, source evidence, issue ownership and a controlled resolution record.
A WDG(JR+) milestone dispute should be resolved against the agreed proposal, evidence and acceptance criteria. The nett-fee model means government support is paid to the consultant after milestone completion, but the company still needs to decide whether the work was actually delivered. A disagreement should not be hidden by signing an acceptance note to keep the schedule moving.
Reconstruct the agreed milestone
Collect the approved proposal, quotation, work plan, deliverable definition, acceptance criteria, change record and relevant correspondence. State the milestone in plain terms and identify the company approver. Separate a missed result from a changed expectation that was never documented.
The current EWTP page explains the three support scopes, company cap and nett-fee model. The official EWTP factsheet describes WDG(JR+) as support for workforce transformation and job redesign. The accepted project documents determine the actual deliverables.
Test evidence with affected users
Compare the consultant’s output with source data, redesigned roles, observed work, training records and manager capability. Speak to the line managers and employees expected to use the change. Attendance, a slide deck or a configured tool is not sufficient when the milestone requires a working process or measurable outcome.
Record each defect, severity, evidence, business effect and proposed correction. Give the consultant a clear response period and preserve its explanation. Keep grant administration, commercial payment and project acceptance as separate decisions even when they are connected.
Resolve without backdating acceptance
Choose a documented outcome: accept, accept with minor tracked actions, reject pending remediation, vary through the permitted route or terminate according to the agreement. Obtain appropriate advice for contractual disputes. Do not backdate a sign-off or alter test evidence after the fact.
Update the project timetable, risk record and next milestone. Notify SBF through the published channel when programme treatment is required. Close the dispute only when the corrective evidence and authorised decision are read back and retained.
Keep employee communications factual and proportionate. A disputed consultant milestone should not become an unsupported statement about individual performance. Preserve confidential records with limited access while giving affected managers enough information to test the redesigned work and corrective action.
Turn the decision into a controlled file
Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.
Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.
Review before commitment and again before closeout
Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.
Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.
Handle exceptions without rewriting history
Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.
If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.
Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.
Verify the final outcome independently
Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.
Use the WDG(JR+) milestone-acceptance guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.
Practical review checklist
- Approved milestone reconstructed
- Acceptance criteria tested
- Affected users consulted
- Defects and responses recorded
- Authorised outcome retained
The dispute record is complete when the company can show what was promised, what was observed, how both sides responded and why an authorised decision was made without weakening the evidence trail.