01
Contributor and consent
Confirm the contributor's identity privately, record their permission to publish and agree the name or attribution that may appear publicly. No invented profiles, surprise publicity or implied availability for hire.
Built In Ireland · evidence before promotion
A portfolio line should tell a reviewer what changed, who checked it and where the evidence lives. Built In Ireland is developing that standard for Irish project work. Until a record meets it, we label the work unverified instead of turning a draft into a testimonial.
Current publication state
An integrity review found that three legacy draft pages contained names, dates, output totals, indexing results, recommendations and signing claims without a supporting entry in the site's evidence file. Those assertions have been removed from public-facing copy.
The old URLs remain so a shared link does not silently disappear. Each now carries a clear held status, a noindex instruction and an explanation of the evidence that would be required before a genuine record could replace it.
This is a correction, not a verdict on any real person. The audit did not establish that the named contributors existed, consented, completed the described work or received the described reference. The site therefore makes none of those claims.
The page itself is not the proof. A record becomes useful when another person can retrace the claim without relying on marketing language.
Confirm the contributor's identity privately, record their permission to publish and agree the name or attribution that may appear publicly. No invented profiles, surprise publicity or implied availability for hire.
Name the task in checkable terms: the files, research rows, editorial pages or release unit. Avoid vague praise and do not attribute an entire site's performance to one contributor.
Keep the brief, review trail and accepted artefacts. If a record mentions traffic, ranking, publication or deployment, preserve the dated report or release evidence that supports that specific statement.
A reviewer must be able to say what they inspected and what they did not. A logo, domain or generic organisation name is not a substitute for an accountable person.
Records can be corrected when evidence changes. The revision date and reason should be visible. Claims that a webpage “cannot be edited” are misleading; transparent change history is the more honest control.
A project artefact can support a narrow claim about work. It does not automatically establish employment, professional accreditation, client approval, authorship of every changed line or responsibility for later results.
Use it only when deployment or publication evidence exists. A local draft, pull request or content proposal is not shipped work.
State the scope of review. A technical check does not prove factual accuracy, and an editorial check does not prove commercial outcomes.
Analytics can show what happened after publication. They rarely prove that one page or person caused the change without a careful comparison.
Built In Ireland's older guides remain useful starting points for understanding Irish work-experience and return-to-work routes. They are informational articles, not a promise of a placement, a substitute for an official source or evidence that this site operates a matching service.
Scheme rules, eligibility and application steps change. Use a guide to learn the vocabulary, then confirm the current position with the named public body before acting.
Keep a short brief, the work itself, review notes and a dated result. Five strong, bounded examples usually communicate more than a long list of unsupported skills.
A career break does not need an invented client story. Explain the gap briefly, then show recent work that is genuine, relevant and easy to inspect.
Browse the work and scheme guides. Always follow their links to current official information.