WEBSITE PLANNING

Collect Permission and Evidence for a Project Story

Prepare a project story with an evidence and permission worksheet that separates verified work, measured outcomes and approved client quotations.

Choose a claim you can support

A project story can explain a problem, a decision and work completed without inventing a sales result. List each proposed statement and the evidence behind it. A deployment record may support that a feature was released; it does not establish that revenue increased because of that feature. If analytics are unavailable, describe the verified work and leave the outcome unclaimed.

Use a fictional approval worksheet

An example row might read: claim — replaced a broken inquiry route; evidence — dated before-and-after validation; client name — approval pending; screenshot — redaction needed; quote — not supplied. Another proposed claim, doubled leads, should remain excluded without a defined period, trustworthy measurement and appropriate context. These rows demonstrate a review process and are not North Front Digital client results.

Keep the client’s words authentic

Ask for approval of the exact quotation, attribution and context rather than composing praise and presenting it as a customer statement. The FTC’s reviews and testimonials guidance addresses fake or false testimonials. Permission to publish a logo or screenshot is also a separate decision; a project relationship alone should not be treated as permission for every asset.

Make publication review concrete

The handoff should contain the final draft, evidence references, authorized assets, redactions, approved attribution and a named reviewer. Remove private customer details from screenshots and check whether visible dates or metrics could mislead. Keep a record of what was approved and flag substantive later changes for review. This worksheet adds evidence control to a portfolio outline. Bring a real project and its available records to a content review discussion before promising a case study.