Last week’s date on a housing leaflet is not a design miss. A borough comms desk already published one PDF. A cleaner sky or a brighter block photo is a fair late request. A new generation that also moves the temporary-accommodation date is a public-record miss. NovalImage’s Nano banana only helps that reprint if the signed leaflet stays the source and the date stays the date readers already saw.
London leaflets get treated as notices. Residents keep the fold in a kitchen drawer and quote the week printed on the front. The reprint cost shows up as the afternoon spent telling housing officers, councillors, and the print contractor that yesterday’s run showed the wrong week.
Last Week’s Date Still Prints After Cleanup
Housing comms does not ship vibes. It ships a week, a phone line, and a block photo the cabinet already cleared. When an edit tool treats that page as a fresh poster, the date is the first thing that drifts. The new sky looks fine. The week on the banner does not match the PDF that went to the leader’s office.
The fail is easy to miss on a laptop. It shows up on the print-room counter, next to the pink date stamp the contractor uses before a run. If that stamp and the banner disagree, the stack is waste. The desk then reprints, and the first run still exists in someone’s hallway. Residents do not compare PDFs. They compare the paper they were handed with the week a neighbour was told on the doorstep.
Why Reprint Desks Recycle a Whole Leaflet
The old habit is honest and expensive. Someone exports a new JPEG, drops it on the InDesign page, and hopes the date survived because the rest of the layout did. That is how a signed PDF becomes a second original. The housing copy is the same. The week is not.
A full regenerate is tempting when the block photo is muddy. It is the wrong move once the leaflet has been to legal and to the print slot. The contractor has a file name and a fold. A new picture with a new week is a different notice, even if the sky is better.
The Signed PDF Becomes a Second Original
Exporting the approved page to a desktop folder looks tidy. It creates a cousin file. The next prompt then talks to the cousin, not to the notice residents already have. If the cousin invents 8 September where the cabinet signed 1 September, the desk is no longer editing. It is publishing a second week.
Keep the conversation on the file the borough already sent. Upload that PDF page, or paste the CMS image URL if it still lives on the site. Write one change: the sky, the block entrance, the mud on the path. Do not ask for a “fresher campaign look.” That phrase is how dates die. If two people on the desk cannot point to the same PDF in the shared drive, stop before the first generate. You do not yet have a source.
Readers Treat the Printed Date as a Record
A London housing leaflet is closer to a notice than to a lifestyle card. People use the week to decide when to call, when a viewing slot opens, or when a buyback update applies. If the printed week and the online PDF disagree, the resident is right to treat the paper as the lie.
That is why the reject sits in the print room, not in a brand review. Hold the pink stamp next to the banner. If a resident would quote two different weeks, the stack does not ship. No scorecard is required.
Lock the Date Region Before the Next Generate
The useful path is a local edit on a file the borough already owns. Open the workspace, start from that leaflet still, and name the region that may move. Banana AI image generator work belongs here only when the date is treated as a locked field, the way a notice number is locked.
NovaImage AI puts Image Marking on the Pro yearly row for that kind of pinpoint. Mark the sky or the muddy path. Leave the date banner and the housing body copy unmarked. If the unmarked week still changes, stop. The local-edit gate already failed. Do not stack adjectives and hope the next pass puts the week back.
Mark the Date, Leave the Housing Copy
Write the prompt the way a comms officer writes a print query. “Replace the grey sky. Keep the week and the phone line exactly as printed.” If Image Marking is on the plan, put the mark on the sky, not on the banner. A mark on the date is an invitation to rewrite the notice.
Failed generations on that workspace do not burn credits. That fact matters to a production manager watching a reprint budget. It does not matter to the resident holding the leaflet. The resident only sees the week.
Download the File the Printer Already Knows
Download the result and drop it back on the same page, in the same trim. Do not screenshot the workspace. A screenshot picks up Chrome the contractor did not quote. Put the file in the fold the printer already has on the docket.
Then do the only check that counts. Read the banner at print size. Read the phone line. If the sky moved and the week did not, the reprint can proceed. If the week moved, the file is dead, even if the block photo is sharper.
What a Comms Officer Rejects at Print
The reject is verbal and fast. The officer holds the signed PDF and the new printout on the counter. If the week changes, the stack is waste. If a new logo, a new slogan, or a second phone line appears, the stack is waste. A prettier courtyard does not clear that test.
| Check | Old whole-page regenerate | Region-locked edit |
| Source file | A new JPEG that is not the signed PDF | The leaflet page the cabinet already saw |
| What may move | Sky, brick, date, and phone line together | Only the marked region |
| How failure shows | The pink stamp and the banner disagree | The unmarked week stays, or the file is discarded |
| Who pays | A second print slot and a hallway full of wrong weeks | One generate, then a yes or a no |
Use the table as a door, not as a style guide. If the desk cannot name the one region that is allowed to change, hold the generate. The leaflet is still in argument.
A nano banana pro pass on NovaImage AI can stay on that same still for one named region. It cannot invent a new housing week and keep the notice honest. The officer has to refuse that swap, the same way they refuse a caption that names the wrong block.
When a Fresh Leaflet Is the Honest Next Step
Sometimes the sign still cannot take the change. The block photo is unusable. The entrance has been rebuilt. The phone line itself changed. That is a new notice, not an edit. Write the new week in the copy first. Get the cabinet to sign the new PDF. Then generate, if a picture is still needed.
Mixing the two jobs is how last week’s date survives in a drawer while this week’s date sits on the website. Keep the edit path for a still the borough already published and a change that stays local. Keep the new-leaflet path for a week that has not been signed.
Keep the Date If the Borough Already Published It
Comms desks that already published a week, and only need the sky or the path to move, can start from the signed page, mark one region, and read the banner at print size. If the week has drifted, reject the file. A desk still hunting a first picture belongs on a first generate, not this loop.
NovaImage AI is useful on that narrow civic job because the edit can start from a notice the borough already owns. The reprint stays calmer when the published week is a field, not a decoration the model is free to refresh.
Officers who need a new week should write the week in copy and get a fresh cabinet signature before anyone opens a generator.
