Should I weigh meat raw or cooked when tracking macros?

Nikkiey's own routine is consistent across her dinner videos. When she preps a meal, protein goes on the plate first. She cooks the chicken, weighs it, and builds the rest of the meal around it. She weighs meat in ounces because, as she puts it, ounces are more precise for meat. Then she either scans the package barcode or searches the MyFitnessPal database, sets the serving size to ounces, and enters the number she sees on the scale.

She uses the same approach to hit a protein target. For a shredded chicken taco bowl, she weighs the chicken in ounces until it lands around the amount that gives her about 40 grams of protein. She adjusts a little if needed, then logs that exact number. She weighs her salmon on the scale in ounces too, so the macros calculate precisely.

For packaged foods like yogurt or cottage cheese, she uses a different method. Scan the barcode, change the serving size to one gram, and enter the grams you ate as the number of servings. For example, 200 grams of yogurt is 200 servings. Her takeaway is that the scale and exact entries are what make tracking accurate, not eyeballing.

One honest note: these episodes show Nikkiey weighing cooked meat, but they don't explain how raw and cooked weights differ or which database entry to choose for each. If your numbers ever seem off, that's a gap in the method, not a failure on your part. Weighing and logging the exact amount, the way she does, removes most of the guesswork.