Project: I-worker Contracting

I-worker Contracting has now been framed as a prospective PHC Project focused on making ethical remote work legible, auditable, and scalable. The project is based on the iWorker-style model of connecting entrepreneurs and small organisations with skilled remote contractors from countries affected by crisis, including Venezuela and potentially other regions where remote work can provide meaningful income and professional opportunity.

The core proposition has been established: PHC Port can provide a lightweight governance layer that turns real remote-work activity into reviewable evidence. This includes timechunks, validated hours, actions, deliverables, decision context, Experience/CV records, and reporting outputs.

The Framing Questions, Strategic Plan, and Business Case have now been drafted in first-pass form. These documents define the value of the project for three audiences: contractors who need credible evidence of work and growth, clients or project owners who need better coordination and quality control, and funders or partners who need assurance that claims about work, payment, and impact are supported by records rather than anecdote.

The main barrier is that the project is still at concept and pilot-framing stage. No confirmed pilot group, partner agreement, participant list, validation process, or funding route has yet been established.

A second barrier is the need to keep the PHC layer genuinely lightweight. The project will only work if timechunk logging, deliverable tracking, validation, and Experience/CV output are useful to contractors and clients without creating excessive administration.

A third barrier is consent and data handling. The project may involve personal work history, client feedback, payment-related evidence, contractor development records, and possibly sensitive personal circumstances. Clear participant consent, access control, and publication rules will be needed before real data is used.

There are also operational risks linked to remote work in crisis-affected countries, including unstable electricity, unreliable internet, device failure, payment disruption, banking barriers, privacy exposure, and local conditions that may affect availability or delivery.

1. Confirm pilot route: identify whether the first pilot will be run with iWorker directly, with a small group of contractors and clients, or as a PHC Port demonstration using representative sample data.
2. Define the minimum data set: decide exactly what must be recorded: contractor profile, timechunks, task/action records, deliverables, validation notes, payment status, client feedback, and Experience/CV outputs.
3. Create onboarding material: prepare simple guidance for contractors, clients, and project owners explaining how to use PHC Port without creating unnecessary admin.
4. Agree validation rules: define who validates hours, deliverables, payment status, and completion evidence, and how disagreements or missing information are handled.
5. Prepare consent wording: create a clear participant consent statement covering data storage, use of records, Experience/CV outputs, anonymised reporting, and withdrawal or correction rights.
6. Develop sample outputs: produce examples of a timechunk report, contractor Experience record, deliverable history, monthly PHC status report, and funder-facing impact summary.
7. Design pilot review rhythm: establish a light weekly or monthly review process covering work logged, actions closed, deliverables completed, payment exceptions, contractor development, and lessons learned.
8. Clarify future service levels: distinguish between self-serve PHC Port use, supported pilot governance, contracted PHC reporting, and any later incentive/shareout mechanism based on validated hours.