Your approved clubs
–Sign in only when you are ready to request or use club access.
Accountable club contributionClub source retained · central verification required
Club operations
Club Pro
Give the people closest to the club a safe route into ZimPrem without surrendering editorial or data control. Verified club staff can submit structured updates, see their status and know when a change has actually reached the live public record.
Pending verification
–Contributor requests still awaiting a data-team decision.
Publication rule
Verified ≠ liveApproved submissions remain pending until an operator records their application to production data.
Operating model
The club can contribute. ZimPrem still verifies.
The product separates identity approval, evidence, verification and live application so accountability is visible instead of implied.
Step 01
Verify the contributor
A real club officer requests access and records their job role. ZimPrem verifies the person before a club workspace opens.
Step 02
Submit the exact change
Approved contributors identify the affected player, fixture, staff member, club record or media asset and attach source context.
Step 03
Central verification
The ZimPrem data team checks the change. It may be approved, returned for changes or rejected. Nothing publishes automatically.
Step 04
Apply to the live record
A verified change remains visibly pending until an operator records where it was applied to the public data.
Submission lifecycle
One status language from club to public site
01Draft
Prepared but not yet sent.
02Submitted
Waiting for central review.
03Needs changes
The data team needs clarification or evidence.
04Verified
Approved, but not yet treated as live until applied.
05Applied live
The verified change has been written into the public record.
Structured, not free-form chaos
Each submission records the affected entity, effective date, authorised club source, evidence and exact requested change.
No direct overwrite
Club contributors cannot silently overwrite public football records. The central verification layer remains the publishing gate.
Source survives publication
When a club-originated change is applied, its source and audit context can remain attached to the operating record.
Request access
Verify your club role
Use a real work email where possible and tell the data team what you would keep current. Details are used only to verify and operate the request.