Evaluating gigs before you accept

Builders protect their reputation by choosing work they can finish well. A bad gig drains Execution Reputation; a good gig compounds your Passport. Diligence is not paranoia — it is professional hygiene, especially for freelancers balancing African time zones and payment risk.

Treat every gig as a temporary collaboration with Reputation consequences. The diligence checklist below is how freelancers keep Passport momentum without getting trapped in unpaid ambiguity.

Ask early

• Scope and definition of done
• Timeline and payment schedule
• Who reviews work and how often
• Ownership of IP and public portfolio rights
• Communication channel and timezone overlap

Scope and definition of done, timeline and payment schedule, who reviews work and how often, ownership of IP and public portfolio rights, communication channel and timezone overlap. Write the answers in the thread before you start.

If the client cannot answer payment schedule or definition of done, that is your answer. Strong clients welcome clarity because they also want finished work they can trust.

Ownership of IP and public portfolio rights matter if you need Passport growth. Negotiate a sanitized case study when NDAs are strict.

Red flags

Unclear scope, pressure to start unpaid “trials” that look like free labour, requests to hide the work permanently without a strong reason, or payment only “after investors fund.” If you cannot write definition of done in five bullets, do not start.

Takeaway: If you cannot write definition of done in five bullets, do not start.

If you cannot write definition of done in five bullets, do not start. Unclear scope is how Execution Reputation gets drained.

Protect the relationship

Write a short agreement summary in the thread. Confirm milestones in writing. Deliver early demos. Invoice on schedule. Use async stand-ups so progress stays visible without meeting debt.

Confirm milestones in writing, deliver early demos, and invoice on schedule. Professional hygiene compounds referrals.

Passport implications

Prefer gigs that allow a public-safe case study. If NDA blocks all proof, negotiate a sanitized write-up or decline if you need portfolio growth. Career OS Earn depends on something you can show.

When portfolio rights are blocked, ask whether a sanitized architecture write-up is allowed. Something public-safe is better than months of invisible labour that never compounds Earn.

Prefer gigs that allow a public-safe case study. If NDA blocks all proof and you need portfolio growth, decline or renegotiate.

Exit criteria

Agree how either side ends the engagement. Mid-project silence is expensive — set response SLAs. A clean exit protects both Passports and keeps the network’s trust graph healthy.

Closing

Good gigs compound your Passport. Bad gigs drain it. Before you accept the next brief, write five definition-of-done bullets and payment milestones in the thread. If you stall, ask Aurora for one next action that matches your persona, hours, and target role — then ship the link.